AJAX is teh b0rked when adding categories.

Cannot reproduce as of [7412] using Safari 3.1 or Firefox 2.0.0.12 (both OS X 10.5.2). Server environment is Apache 2, PHP 5.2.4

Please re-open with more details about your server/browser environment. Please try it with ALL plugins disabled.

I just tested this locally and it seems to work fine (on Mac OS X Leopard with MAMP, with no plugins). I just tested it again on the same install, with the same settings (on my actual website), and it still said "AJAX is teh b0rked" but once I refreshed it, all the categories disappeared! I refreshed again, and all the categories reappeared, including the one I was trying to make when "AJAX was b0rked". Here's a little info that might be useful to find the problem:

I'm running Apache/2.0.54, php 5.2.5, mysql 4.1.11.

christhompson, what WordPress version/revision?

Try disabling JavaScript? in your browser and then add a category from Manage -> Categories. What happens?

Trunk adds some extra error checks to help isolate the problem. If you're using svn, update and trying adding a category. Do you see "Could not insert term into the database"?

Indeed. I'm having this happen on a client's install.

wp-ajax-response-debug.php

A plugin that will output the parsed data of any XML response resulting from a WP AJAX request (see attached screenshot). Upload it to your wp-content/plugins/ directory and activate it from your WordPress' Plugins admin page.

Tested in FF2, Safari3, Opera9, IE6/7

example output of attached plugin

mod_security problem, perhaps?

having the same problem here (FF3b4, Safari 3.1, MaxOSX 10.5.2). When switching of Javascript i get "Category not added" instead without any other visible error/problem. I switched off all plugins and still get the same error. Probably something server related. Can't say too much about installed modules as this server isn't my own. Will try another install on a local test machine.

Check error logs to see if anything is being output there, particularly database error related stuff.

"Lost connection to MySQL server during query"

That error was reported on the testers list. Seems related to the "gone away" errors from #5951 that people worked around by using mysql_ping(). I'll create a mysql_ping() patch to wpdb to see if that helps.

If a query errors out with a CR_SERVER_GONE_ERROR or CR_SERVER_LOST errno, two attempts are made to mysql_ping() and reconnect. If successful, the query is done again, otherwise we bail.

Modified wp-db.php attached for those who don't have patch handy.

Seems to have worked, but it's REALLY slow (like 10-30 seconds).

Also:

Warning: mysql_ping() expects parameter 1 to be resource, boolean given in [...]

Looking at the patch $this->dbh can only be a bool if the mysql_connect fails - I assume it's the reconnect that fails.

Update patch to not ping if the reconnect fails

Update wp-db.php to not ping if the reconnect fails

I've attached a new patch (or wp-db.php) for people to try which won't ping if the reconnect fails.

Works, but still a horridly long page load. Takes exactly 30 seconds to get the AJAX response (same for non-AJAX). Seems some timeout is occurring and it takes 30 seconds before it gives up.

(In [7481]) Make sure IDs are >= 0. see #6305

I looked at differences between how categories are created from Write->Post versus Manage->Categories. Manage->Categories allows parent IDs of -1 to be passed down. The commit above changes negative IDs to zero just in case negative IDs are somehow responsible.

(In [7483]) Make sure cat parents are >= 0. see #6305

Indeed they were. Totally blazing fast as of the current SVN version. Woot!

Er, I probably shoulda waited for confirmation from others before closing. Someone reopen this if it didn't fix it for you.