My host says there's a bug with this plugin
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday. If you have problems with registration ask help on contact us page pleaseIf you not got email within 24~36 business hours, firstly check your spam box, and if no any email from the support there - back to the forum and read answer here. DO NOT ANSWER ON EMAILS [noreply@pluginus.net] FROM THE FORUM!! Emails are just for your info, all answers should be published only here.
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday.
I am seeing a very strange problem with this plugin when I use the Local app on my Macs (macOS Catalina and Big Sur) and push changes to my production site.
When I push any changes from Local to my production site (I always include the database) the changes undo one of the product filters. This is really bizarre and happens no matter what changes I made on Local whether WooCommerce related or not.
Specifically, what is happening is the “In Stock” filter disappears on my production site but is still visible (and functional) on the Local site. This filter can be seen at the top of the “Filter Inventory” slide-out on my store page: https://hdpowerequipment.com/inventory.
The only way for me to get the In Stock filter option back is to login to my production site and re-add it but I have to repeat this if I ever use the Local app to push changes again.
UPDATE: I deleted my entire local site & pulled down a fresh copy from my produciton site. Even though my production site has the “In Stock” filter working fine, the freshly pulled local site does NOT have the filter at all. I have to go the plugin’s options and re-add it.
I contacted my host (Flywheel) and received the below reply:
I have dug into this and I am finding an odd behavior in the database for the Woocommerce filters plugin. The plugin stores the information on that filter in the database in the wp_ge9cnxqpig_options table, with a option_name of woof_settings. The option_value for the woof_settings mentions sorting “by_instock”, but that option value seems to change when pulling down the site. This happens when we export the DB.
This type of behavior isn’t normal and wouldn’t be done because of Local. I think the plugin has a bug with how it saves data when the database is exported. I recommend reaching out to the plugin developers and letting them know about the information above.
Hello
I'm not sure if these guys got the reason.
The plugin checks if the extension is connected by the relative path to the extension. Why these keys do not match - the reason is probably that the servers use different slashes.
We will definitely check it
No idea what that means but I'm glad you're looking into it 👍
Hello
I think we will fix it in the next version.
Awesome -- thx very much.
Hello
Welcome;)
Any updates on the fix for this bug?
Hello
We are still working on a new version of the plugin (the fix will be included in the new version)
Hi there,
I see this bug is still not fixed. It is becoming very tiresome having to perform the additional login to my production site after I pushed changes with the Local app and continually having to to re-enable the In Stock filter that was disabled during the push.
Please fix this bug, it has been over four months now since I first reported it.
Hello
Please drop me exact linlk to the issue - We've fixed it! Unfortunately, we have no other options for solving this problem. Moreover, you are the only user with such an err
Hi Pablo,
The problem has not been fixed. I am seeing the exact same issue when synching the Local app to my production site. In fact, the problem happens even if I do not make any content changes within the Local app. I performed a test where I opened the Local app, select my site, did not even login, but simply pushed to production. Then I go to my production site and sure enough the in-stock filter option has now disappeared, and the only way to get it back is to login to the production siteand re-add it.
I spoke to my host about it again, and they just informed me they still believe the problem is with your plugin.
Hello
Ok! I did test on my localhost - everything works perfectly
Extensions use a key as a path from wp-content to exact extension. The extension can be disabled only if you have different folder names in the wordpress core or if you delete the key from the database
Hi, thanks for continuiing to look into this matter. I read your last answer multiple times but cannot make any sense out of it. Can you rephase your last answer into something a non-developer can understand?
Hello
Ok!
Plugin finds extension data by key. This key is formed from the names of the folders where the extension is located. an example - \wp-content\plugins\woocommerce-products-filter\ext\by_instock\
Extensions can be disabled if:
- If you changed the name of the folders
- You have deleted these keys in the database
Thanks for the reply. I have not deleted any folders or keys and I would have no clue how to do such things.
Hello
Compare folder names between two servers: \wp-content\plugins\woocommerce-products-filter\ext