goldsztajn

I have tried googling this repeatedly and never found a satisfactory answer other than hacking out the comment code with every single install of wordpress (which either way would still be dealing with symptoms and not cause). Sorry if you think I implied it is “simple”, that wasn’t my intention; it’s obviously not simple because the problem has remained for so long.

Thank you for the reply. It is rather disconcerting that this can happen…. Any reason why this kind of problem has not been dealt with? Using a pluggin to block the spam bots seems to be dealing with the symptoms and not the cause…. (I upgraded to 3.0.1 just two hours ago and already the same problem).

Turns out my solution was exactly the same. orphaned <div> was within a single post, and somehow was created as a result of an image styling…not sure if wordpress’ new caption caused this, although I think it came about as i was previously using a captioning plugin (not needed anymore). Anyway, lesson here is check all posts for strange code.

I’m having exactly the same problem following a recent upgrade to 2.7. Sorry, but i don’t understand how you solved the problem… where was the unclosed div tag? was it within a single post? how was it generated?

You are using the two-column K2 which option means your header will be 780×200. The simpliest thing to do is edit your header image to those dimensions and then FTP the image into …./images/headers/ folder of the K2 theme. you can then choose this header from the k2 options page.

The solution is this plugin:

https://www.ndsinternet.com/blog/archives/2006/08/wordpress-plain-text-paste-plugin

On installation: when installing the plain text plugin two important points….
1. make sure pathways in lines 30, 31, 33 of the nds-paste.php file are correct for your site.
2. make sure to clear your cache.

a note to the very useful plugin mentioned by floatingworld: when installing the plain text plugin two important points….
1. make sure pathways in lines 30, 31, 33 of the nds-paste.php file are correct for your site.
2. make sure to clear your cache.

Basically had these problems with all my installations so far. The solution suggested of repeated checks on the permissions worked for me (basically change the permissions, disconnect, reconnect, change permissions). The problem of seemingly creating folders with 777 permissions but not actually being 777 (rather 755) occurred using both cuteFTP on a PC and Fetch on a mac.