jezzdalgarno

Hi, here is basically what I did – if you go to your blog, to a page that contains the menu, then view the source, you may find that there is code for a menu item that you can’t see, it will show a menu_item_id, this will correspond to the spurious item that has not been deleted correctly. What I did next was to go through the WP database and remove anything that references that menu_item_id. I only found a spurious post_id and deleted references to that as well.

I don’t know if this helps, basically the problem arose because I had created a custom post type, added it to the menu, created a post based on it, then deleted the plugin. Unfortunately it did not do a good job of cleaning up after itself!

FIXED ———–

The issue was the result of using and then deleting a plugin that allows you to create custom post types and taxonomies. I had created a custom post type and then added it to the menu. Having deleted the post type and then deleting the plugin there were no traces of the menu item, however I then realised that the menu was still trying, (and failing) to create the menu item behind the scenes. Having gone through the DB and deleted every trace of the menu_item_id and post_id my admin menus page is now displaying correctly again.

I checked the PHP error log, found this:
[14-Jan-2011 08:53:58] PHP Catchable fatal error: Object of class WP_Error could not be converted to string in D:\htdocs\intranet\wp-includes\formatting.php on line 433
I think this is probably just a result of the fact the proper HTML code isn’t being generated, since line 433 is part of the function wp_check_invalid_utf8 function.