I installed the Views and WooCommerce Views plugin updates today, and observed two immediate problems (so far):
1) I'm using a custom product layout template via WooCommerce Views. The update disabled the template and hid the WooCommerce Views item in the Toolset menu tree, so I'm unable to review or restore the setting. Backing out the WooCommerce Views update fixes the problem.
2) I have a view of products with custom CSS applied to the its content template via the Views "CSS editor" feature. Following the Views update, the CSS is no longer being applied to the view, although it looks fine in the interface and I don't see any obvious markup change that would have made it fail to apply. Backing out the Views update fixes the problem.
Hello,
They seem to be a compatibility problem with your theme files.
Please try these:
1) Make sure you have install and activate the latest version of Woocommerce Views plugin in your website, you can download it here:
https://toolset.com/account/downloads/
2) Follow our document to setup the Woocommerce Views settings:
https://toolset.com/documentation/user-guides/getting-started-woocommerce-views/
3) Also check if there is any PHP/JS errors in your website:
https://toolset.com/documentation/programmer-reference/debugging-sites-built-with-toolset/
It's not at all clear to me that the theme has anything to do with these issues.
Regarding 1): As I stated in my report, I had just updated to the newly-released versions of Views (2.8) and WooCommerce Views (2.7.9). The previous current versions (2.7.5 and 2.7.8) had been working fine with my configuration.
Regarding 2): As I stated in my report, I was already successfully using WooCommerce Views to replace the Product single-page template with a customized Toolset layout. The WooCommerce Views update not only disabled this, but also removed the WooCommerce Views item from the Toolset admin menu. To repeat: the layout still exists, but I can't see it because the system has reverted to the standard WC template, and I can no longer access the settings that would let me correct this.
Regarding 3): That was certainly worth a try, but no JS errors are being detected by the browser and no PHP errors are being logged by the server.
In the process of writing this response, I noted that you'd released Views 2.8.0.1 since yesterday's report. I applied that update, and it resolved the Views CSS problem that I reported. The remaining issue is the behavior of WooCommerce Views 2.7.9. Please take a closer look at that: why did it disable my custom Product template, and why is the admin interface to the module now missing?
Thanks.
I have a further observation about the WooCommerce Views issue. It appears that updating to 2.7.9 is consistently successful, but always leaves the plugin deactivated. This is why it doesn't appear in the Toolset menu, and would why the system reverts to using the standard Product template. Re-activating the plugin returns it to the menu, but leaves the standard Product template active (i.e. it loses the original setting that enabled the custom Product layout). Manually re-setting that returns normal operation.
I've restored and updated the system a number of times, and can report that this issue is entirely unrelated to the Views issue fixed by 2.8.0.1. Regardless of whether it's updated alone, or before or after Views, updating WooCommerce Views leaves the plugin deactivated and loses the Product template setting.
Now that I know what's going on, I can work around this problem on my client systems, but it certainly should be addressed with plugin update so that others won't have to figure this out as well.
For the WooCommerce Views issue:
I just tried the latest version of below four plugins in my localhost with a fresh wordpress installation:
- Toolset Types 3.2.7
- Toolset Views 2.8.0.1
- Toolset WooCommerce Views 2.7.9
- WooCommerce 3.5.7
It works fine, I can see the WooCommerce Views is activated, and the "WooCommerce Views" in dashboard without any problem.
All above four plugins
See screenshot: WooCommerce-Views. JPG
So it should be a compatibility/server problem of your website, if you need more assistance for it, please provide a copy of your website in below private message box, I need to test and debug it in my localhost, thanks
I agree that there's something idiosyncratic about this website, though it's not clear what it is. I've since updated a couple of similar sites from WooCommerce Views 2.7.8 to 2.7.9, and they have not exhibited this behavior.
I don't think it's worth the time for either of us to pursue it further, however. Thank you for your assistance.
