There were people having mm_handled errors way before 2.5 came out:
http://wordpress.org/support/topic/135740?replies=5
This is not WordPress adding these. WordPress 2.5 does not use the word “handled” anywhere at all, except in debug/display strings and in comments.
Here’s the results of a full text search in WordPress:
Searching for: handled
wp-admin\import\rss.php(25): echo '<p>'.__('Howdy! This importer allows you to extract posts from an RSS 2.0 file into your blog. This is useful if you want to import your posts from a system that is not handled by a custom import tool. Pick an RSS file to upload and click Import.').'</p>';
wp-admin\includes\dashboard.php(310): // $sidebar_args are handled by wp_dashboard_empty()
wp-admin\includes\dashboard.php(370): // $sidebar_args are handled by wp_dashboard_empty()
wp-admin\includes\dashboard.php(376): // $sidebar_args are handled by wp_dashboard_empty()
wp-admin\includes\dashboard.php(399): // $sidebar_args are handled by wp_dashboard_empty()
wp-includes\rewrite.php(882): //add in the rules that don't redirect to WP's index.php (and thus shouldn't be handled by WP at all)
wp-includes\taxonomy.php(1127): * The arguments decide how the term is handled based on the $args parameter. The following
wp-includes\js\jquery\jquery.form.js(66): * The dataType option provides a means for specifying how the server response should be handled.
wp-includes\js\swfupload\swfupload.js(898): this.debug("Error Code: Unhandled error occured. Errorcode: " + error_code);
wp-includes\js\swfupload\swfupload.js(984): this.debug("Error Code: Unhandled error occured. Errorcode: " + errcode);
Found 10 occurrence(s) in 6 file(s)
Otto: Thanks for the info. Looks like I have a difficult choice. Do a fresh install of WP 2.3.3 and have tags not work properly (display numbers and not real content, WP 2.5 was the only way I could fix the issue).
Or, use WP 2.5 and never post anything. The custom fields are only used, for me, by plugins. The main ones are Askimet and podPress. I can do without the others but those two make my blog run.
Here’s hoping someone resolves http://trac.wordpress.org/ticket/6540 so I can someday use WP 2.5.
I have just finished deleting all the custom fields via phpmyadmin. The error message no longer shows in Safari. But, and this is the odd part, it still shows in Firefox.
It is showing when WP tries to load the Categories and Advanced Options sections of /wp-admin/post-new.php
I’m not sure why but it is a predicament and quite odd.
same problem, wish there was actually a solution
I was on my way back to 2.3, accidentally uploaded the 2.5-RC1 files and the problem went away. Hoping for a swift solution though..
I’m having this problem, too.
Here’s my thoughts on this:
I moved a client from blogger to my dev-blog and everything works perfectly on wp2.5.1 … no issues including NO wayward scripts.
I then moved everything to his host (a godaddy private-label provider) and then started having problems with several things including the “unresponsive script”.
I really wonder if this an issue related to WP or something to do with the way WP is installed. On my dev-blog, I use fantastico & then use automatic upgrade plugin for my installs. On client install, a wizard/script was used.
Any thoughts?
I imported a .wxl file from a dev blog into a fresh (my first) 2.5.1 install, when things got a bit strange, custom fields wise. Also tried to import via phpmysql, which didn’t work out well. After I uploaded 2.5 and re-imported, things seem to be fine, so far. Both were on the same server though.
This started happening to me ONLY after importing my xml backup file. I’m still on 2.6 – I’ve been using WP for a year and this has never happened (and I’ve never used the Import function).
Looks like this might be the problem…
Surely there must be a way to undo it?
