Support » Plugin: WooCommerce » WP 5.5 Update conflict

  • Resolved ardoyne12


    Woo is stating it is not compatible any longer due to the recent WP update – editing of products is frozen
    Related woo plugins are also no longer compatible
    Any advice?

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Support Austin M


    Hi @ardoyne12. We’ve had some other reports of this happening as well, although I haven’t been able to replicate it. Feel free to follow along in this thread as well, as it looks like they are reporting the same issue.

    Here are the steps I would take:

    1. Check for JavaScript errors on the product edit page. You can read about how to check for JavaScript errors using your browser of choice here. If you do find an error, please post it here (either a screenshot or just the text) so that we can take a look. If you don’t already have a screenshot service installed, here are a few options:

    There is also a walkthrough guide here:

    2. If you don’t see an JS errors, please look for fatal errors in your fatal error logs. Those would be in WooCommerce > Status > Logs in your dashboard. Once on the logs page, open the dropdown and find any fatal error logs with a date that is after the issue started happening. There could be no error logs as well, which is OK. If you do find any from after the problem started happening, could you paste them into and send us the link?

    3. If the two above steps don’t provide anything useful, then move onto full conflict testing. You can use the Health Check and Troubleshooting plugin to make this easier. The “troubleshooting mode” of this plugin will allow you to simulate how your site would look and behave with plugins disabled and a default theme without actually changing the site.

    These are the steps you should take:

    1. Back up your site. Many hosting providers offer a way to do this, and there are plugins such as WP Database Backup that offer this functionality if backing up your database through your host is not an option.
    2. Update all your plugins and your theme to their latest versions and see if the problem fixes itself.
    3. Turn on Troubleshooting Mode in the Health Check plugin by going to Tools > Site Health > Troubleshooting and clicking “Enable Troubleshooting Mode.” Then, while in Troubleshooting Mode:
    4. Make sure your theme is set to Twenty Twenty.
    5. Make sure all plugins are deactivated, and then activate WooCommerce.
    6. Repeat the action that is causing the problem.

    If you’re not seeing the same problem after completing the conflict test, then you know the problem was with the plugins and/or theme you deactivated. To figure out which one is causing the problem, reactivate them one by one, testing after each, until you find the one causing conflict.

    Ok no fatal errors since July 7th
    – Javascript Errors –
    Javascript error- DevTools failed to load SourceMap: Could not parse content – Unexpected token < in JSON at position 0

    Right now I cannot get the Site Health to operate as since the update, I cant click on any tabs, etc

    I have a support ticket into the host, but I think Im going to have to do a update rollback –

    My clients have also been forced into these updates that are wreaking havoc on all the sites that I manage/maintain/build. Most noteably, one client can no longer choose their product type (simple, variable, etc.). The dropdown menu is completely gone! @apmwebdev would love some help on getting things fixed!

    For testing, I’ve deactivated all plugins with no resolution. Changed the theme to a default WP theme, no resolution. I’ve also checked the error logs you mentioned above with no associated errors.

    This all started right after the forced WP Database update.


    Plugin Support Austin M


    @marketingclarity The issue with not being able to select the product type is a known issue, and should be solved by updating to the most recent version of the WooCommerce plugin.

    @ardoyne12 Thanks for checking for JS errors. That particular error is not something to worry about and isn’t related. If that’s the only one you saw, this probably isn’t due to something going wrong with the JavaScript on the page.

    You mentioned that you “cannot get the Site Health to operate as since the update, I cant click on any tabs, etc” Are you able to get to your system status report? You can find that by going to WooCommerce > Status in your dashboard, then clicking “Get system report,” then “Copy for support.” If you’re able to access that, can you post it? That might shed some light on what is going on. Thanks!

    @apmwebdev Yes, I was unable to navigate the admin panel 100% when I clicked on Site Health nothing would not open in order to do anything as an example – even the media library I could get to it, but once open there was a blank screen no content. Dashboard much the same, could not add any products, nothing it was a mess also kept logging me out and then denying my admin password – must have reset my password 5 times just to get in the site.
    Now when I did finally get into the System Status there where no errors nothing out of the usual at all.

    I finally just rolled WP 5.5 back to the last version – once I did that, the site became operational again
    And I ensured that the site will not automatically update as well,

    Also, what @marketingclarity mentioned is the first thing I discovered when I realized the update has caused issues – again, once I did the rollback all was well again and so far the issue is resolved

    Good luck @ardoyne12!

    Thank you @apmwebdev updating did resolve the issue. Just a note: I have WoocCommerce on multiple client websites and all of them have an error saying that woocommerce hasn’t been tested with other plugins- which is why we haven’t been updating! Happy this is working for one client now. Appreciate your time.

    Plugin Support Austin M


    @marketingclarity Great! I’m glad that solved your issue. Yes, the alert about plugins not being tested with the latest version of WooCommerce is usually not something to worry about if you’re updating your plugins regularly. Problems rarely happen for small jumps in plugin versions. They typically happen for larger jumps, like if you don’t update your plugins for a year or two and then try to update things. If you’re worried about it, though, I’d recommend creating a staging site to test updates so that you can be sure everything still works. You can read more about options for doing that here.

    @ardoyne12 Thanks for the additional details. Now that you’ve rolled back, I’d recommend updating all your plugins to their latest versions–particularly the core WooCommerce plugin–and then trying to update to WP 5.5 again. My recommendation to Jennifer about using a staging site applies here as well. This will let you test this process without fear of breaking your site.

    Plugin Support Austin M


    We haven’t heard back from you in a while, so I’m going to mark this as resolved. Feel free to start a new thread if you have any further questions!

Viewing 8 replies - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.