Skip Navigation

[Resolved] Toolset WooCommerce Views is not working after I update WooCommerce version3.3.3

This support ticket is created 6 years, 1 month ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- - 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00
- - - - - - -

Supporter timezone: Asia/Ho_Chi_Minh (GMT+07:00)

This topic contains 2 replies, has 2 voices.

Last updated by Junichiro Taira 6 years, 1 month ago.

Assisted by: Beda.

Author
Posts
#618590
スクリーンショット 2018-02-22 19.40.59.png

I have test site using
-WooCommerce 3.3.3
-WooCommerce Composite Products 3.13.6
-Toolset WooCommerce Views 2.7.5

Here is URL
hidden link
It stops Loading...

I was able to display all until I update WooCommerce.
SO I tried several tests.

It will appear without Toolset WooCommerce Views plugin.
(But the layout is not OK.)

And also there is Warning message:
I attacked image.

I think Toolset WooCommerce Views plugin has an issue.
Would you take a look ?

#618682

On that page there is a JS error:

Uncaught SyntaxError: Invalid or unexpected token
    at eval (<anonymous>)
    at <em><u>hidden link</u></em>
    at Function.globalEval (<em><u>hidden link</u></em>)
    at Ha (<em><u>hidden link</u></em>)
    at a.fn.init.append (<em><u>hidden link</u></em>)
    at a.fn.init.<anonymous> (<em><u>hidden link</u></em>)
    at Y (<em><u>hidden link</u></em>)
    at a.fn.init.html (<em><u>hidden link</u></em>)
    at a.fn.init.$.fn.(anonymous function) (<em><u>hidden link</u></em>)
    at a.fn.init.$.fn.(anonymous function) [as html] (<em><u>hidden link</u></em>)

It should be related to On Sale badges.

The PHP error instead, that is related to our Installer, which expects a valid array in that line of code.
I see you use a Toolset Starter Child Version, and if you did not alter the Child Version we provide (not remove anything), then this should not happen.

Can I know where you can see the warning exactly?

For the JS error, this seems some compatibility issue introduced eventually during the last updates.

You mention that this is still replicable with Toolset and WooCommerce, but I cannot replicate such a situation locally with those plugins.

I assume I need some addon Plugins or specific settings.

Can you illustrate how to replicate this problem, or eventually provide me with a Copy of a site where you replicated this using the minimal setup you mention?

I can then help to solve it.

Online it is difficult to debug this - I cannot run the Debug Tools, and the website is in Japanese, I would prefer not to alter that on the website directly.

#619267

Thank you so much! I could figure out.

This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.