schestowitz

it’s not tested, but

blockquote:before {
content: url(/IMG/image.png) ” “;
}

I don’t even know if it’s perimitted when it comes to standards.

I am not too sure it’ll provide a solution. What browser are you using? Have you got another browser to test this with? Maybe a mate who can test this from a remote computer? You can try viewing your site from a proxy. Try <My domain name>/proxy. Username is ‘open’, password is ‘proxy’.

Have you contacted the author of the plug-in? It would be hard to judge as we have no access to the editor, so can’t see for ourselves. Maybe it’s a known bug that is described in the form of comments in the author’s homepage. There are other spellchecker tools, by the way. Some of them are browser-bound.

Sounds like a php file is treated as a simple object here. Contact the system admin if you haven’t PHP running. See server information as well if the sysadmin is on holiday…

This sounds similar to:

http://wordpress.org/support/topic/52993

Does this happen in all items (posts)? It sounds as though there might be a bad comment or something that was not propagated successfully from a previous installation.

This would be very hard to achieve. You will need to hack the WordPress code to do this. I thought about this before, but it has many reasons to be avoided. What’ll happen if you display various items together and each one inhereits a different theme? Thoughts to ponder…

You must have stumbled upon an implementational conflict. The index files are used to display categories as well as anything else at the core. Changing the order of items fetching perhaps causes the archives-generating function to fail. Maybe it has an implicit precondision — an assumption about post order. All in all, you could probably retract the changes or find a more robust solution/hack.

This is quite normal. the comment will probably show up later.