Quote from Alex Dev on November 9, 2026, 18:58
Hello
Thank you for the report.
I have just checked it on our test server with the latest BEAR version, and editing and saving fields works as expected there: the new values stay after the page is reloaded. So something specific to your site is getting in the way, and I need a few details to find it:
1. Your BEAR version, and your WordPress, WooCommerce and PHP versions.
2. Which fields do not save: all of them, or only some (for example price, stock, title, categories)? Simple products, variations, or both?
3. Do you edit directly in the table cell, or through Bulk Edit?
4. Do you use a persistent object cache on the site, such as Redis or Memcached (often enabled by the hosting or by plugins like LiteSpeed Cache, W3 Total Cache or Redis Object Cache)? An object cache can keep serving the old values after the new ones are saved. If you have it, please flush it, or switch it off for a moment, and try again.
It would also help a lot if you record a short screen video: open BEAR, edit one field, wait a few seconds, reload the page and show that the old value is back. If you can, open the browser console (F12, Console tab) before editing, so any red errors are visible in the video.
You can share the video link in the private area of this ticket.
Best regards,
Alex
Hello
Thank you for the report.
I have just checked it on our test server with the latest BEAR version, and editing and saving fields works as expected there: the new values stay after the page is reloaded. So something specific to your site is getting in the way, and I need a few details to find it:
1. Your BEAR version, and your WordPress, WooCommerce and PHP versions.
2. Which fields do not save: all of them, or only some (for example price, stock, title, categories)? Simple products, variations, or both?
3. Do you edit directly in the table cell, or through Bulk Edit?
4. Do you use a persistent object cache on the site, such as Redis or Memcached (often enabled by the hosting or by plugins like LiteSpeed Cache, W3 Total Cache or Redis Object Cache)? An object cache can keep serving the old values after the new ones are saved. If you have it, please flush it, or switch it off for a moment, and try again.
It would also help a lot if you record a short screen video: open BEAR, edit one field, wait a few seconds, reload the page and show that the old value is back. If you can, open the browser console (F12, Console tab) before editing, so any red errors are visible in the video.
You can share the video link in the private area of this ticket.
Best regards,
Alex