Sold Individually Meta Key reverts to no by itself

  • Resolved structuraldetails

    (@structuraldetails)


    4 months, 1 week ago

    Hi there,
    Following the last update, I noticed that some of my products started showing the quantity field even though I have the SOLD INDIVIDUALLY option checked on all of my products since they are digital downloads. In the database table postmeta, the meta key _sold_individually should be set to yes.
    I noticed that for those random ( only a few ) products this option was turned off.
    So, I turned the option on ( by visiting the edit product backend and checked the sold individually option in the inventory tab ) and then after a few hours I noticed that some other products showed the same issue ( random products and only a few at a time ).

    This happens every few hours, for random products and only 1 or 2 at a time. For some reason the meta key value for _sold_individually changes from yes to no. I am not able to pin point the source of this problem. It happens without making any changes/updates or anything else.

    Please help!

Viewing 4 replies - 1 through 4 (of 4 total)

  • Hey there, @structuraldetails! Thanks for contacting us. I’m happy to help you.

    To help pinpoint what is happening, can you please follow the steps below?

    • Create a staging site (you can ask your host if they offer this service, or you can use WP Staging for quickly spinning up a new test site.)
    • Switch the theme to Storefront
    • Deactivate all plugins but WooCommerce (no other exceptions, this includes deactivating plugins that add custom code or page builders)
    • See if the issue happens on the staging site after waiting the usual time it takes on the live site

    Please let us know how it goes.

    Looking forward to your reply.

    Have a wonderful day!

    Thread Starter structuraldetails

    (@structuraldetails)

    Hi again,

    Something really strange is going on here and I would appreciate any type of help or ideas.

    So I have created a cloned staging site ( exactly the same ) as the live site. The problem is that the problem is not happening here.

    I am completely buffled and clueless of how to find and resolve this problem.

    anastas10s

    (@anastas10s)

    That’s great to hear! Thanks for letting us know the issue is no more on the cloned staging site.

    How about making the issue appearing on the live site a thing of the past?

    Big fan of Alexander the Great’s solution to the Gordian Knot here, therefore, I’d like to propose the following:

    • Make sure there is a backup available, with a solution like?Jetpack VaultPress Backup
    • Create a?fresh/new?WooCommerce site, where WooCommerce and its database will both be at the latest version available – along with everything else being tip-top (I assume this is the staging site already mentioned here, where the sold individually option is working as expected)
    • Use the backup created in the first step, to?restore the site’s data, thus having a perfectly functioning store again

    Bonus: having a round-the-clock backup solution, keeping a log of every change, making future restores a breeze.

    Sidenote: I assume the priority is to have the required setting work as expected again ASAP, over investing further time to discover the culprit of this persistent behavior on your site.

    I hope that helps! Let us know how it goes.

    Thread Starter structuraldetails

    (@structuraldetails)

    The problem was with Woocommerce Paypal Payments plugin.

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

Tags