I have the following code in a rendering, running on multiple environments:
<li class="formWWW">
<span class="formNumber"><sc:text field="Form Number" /></span>
<h4><sc:link field="URL"><sc:text field="Title" /></sc:link></h4>
<p><xsl:value-of select="sc:fld('Description', .)" /></p>
</li>
The issue I'm having involves the <sc:link> inside the h4. On my local machine and in our development environment, it properly generates an anchor tag the way it is supposed to; however, in our QA testing environment, it seems as though <sc:link> is just dumping the contents of the URL (General Link) field instead of rendering it as an anchor. It is very confusing since I know the renderings and the data inside the fields are both consistent among the environments.
My best guess is that there is a configuration setting somewhere relating to the behavior of <sc:link>, but I don't know. Thank you for your time.
I thought about just deleting this question, but it may be useful for others down the line to know that the problem was solved by resetting IIS. It seems as though whenever nothing makes sense, iisreset.
Related
I am using cayman theme for github for writing scientific articles which i can host on Github pages. I am using mathjax to render equations.
I have pasted the following lines inside the cayman/_includes/head-custom.html file.
<script type="text/javascript" id="MathJax-script" async
src="https://cdn.jsdelivr.net/npm/mathjax#3/es5/tex-mml-chtml.js">
</script>
Mathjax renders the math equations correctly (local and remote), but it produces an error on Github (image attached). I can not make anything out of this error, I am a little concerned that it may create bigger issue later on.
Any guesses why this error and how to fix it.
It appears that your html-proofer test script implementation is set to check for CORS/SRI on external js resources and thus is throwing a validation error because it's expecting a couple of additional attributes on all <script> tags (that aren't there currently on the tags in question), crossorigin="anonymous" and integrity="...insert-sha256-value-here..."
My understanding is that SRI needs to be supported by the developer and therefore the integrity value should be coming from them.
If MathJax hasn't provided an integrity value along with their CDN script code then I think you may need to disable checking for CORS/SRI to eliminate the error.
Do you have access to the script that contains the command that runs html-proofer, and if so, can you see if it's checking for SRI? Might look something like this:
htmlproofer --check-sri ...
According to the html-proofer docs, --check-sri defaults to false, so if this option is being set and you can disable it, I'd give that a try.
dynamicBullets is not supported in ionic-slides?
ionic-slides adopted from swiper.js and swiper.js support dynamicBullets: boolean.
How can I use dynamicBullets in ionic-slides?
I even tried to inject swiper.js into the ionic project and it's not working well. I believe there is a conflict error somewhere in ionic since it was adopted from swiper.js
I am using this to add bullets in text line. try this
<ul>
<li><p>Keep your knees and tons pointing slightly outwards as you jump.</p>
</li>
<li><p>Land with soft knees on the balls of your feet to protect your knees.</p></li>
<li><p>Go as fast as you can without losing control.</p></li>
</ul>
My problem, in a nutshell, is the following:
I use Privoxy to set up a whitelist of sites in Raspbian Jessie on Chromium. I have Chromium start on boot with the following snippet in lxsession/LXDE-pi/autostart:
#privoxy
#chromium --incognito --kiosk --proxy-server=127.0.0.1:8118
This does work as intended, with every site except the ones I specify blacklisted.
Now I edited /privoxy/templates/blocked so that instead of the usual site it will give me a redirect to a certain site should a link be opened that is not on the whitelist:
<!DOCTYPE html>
(Stuff happens)
Please go back to this site.
example.com being one of the sites I whitelisted. The problem is, it simply redirects me to the "blocked" page again, making me stuck in a loop. Does anyone have a clue why this would be and how I could work around it? I tried using
window.history.back()
however it doesn't seem to work either.
I use Kiosk mode because I want to use this in a context where entereing URL-adresses is not desired, just to clarify my Chromium-call.
Well, I solved it, at least partially. Turns out that I need to add http:// in front of the URL, since it gets added to the already existing URL otherwise. Which is fair, but a bit awkward for me to admit. HTML isn't exactly my forté. Marking it as solved and keeping it, just in case somebody stumbles upon a similar problem.
I would like to use magnific popup for a site which is still in development, but unfortunately nothing happens after the installation and adding the static content in my template.
No matter what i try no popup comes up.
If someone would like to help me i will provide access to the site.
Thanks a lot!
First thing to do:
look at your source code: does the 'link' show any sign of 'magnific popup' code?
Added classes? id?
Second: do you see any extra javascript and/or stylesheet that is added by the extension?
If you answer negative to 1 of these, the extension does not output anything. Sounds logic, but it is the first step. Is it a solution? Nope, it means your live just got a bit more worse, but hang in there !
If it does show any code from the ext: look at your console, are there any js errors occurred ? (if you don't know what console is, or (even worse) you work with IE) please read about chrome console of at least install Firefox with firebug.
My best beth would be a JS error...
Can it be possible that the ext itself does not work?
Does your php error logs tell you that the extension is behaving badly?
Do you see errors in the typoscript analyser (or whatever it's called to analyse the css_styled_content and other TS spaghetti )
If not, then no, it is not the ext.
Again, i'm betting my wive, three horses and a barrel of beer on JS erros.
Good luck mate !
ps: IF i'm wrong, i'm not sending you my wife by postal service. Loads of trouble last time. Nor the horses, same shizzle ..
Is it possible to make nXML mode more convenient for web development?
Specifically:
Treat <? ... ?> bits as if they didn't exist
Don't issue "Unknown element" warnings when the XML schema is
unknown
I'd rather not use a multi-mode
Edit:
Regarding point 2, the vacuous schema is supposed to do that, but it gets confused when there is no root element. A quick fix is to wrap everything in a tag with any name
Edit2:
A better fix still, might be to write a script that will:
Check if the schema is vacuous, after entering nxml mode
If it is, add <temporary-root-tag> in the beginning of the document
Before saving, remove the tag
After saving, put the tag back
Setting (rng-validate-mode 0) is probably a good start.
Do you know about nxhtml mode? It is specifically for web development and it builds on nxml.