Unable to edit priority

Hi @rosbiffer, thank you for using WooCommerce Product Tabs. Please make sure that you are using the latest version of the plugin – version 2.1.3. I tested this on my test site and I am not able to replicate the issue.

If the issue persists even if you’re using the latest version. Please disable all your other plugins and temporarily switch to the Storefront theme and see if the issue persists.

If the issue persists with all other plugins disabled and while using the Storefront theme, please get in touch with us through our Support Center so that we can investigate closer.

Let me know how it goes. – Carl

Hey Carl!

I’m having the same issue. I have a demo site with only WooCommerce, this plugin, and Storefront installed.

I update the priority and when the page refreshes the priority is still set to 0. ??

Here’s a 40-second screencast showing the issue and my status page: https://d.pr/v/3PD0Ne

Hi, @rosbiffer and @bftrick,

This issue was escalated to our team of developers. Since we are still unable to reproduce the problem and are getting the expected result, both on the back end (which properly stores the change in the priority) and the front end (where the position of the tab relative to the other tabs reflects the new value set for the priority), we kindly ask if any of you could activate WP Debugging and see if there is any error or warning popping up in the log that may explain why the priority is not stored in your configurations.

When I look at Patrick’s screencast, the only differences between his configuration and mine are:

• the server (NGINX vs Apache)
• two drop-in caching plugins (which I doubt can be responsible for this, at least on the back end)

Thanks for your cooperation on this matter.
Luigi,
Senior Developer

Wild!

I turned on WP Debug and didn’t see any errors.

But I did notice that the priority changed since the last time I logged in ??

Screencast: https://d.pr/v/AvbnQx

So maybe it does have something to do with caching? ??

I can setup a test site for a developer (with similar caching plugins installed) if you want. Contact me here if you want that: https://www.speakinginbytes.com/contact/

Hi, @bftrick,

Thanks for taking the time to run that test and confirm that caching could be an issue here. I initially doubted that just because, usually, caching plugins do not affect the back end. Nevertheless, if object caching is involved, it would make sense that records from the database are stored in the memory, causing this issue. This would also explain why, all of a sudden, you managed to store the priority value.

Another interesting test would be to temporarily disable memcache on that website and see if priority gets stored as expected at every attempt. That would be pretty conclusive about my assumption.

Anyway, you now provided us with enough information to run more tests on our end. Thanks for making yourself available to let us test this on your end: if we need that, we will let you know.

Best regards,
Luigi
Senior Developer

• This reply was modified 1 year ago by Barn2 Plugin Support.

Hello, everyone.

I can confirm this is an issue with Memcached. I have just tested this on a server with Dynamic Caching (NGINX) and Memcached and was able to reproduce the issue you reported.

The good news is that, even though the priority field shows the previous value when the page reloads upon clicking the “Update” button, the new value is actually stored in the database. It is enough to clear the cache of the server (Dynamic Cache + Memcached) and reload the page of the Tab editor (even without clicking the “Update” button again) and you will see the correct value in the priority field.

Please use this workaround while we further investigate this issue to see if it’s a transient issue that we can solve on our end.

Thanks for your patience,
Luigi
Senior Developer

Just want to confirm that this is happening with Redis Object Cache too. Priorty was always 0, even after refresh etc. I didsabled Object Cache and everything then worked as expected.

Hi @snugsite,

Thank you for confirming the conflict with the caching plugin. We will further investigate this to see if there is a workaround for it.

We will let you know as soon as we have an update.