Forum Replies Created
Thank you for the information – that is good news.
Thank you also for continuing to support this great theme.
Thanks for your comments. I can see it is not a straightforward fix.
Great info about the WordPress ticket that I hadn’t seen – I noticed that has now been assigned, so maybe something will happen there.
Thanks for considering this. I understand that child themes and plugins are another issue but it would be great if standard Thematic supported CSP out of the box.
Regarding the inline script from
wp_localize_script()– instead of inlining it would it be possible to have Themnatic load it from local script file instead?
Hmm, should have used search earlier! I just found this discussion which is exactly what I am after, Scott even has the code I need!
I read through the discussion and noted the html5 comments but I was just thinking wouldn’t it make life easier if aside widgets were not h1 by default exactly for SEO. Bing SEO Analyzer flags multiple h1’s as a high severity issue –
High Severity Issue There are multiple h1 tags on the page. Recommended Action: Remove redundant h1 tags from the page source, so that only one h1 tag exists.
I used a macro in a text editor to find all the modernizr functions (tests[‘…’]) in the modernizr.js included with childsplay and then searched for them in my childsplay style.css. I excluded the modernizr.xxx functions as they are easy to find anyway (none used in childsplay).
I only found …
I can comment out the audio and video items as I don’t need them. Altogether I will get a huge reduction in the size of the final modernizr script used on my site, once compressed it will be < 10% of the uncompressed full script.
In case this of use to someone else the full list of modernizr functions I used to search from was
inlinesvg svgclippaths smil inlinesvg svg applicationcache webworkers sessionstorage localstorage audio video generatedcontent fontface csstransitions csstransforms3d csstransforms cssreflections cssgradients csscolumns cssanimations opacity textshadow boxshadow borderradius borderimage backgroundsize multiplebgs hsla rgba websockets draganddrop history hashchange indexedDB websqldatabase postmessage geolocation touch webgl canvastext canvas flexboxlegacy flexbox smil
Thanks for the tip on the html5 plugin – I had already noticed and I plan to try it out shortly.
I also wonder is there such a thing as a css / js “compiler”, by that I mean a program that generates files which include the only code that is actually used / needed. Approx 50% of my sytle sheet css is superfluous and AFAIK minify type programmes eliminate unused css.
A couple of follow-on’s
- a) How do you figure out which modernizr elements need to be enabled in the build options when you are production ready? It doesn’t seem reliable to just do that from memory – not for me at least. b) Do you use modernizr.load?
- OK – I’ll wait for the stable release and your update.
- Thanks – I appreciate the effort it must take to support themes that you may not be using much any more.
You didn’t mention the name of your awesome responsive theme – is it Titanic?
You are completely correct (of course!). I hadn’t properly understood how the full blog_description function worked. I thought that you missed out the
add_actionfor simplicity and I assumed I should include it. Effectively I was calling the override function twice 🙁
Thanks for correcting my error so quickly.
Thanks for you comments.
I had looked at WordPress SEO by Yoast previously and I felt there was a lot of overhead that I didn’t need as my pages are static.
However in light of your comments I’ve put my function tweaks on ice and have decided to give WordPress SEO another try.