• Resolved tofuSCHNITZEL

    (@tofuschnitzel)


    Hi,

    it seems an update broke the Quickedit feature with products.

    if you have a product that has the status “private” and you use quickedit to untick the private checkbox and save the product is not made public.

    in the admin ajax request you can see that the post status is still sent as private even though the checkbox is unchecked.

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    Hi @tofuschnitzel!

    Thank you for reporting the issue.

    I tried to replicate this on my end, but I wasn’t able to reproduce the behavior you described. When I uncheck the Private option using Quick Edit and save the product, the product is correctly changed to Public.

    To help us investigate further, could you please:

    • Record a short video showing exactly what happens when you perform the Quick Edit? This will help us better understand the behavior you’re seeing.
    • Confirm how many products you’re trying to update. Are you Quick Editing a single product or multiple products at once? I tested this with a single product, and it worked as expected.

    Also, I’d like to better understand your site’s configuration. Could you please share the following:

    • System Status Report (available under WooCommerce > Status)
    • Fatal error logs (if any) under WooCommerce > Status > Logs

    Please upload the System Status Report to either https://pastebin.com/ or https://gist.github.com/ and share the link with us.

    Once we have this information, we’ll be in a better position to investigate the issue further.

    Thread Starter tofuSCHNITZEL

    (@tofuschnitzel)

    HI,

    interesting – I just created a fresh test-install on my localhost and it has exactly the same behaviour… the change to non-private is not saved.

    Here is the video:

    https://www.pasteboard.co/wh6X8lUDO8bv.gif

    And the System Status Report:

    https://pastebin.com/fwZu17xP

    Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    Hi @tofuschnitzel,

    Thank you for sharing the video recording and the System Status Report.

    I reviewed the video, and I can see that the Bulk Edit option is not saving the change from Private to Public on your test site.

    I also tested this again on two separate sites, but I wasn’t able to reproduce the same behavior. On my end, the change is saved successfully. Here’s a video recording of my test for reference:

    https://somup.com/cOitimVnATF

    I also reviewed the System Status Report, and everything appears to be normal.

    To help narrow this down further, could you please try the following?

    • Disable all browser extensions and then test the bulk edit again.
    • Alternatively, open your site in an incognito/private browsing window and see if the issue still occurs there.
    • Open your browser’s Developer Tools by pressing Ctrl + Shift + I (or Cmd + Option + I on macOS), then go to the Console tab. Try performing the bulk edit again and check whether any error appear. If you do see any errors, please share a screenshot or copy the messages here.

    Please let us know what you find, and we’ll be happy to continue investigating with you.

    Thread Starter tofuSCHNITZEL

    (@tofuschnitzel)

    Hi,
    I realised I have this issue only in Firefox not in Edge. Firefox even with all extensions disabled and in the private window… what browser did you use for your test?

    I will try to check the console for request details between the browser.

    Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    Hi @tofuschnitzel!

    Thank you for sharing this additional information. It’s very helpful.

    I was testing this in Google Chrome, where the bulk edit functionality worked as expected. However, after checking it in Firefox, I was also able to reproduce the same behavior you’re seeing.

    I’ve escalated this issue internally so we can get further information from our development team. Once we have an update, we’ll be happy to share it with you and guide you accordingly.

    Thank you for your patience and cooperation.

    Thread Starter tofuSCHNITZEL

    (@tofuschnitzel)

    Thanks! Great that you could confirm it!

    Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    Hi @tofuschnitzel

    You’re very welcome!

    I’ll keep you updated as soon as I receive any information from our team.

    In the meantime, I’d recommend using Chrome or Microsoft Edge as a temporary workaround until we have more information.

    Thanks again for your patience and understanding!

    Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    Hi @tofuschnitzel

    Just a quick follow-up to let you know that we’ve created a bug report for this issue on GitHub:

    https://github.com/woocommerce/woocommerce/issues/67505

    I’d suggest leaving a comment on the GitHub thread so you can receive updates and follow the progress of the issue as our developers investigate it.

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

You must be logged in to reply to this topic.