Skip Navigation

[Resolved] Toolset View generate a conflict in backend

This support ticket is created 4 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
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 Christian Cox 4 years, 1 month ago.

Assisted by: Christian Cox.

Author
Posts
#1533031
Annotazione 2020-02-29 000342.png

The site was built 3 years ago and to manage the gallery field I have used ACF Custom Field plugin.
Now, after the last View update, I have js conflict in the backend of the post (see the attached image) that it is solved after I deactivate the View plugin.
What should I do to solve this issue?

This is the link of a backend post page: hidden link

#1534463

Hello, thanks for the report. We have had a few reports about Smush Pro compatibility in the past few days, and the error I see in this screenshot has been reported already. I will keep you posted here as I receive more information from our 2nd tier team and developers. I don't have a workaround at the moment, but if one is made available I will update the ticket here as soon as possible.

#1536439

I have deactivated the Smush Pro and all conflicts desappears.

#1536443

Thank you for the update. I will let you know as soon as I have more information to share from our 2nd tier support team and our developers regarding the plugin conflict.

#1551291

Hi, I think the Smush Pro team has released a fix for this issue, see here:
hidden link

Please update Smush Pro to the latest version and let me know if the problem is not completely resolved.

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