steve.eldridge

Michael, Yes everything appeared to disappear on the upgrade.

I have a few development servers so I’ll test it out for you.

Ok. I’m back. The reason that I thought they had disappeared is because you changed the editing tools so that you have to select a tab and then a drop-down. I see post types and taxonomies now BUT the taxonomies are no longer remembering to which post types they should associate.

So that is why I thought they were missing, they were missing from the post types taxonomy assignment and the functionality of one my sites was selecting content based on the taxonomy which caused that section of the site to fail. I will have to reassociate each taxonomy with the post types manually.

The other thing that was strange was that one of the custom post types was missing its default icon which made me think that some information was missing making the custom post types object incomplete. When I reverted to the old version the default custom post type icon reappeared, and it resumed working correctly.

I have a test server so if you want any additional information I will try to provide it for you.

Yes Michael,

This update took down at least two of my sites today. Lost the ability to manage/edit the custom post types and taxonomies.

Rolled back to previous version. On one install the site is finished with its development so I just copied your code into the functions.php, and then deleted the plug-in so that the client would not do another update that is catastrophic for their website.

I’m going to delete your plug-in on all my clients installation in the coming days to keep the sites from failing if they accidently push update.

This is a great tool but until you let us know that you’ve fixed it I’m going to try to avoid your plug-in for now.

We can agree that as WooCommerce looks at how they changed THEIR CODE that results in this error, they can escalate the issue to core for an update.

It is not unreasonable for a developer to call ‘setup_postdata()’ and should not be left to coders to solve the issue that was dismissed by @coen Jacobs:

Warnings as in the original post are probably caused by a theme or external plugin using old functions that have been deprecated for a while, which are now removed. Please verify this by temporarily switching to a default theme like Twenty Twelve.

It was not appearing in 2.0.20 and now it is appearing. The error will not appear if WooCommerce is disabled so I can only debug my code so far before I have to fix more errors in WooCommerce, and this is not the first time I’ve had to patch over their code in functions.php to fix unexpected issues.

I’ve spent many hours this week finding all the thrilling new “features” unleashed by this release. Needless to say I’m not thrilled.

@alexbaron50

I’m confirming that setup_postdata() is indeed the code that will result in the error with WooCommerce 2.2.1 enabled.

This call is used for custom queries to standardizes other WordPress calls for items like ‘the_title()’ in new query items returned.

The work around is to dig into the $post object and select items using calls like this:

$post->post_author
$post->post_date
$post->post_date_gmt
$post->post_content
$post->post_content_filtered
$post->post_title
$post->post_excerpt
$post->post_status
$post->post_type
$post->comment_status
$post->ping_status
$post->post_password
$post->post_name
$post->to_ping
$post->pinged
$post->post_modified
$post->post_modified_gmt
$post->post_parent
$post->menu_order
$post->guid

As far as I can see from the calls for the setup_postdata(), this is a WP core item and a WooCommerce ERROR. A quick Google search returns hundreds of websites that are sporting this error message in their search results. WooCommerce has made a mess out there.

Recommendation – WooCommerce needs to fix their error.

Even easier solution.

1. Select the Hosts interface in MAMP.
2. Choose the host and then look at the interface marked “Disk Location”.
3. Select the button “Permissions…”
4. Change the Owner and Group to _www.
5. Select the “Set” button and wait for the update to complete. Takes a while depending on the number of files that will be updated.

6. DONE

Your MAMP installation will not allow you to update WP and Plug-ins.

Your post is very promising, especially the part about using the correct URL rewrite.

Could you share how you got it to work?