Skip Navigation

[Resuelto] Toolsets maps provoca un conflicto con Variation Swatches and Photos

This support ticket is created hace 4 años, 5 meses. There's a good chance that you are reading advice that it now obsolete.

Este es el foro de soporte técnico para Toolset: un paquete de plugines para el desarrollo de sitios WordPress sin escribir PHP.

Cualquier persona puede leerlo, pero solo los clientes de Toolset pueden publicar en este foro. El soporte de Toolset atiende 6 días a la semana, 19 horas por día.

No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.

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 7 respuestas, has 2 mensajes.

Last updated by Christian Cox hace 3 años, 5 meses.

Assigned support staff: Christian Cox.


Hi. Since the last update of views, there is a conflict with Variation Swatches and Photos (woocommerce). I have to disconnect the toolset maps so I can work normally. I made a video, so you can see it better.

hidden link



Hi, I'm not able to replicate the same problem on my own local site with just Toolset, WooCommerce and WooCommerce Variation Swatches and Photos active, so there must be something else going on. Can you try these troubleshooting steps?
- Temporarily deactivate all plugins except Toolset, WooCommerce, and WooCommerce Variation Swatches and Photos
- Temporarily activate a default theme like Twenty Nineteen
- Test again. If the problem is resolved, reactivate your theme and other plugins one by one until the problem returns.
- If the problem is not resolved, please open the browser console and watch for any JavaScript errors that appear when you try to open the swatch tabs.

Please let me know the results and we can go from there.


Hello Brian.

I have also created a copy of the Artikalia website so you can work with peace of mind. I have disconnected the plugins and there are only Toolsets, Avada and the Swatches plugin.

The access data is exactly the same as I gave you previously. Only change the url.

hidden link

Feel free to work with peace of mind and perform the necessary tests.

A product in which you can do tests is this:

hidden link

Effectively the console shows a problem in javascript between both plugins.

I await your news

Thanks for your help


Okay this is strange. Go to Avada > Theme Options > Privacy, then choose:
Privacy consent: OFF
Privacy bar: OFF
The problem is resolved. Not sure what's going on here so I'm asking my 2nd tier support team to look into this. I'll let you know what I find out.


Hello Brian. It is disconnected, but it still does not work. From what little I understand of the console, the conflict seems to be with the java of vpv addons maps.js and also with some more toolsets and the plugin itself.


Hello Brian. Sorry, I'm looking to go to the page you go, pages, entries, products, always leave the same javascrip errors. There is something that clearly is not working well.


Hello Brian, I have asked my 2nd tier team for some additional information and I will update you soon.


Hi, just a quick update to let you know our contact at Avada has assured us this issue will be resolved in an upcoming release of their theme. Since the fix needs to be applied in their codebase, we will consider the matter closed here. If you continue to experience issues, we recommend filing a ticket with Avada for this JavaScript error in wp-admin:

Uncaught ReferenceError: google is not defined
    at new WPViews.ViewAddonMaps (wpv_addon_maps.js?ver=2.0.2:15)
    at HTMLDocument.<anonymous> (wpv_addon_maps.js?ver=2.0.2:1543)
    at i (load-scripts.php?c=1&load[chunk_0]=jquery-core,jquery-migrate,underscore,shortcode,utils,backbone,wp-util,wp-backbone,media-models,moxiejs,plupload,wp-plupload,jqu&load[chunk_1]=ery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable&ver=5.4:2)
    at Object.fireWith [as resolveWith] (load-scripts.php?c=1&load[chunk_0]=jquery-core,jquery-migrate,underscore,shortcode,utils,backbone,wp-util,wp-backbone,media-models,moxiejs,plupload,wp-plupload,jqu&load[chunk_1]=ery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable&ver=5.4:2)
    at Function.ready (load-scripts.php?c=1&load[chunk_0]=jquery-core,jquery-migrate,underscore,shortcode,utils,backbone,wp-util,wp-backbone,media-models,moxiejs,plupload,wp-plupload,jqu&load[chunk_1]=ery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable&ver=5.4:2)
    at HTMLDocument.J (load-scripts.php?c=1&load[chunk_0]=jquery-core,jquery-migrate,underscore,shortcode,utils,backbone,wp-util,wp-backbone,media-models,moxiejs,plupload,wp-plupload,jqu&load[chunk_1]=ery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable&ver=5.4:2)

Their privacy scripts should not be triggered in wp-admin, only on the front-end of the site.