Skip Navigation

[Resolved] Toolset Views conflict with Siteground's SG Optimizer Lazyload Functioanlity

This support ticket is created 3 years, 7 months 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
8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 - -
13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 - -

Supporter timezone: America/New_York (GMT-04:00)

This topic contains 4 replies, has 2 voices.

Last updated by Timothy 3 years, 6 months ago.

Assisted by: Christian Cox.

Author
Posts
#2065455

Hi,

I was having an issue where some pages/posts were not displaying images. Upon deactivating all the plugins I found Toolset Views was causing a conflict with Siteground's SG Optimizer plugin and their Lazyload feature. I also have their Combine JS query enabled .

The console error was "Uncaught SyntaxError: redeclaration of const wpvViewHead"

Would you need me to reactivate the plugin to demonstrate the issue on my live site?

Tim

#2065795

Hello, that may or may not be necessary. Concatenating (combining), minimizing and obfuscating Toolset's JavaScript can cause some compatibility issues, so we recommend excluding a few specific Toolset files from these processes. You should be able to use SG Optimizer's configuration editor to exclude specific files. Please exclude the following files from any active Toolset plugins.

Toolset Blocks:
/wp-content/plugins/toolset-blocks/public/css/views-frontend.css

Toolset Views:
/wp-content/plugins/wp-views/public/css/views-frontend.css

Toolset Forms:
/wp-content/plugins/cred-frontend-editor/vendor/toolset/toolset-common/toolset-forms/js/conditional.js
/wp-content/plugins/cred-frontend-editor/vendor/toolset/toolset-common/toolset-forms/js/date.js
/wp-content/plugins/cred-frontend-editor/vendor/toolset/toolset-common/toolset-forms/js/main.js
/wp-content/plugins/cred-frontend-editor/vendor/toolset/toolset-common/toolset-forms/js/validation.js
/wp-content/plugins/cred-frontend-editor/vendor/toolset/toolset-common/toolset-forms/js/recaptcha-php-1.11/recaptcha_ajax.js
/wp-content/plugins/cred-frontend-editor/vendor/toolset/toolset-common/toolset-forms/js/recaptcha-v2/api.js
/wp-content/plugins/cred-frontend-editor/vendor/toolset/toolset-common/visual-editor/res/js/codemirror/lib/codemirror.js
/wp-content/plugins/cred-frontend-editor/vendor/toolset/toolset-common/res/lib/select2/select2.css

Toolset WooCommerce Blocks:
/wp-content/plugins/toolset-woocommerce-blocks/library/toolset/woocommerce-views/res/css/wcviews-onsalebadge.css
/wp-content/plugins/toolset-woocommerce-blocks/public/css/style.css

Toolset Maps:
/wp-content/plugins/toolset-maps/resources/css/toolset_maps_fixes.css

We have this list published in our FAQ document:
https://toolset.com/faq/how-to-use-optimization-plugins-with-toolset/
However, I've asked to have that document updated to remove the version numbers from each file, and to include the full file paths for all Toolset Forms assets (some are currently missing). I think the list above is a better resource for now.

Please exlcude those files isted above, clear your browser cache, and test again. If the problem persists, I'll need to take a closer look.

#2072165

Thanks, but when I deactivated and reactivated my plugins the children posts all got deleted from their parent posts. Is there anyway that can be fixed?

#2073585

Thanks, but when I deactivated and reactivated my plugins the children posts all got deleted from their parent posts. Is there anyway that can be fixed?
That is not normal, these connections should be maintained in the database when you deactivate and reactivate plugins. It's possible there is something else going on, like a JavaScript error preventing this section in the post editor screen from loading correctly. I would need to log in to take a closer look. If you share login credentials in the private fields here I can check the editor. Please let me know one parent post and one child post that should be connected.

#2075567

My issue is resolved now. Thank you!