Note:
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.drewvogel.com%2Findex.php%2F2006%2F08%2F17%2Fsystem-strangeness%2F&charset=%28detect+automatically%29&doctype=Inline&ss=1&verbose=1#line-109
You need to either make your scripts external or use CDATA, e.g.;
<script type="text/javascript">
<![CDATA[
... Drew's unescaped script content ...
]]>
</script>
The other errors are pretty self-explanatory…
Another note ;’):
Found <style type="text/css">#commentform{ display: none; }</style> in the source. I think FF is ignoring the diplay:none; but IE is not. My question is what the hell is it doing there in the first place? Afraid I can’t answer that one…
Thanks for your reply. I feel like we’re close on solving this issue!
> You need to either make your scripts external or use CDATA
>
I’m not sure how to accomplish those goals. Can you enlighten me? Use small words — 🙂 — I’m no coder!
> Found <style type=”text/css”>#commentform{ display: none; }</style> in the source.
>
Where can I look to fix that?
I might be wrong (as it often happens) but a few days ago another user had similar “disappearing comments” issues and strange code all over their blog… and they were using the same hashcash thingy.
Moshu’s right (thanks moshu) hashcash may be trying to hide the comment form from those not registered/logged in? Deactivate and test.
As to the CDATA I gave an example above…
Thanks Yosemite and Moshu for your replies.
> Moshu’s right (thanks moshu) hashcash may be trying to hide the comment form from those not registered/logged in? Deactivate and test.
>
Deactivating hashcash enables comment form to appear again in IE, thereby fixing the problem!
> As to the CDATA I gave an example above…
>
Yes, but where do I make those edits? I don’t even know where to look! Or is it better to make the scripts external? Again, not sure how to do that either…
This afternoon I hope to dig into the permalinks. I anticipate having more questions on that subject!
Making scripts external is pretty easy. Take all of the script stuff itself (everything between the <script></script> tags and put it into a file, save it as whatever the name of the script is using the extension .js.
Then set up the script tagset in the head of each page which needs access to it, like this:
<script type="text/javascript" src="*.js"></script>, replacing the * with the name of the file you created. And of course, make sure you upload it to the root of your site or wp install, whichever makes most sense.
> Making scripts external is pretty easy. Take all of the script stuff itself (everything between the <script></script> tags and put it into a file, save it as whatever the name of the script is using the extension .js.
>
Thank you for your reply. The question I’ve got, I guess, is where do I FIND the “script stuff itself”? That’s what’s confusing me…
Also, I’ve disabled HashCash completely. The newer version (3.2 instead of 2.3) made it work in IE but not work in Firefox.
Now, however, I had to disable my cache again because it would work if you hit the page once (when the cache page is generated), but failed to display (only the white screen) if you hit it again.
One is in your header.php, but it may be getting generated by your ‘live’ plugin. Other one is in the footer.php, perhaps the end of the ‘live’ finctions? Not sure…
Check the ‘live’ plugin author’s site?
I have removed that Live plugin. I never used it anyhow… Have the script issues you mentioned previously disappeared from the front page now?
I had to disable my cache again because it would work if you hit the page once (when the cache page is generated), but failed to display (only a white screen is displayed) if you hit it again. VERY strange.
Bingo! First one’s gone (header). Still have the footer one. The footer one makes reference to “hReview microformat”, ring a bell?
As to the wp-cache blank-page issue there is a fix: Go to Quick look at WordPress issues in May: and scroll down to “On May 17th Pedro Valente (and Dreamhost) shared this regarding wp-cache:”
Thanks for the reply!
I think the footer is refering to the Structured Blogging (http://www.structuredblogging.org) plugin I had. I’ve now deactivated it, so it should be clean. Please let me know what you find.
Regarding the cache and the fix you mentioned… I had previously applied that fix and in fact it’s what is currently in the wp-cache-phase2.php file. Still stumped…
Here’s the results of my latest experiments…
I carefully followed the instructions (1-5) in wordpress.org/support/topic/58389 (including removing “/index.php” from the permalink in #4) and it didn’t work. The URL showed the permalink in the desired format (“http://www.drewvogel.com/2006/08/18/system-strangeness/”), but the page didn’t display.
I noticed that rolling back after the failure — that is, restoring the backup of my .htaccess file and adding “/index.php” back to the permalink and updating the permalink structure — did NOT return the site to working order. Simply VISITING Options->Permalinks is enough to cause the site to stop working, no matter if I “Update Permalink Structure” or not. I ended up having to Empty and restore my WordPress database from backup! This is bad.
Any ideas how to proceed?
We’re back to two issues — the cache is no longer working (and is currently disabled), and the ongoing permalink issue.
What’s your .htaccess look like?
Thanks for your continued assistance. Here’s the .htaccess file:
# BEGIN Url Rewrite section
# (Automatically generated. Do not edit this section)
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d [OR]
RewriteCond %{REQUEST_FILENAME} gallery\_remote2\.php
RewriteCond %{REQUEST_FILENAME} !/wp-gallery2\.php$
RewriteRule . – [L]
RewriteCond %{THE_REQUEST} \ /d/([0-9]+)-([0-9]+)/([^\/\?]+)(\?.|\ .)
RewriteCond %{REQUEST_FILENAME} !/wp-gallery2\.php$
RewriteRule . /gallery2/main.php?g2_view=core.DownloadItem&g2_itemId=%1&g2_serialNumber=%2&g2_fileName=%3 [QSA,L]
RewriteCond %{THE_REQUEST} \ /f/([^?]+)(\?.|\ .)
RewriteCond %{REQUEST_FILENAME} !/wp-gallery2\.php$
RewriteRule . /wp-gallery2.php?g2_controller=permalinks.Redirect&g2_filename=%1 [QSA,L]
RewriteCond %{THE_REQUEST} \ /v/([^?]+)(\?.|\ .)
RewriteCond %{REQUEST_FILENAME} !/wp-gallery2\.php$
RewriteRule . /wp-gallery2.php?g2_view=core.ShowItem&g2_path=%1 [QSA,L]
</IfModule>
# END Url Rewrite section
# BEGIN worst-offenders
Deny from 193.93.237.16
Deny from 193.93.237.20
Deny from 193.93.237.29
<longish list of “Deny from…” deleted>
# END worst-offenders
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
