Try installing a totally clean copy of WordPress freshly downloaded and see if you get the same problem.
Ok, will try that tonight. However, I don’t think it will solve the problem, i did a scp to the production server so everything should be right.
I forgot that I have also tried different browsers with the same result (Well, should be, as it is a PHP issue, not a browser issue).
Greetings !
After reinstalling WP 3.0.1, WP 3.0.0, and trying endlessly different solutions… I’ve kind of solved it, and it has nothing to do with whatever was posted before…
I copied/pasted a LOT of lorem ipsum text just to see whether it was a post size problem, but everything was ok. In total, 2x 150 paragraphs, 2x 17939 words, 2x 120716 bytes of Lorem Ipsum text, which was far up the 4.553 bytes text I was trying to post. (Thanks to lorem ipsum btw, you’ve helped a lot of times xD)
With the lorem ipsum result, the only problem could be in the text itself… the only “strange” character was the “@”, which was repeated a lot of times (it is a page which displays many, many emails). I replaced all occurrences of @ with some other text ( :%s/@/(in)/g
did the trick) and violá: everything was normal.
Conclusion:
I don’t think this is a specific WP bug, because on my test server I have no problems at all with the same “@-contaminated” text. Could it be some spam filter on the hosting? It that even possible?
Greetings.
Moderator
James Huff
(@macmanx)
Volunteer Moderator
Just to be sure, try deactivating all plugins. If that resolves the issue, reactivate each one individually until you find the cause.
If that does not resolve the issue, try switching to the Default theme (WordPress 1.5 – 2.9.2) or the Twenty Ten theme (WordPress 3.0 and higher) to rule-out a theme-specific issue.
If neither of those help, it’s possible that a server-side security script (probably mod_security
) is preventing text with the @
symbol from being passed to the database via PHP’s POST
command, and you should definitely contact your hosting provider about that.
@james: that was the first thing I did.
I have completely solved the problem: on the hosting, there was a php.ini value which was the cause of the problem: it was auto-prepending a file called anti-spam-v2.php so a simple php_value auto_prepend_file none in my .htaccess was enough to completely solve the issue.
Greetings.