Technosailor - Latest Comments in WordPress 2.0.1 Posting Bug

Re: WordPress 2.0.1 Posting Bug

Aaron Brazell — Sun, 30 Apr 2006 22:54:19 -0000

Are you running PHP exec or something? '<a href="http://curl.haxx.se/" rel="nofollow">curl</a>' is a unix library for fetching/grokking URLs from the command line and PHP has wrapper functions around it.

Re: WordPress 2.0.1 Posting Bug

Minks — Sun, 30 Apr 2006 01:05:21 -0000

Finally, I found the problem. It's the word that trigger the problem. So I changed it to plural or tense and the problem solved. This is crazy, because that sentence doesn't make sense let alone is grammatically correct.

I find this really ridculous, what is wrong with the word curl? Any significant issue to technical or program problem?

Re: WordPress 2.0.1 Posting Bug

Minks — Sun, 30 Apr 2006 00:56:10 -0000

I tried that on wp 2.02 and still face the same problem. Any other soloution

Re: WordPress 2.0.1 Posting Bug

Aaron — Wed, 15 Mar 2006 21:36:16 -0000

Which version are you running, Stacie?

Re: WordPress 2.0.1 Posting Bug

Stacie — Wed, 15 Mar 2006 21:21:43 -0000

Well, I finally did it and updated. Now, do I still do the second patch or will I mess something up? Everything is running great right now.

Re: WordPress 2.0.1 Posting Bug

Nimrod — Tue, 14 Mar 2006 14:30:41 -0000

[Comment ID #4698 Will Be Quoted Here]

No, I don't think so. I do have PHP Markdown installed. But since the words 'curl' is usually found in <code> or <pre> markup on my post, I was not able to use Markdown to format text with 'curl' in them. Markdown would use HTML entities for anything that is formatted as code (indented by 4 spaces). So I had to resort to using HTML tags.

Re: WordPress 2.0.1 Posting Bug

Aaron — Tue, 14 Mar 2006 14:23:09 -0000

Actually you can use <code> or <pre> or a combination of both as well. Do you have a plugin that executes PHP in the post because that could be making it wonky as well.

Re: WordPress 2.0.1 Posting Bug

Nimrod — Tue, 14 Mar 2006 14:11:05 -0000

That last bit should have been:

The work-around I have found is to wrap the words 'curl' with SPAN tags.

Re: WordPress 2.0.1 Posting Bug

Nimrod — Tue, 14 Mar 2006 14:08:53 -0000

[Comment ID #4695 Will Be Quoted Here]

I am using 2.0.2. I reuploaded the unmodified functions.php. Anyway, I have tracked down the culprit. It seems that the host that my blog is on is using mod_security.

The post that triggers the behavior is very long and contains what would be interpreted as a shell scripting attack by mod_security. I found out that it gets triggered only if my post contained the word 'curl' in it. Since I am on a virtual hosted environment, I cannot turn off mod_security or even change the rules it uses.

Here is the post http://abing.gotdns.com/200...

The work-around I have found is to wrap the words 'curl' with tags.

Re: WordPress 2.0.1 Posting Bug

Aaron — Tue, 14 Mar 2006 13:56:24 -0000

Nimrod--

The problem was fixed in 2.0.2 and the patch is not required. If you have installed WP 2.0.2 <em>and ran the upgrade script</em>, what version is your wp-admin reporting???

Re: WordPress 2.0.1 Posting Bug

Nimrod — Tue, 14 Mar 2006 04:07:07 -0000

Installed WP 2.0.2. The bug is still there. Even worse, the patch above does not work :(

Re: WordPress 2.0.1 Posting Bug

Trevor — Fri, 10 Mar 2006 01:06:58 -0000

Didn't work for me. I continue receiving stuff like this:

WordPress database error: [You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ''schroeder\') as score FROM wp_posts where id=567' at line 1]
SELECT MATCH(post_content, post_title) against ('schroeder\') as score FROM wp_posts where id=567;

WordPress database error: [You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ''don\') as score FROM wp_posts where id=567' at line 1]
SELECT MATCH(post_content, post_title) against ('don\') as score FROM wp_posts where id=567;

Re: WordPress 2.0.1 Posting Bug

Aaron — Tue, 07 Mar 2006 15:50:13 -0000

Wait a day or two. WP 2.0.2 will be out which fixes this and a bunch of other bugs.

Re: WordPress 2.0.1 Posting Bug

Stuart — Tue, 07 Mar 2006 15:40:02 -0000

Hmmm - did not work for me :(
Im getting a 500 - Internal Server Error (a wordpress one, not a real apache one). Only effects me when I try and post an entry with code in it.

Any ideas??

Re: WordPress 2.0.1 Posting Bug

Cary — Mon, 27 Feb 2006 15:58:40 -0000

Hey...thanks for the fix!

Re: WordPress 2.0.1 Posting Bug

anty — Mon, 27 Feb 2006 06:52:43 -0000

Thank you for the solution, I've already added it to my blog ;)