Skip Navigation

[Resolved] Plugin conflict with Toolset and GravityPerks Populate Anything

This thread is resolved. Here is a description of the problem and solution.

Problem:
The user has found a compatibility bug between Toolset and GravityPerks-Populate Anything plugin.
The fix that the user suggests is replacing "contains" by "includes" in wp-views/embedded/res/js/views_shortcodes_gui.js line 341

Solution:
Toolset does not enqueue a new version of underscore or lodash that is causing the issue. Toolset enqueues WordPress library. The plugin was importing its own copy of lodash that is conflicting with WordPress default library. We won't fix this error.

This support ticket is created 4 years, 9 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
9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 - - 9:00 – 13:00
14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 - - 14:00 – 18:00

Supporter timezone: Africa/Casablanca (GMT+01:00)

Tagged: 

This topic contains 22 replies, has 3 voices.

Last updated by Living Passages 4 years, 8 months ago.

Assisted by: Jamal.

Author
Posts
#1578653

Morning Jamal!

I have uploaded 2 zip files to the drive folder. SQL and the wp-content directory.

#1578775

Thank you!

I escalated this to our 2nd Tier for further analysis before escalating to developers. And I will keep you informed as soon as possible.

All the best!

#1579663

With our 2nd Tier, we are still trying to understand the root cause of this issue. So far, we found that Beaver Builder does not work on the homepage, even with a default template, when the following plugins and their dependencies are activated:
Plugins:
- Views
- GP Populate Anything
- Ultimate Addons for Beaver Builder
Dependencies:
- Gravity Forms
- GravityPerks
- Beaver Builder Plugin (Pro Version)
- Types

We would like to test with the latest releases of:
- GP Populate Anything version 1.0-beta-4.52
- Ultimate Addons for Beaver Builder version 1.26.2

Can you please share these versions on the drive folder?

#1579923

latest releases uploaded.

#1588411

Hello,

According to our 2nd Tier, we won't actually fix our code to prevent this issue. We would like to have a contact email of the Populate Anything plugin authors to reach to them and suggest a proper fix.
For the moment, we think, that the plugin is not following WordPress Javascript interoperability guidelines. Lodash from the plugin should not override the global _ object.
https://make.wordpress.org/core/2018/12/06/javascript-packages-and-interoperability-in-5-0-and-beyond/

Our 2nd Tier recommends to contact all the plugins(involved in this issue) authors and let them know about this issue. If we have any contact email, we will reach to them and collaborate to fix it.

All the best.
Jamal

#1588549

Hey Jamal,

Thanks for the update.

I don't have a direct email for their support - but I could attempt to get it if you require it.
Their website where you may have luck contacting them is: hidden link

Let me know if you need anything further from me.

Thanks

#1589621
#1589625

Hello and thank you for your feedback.

Discussing this with our 2nd Tier, I am afraid, we can't do anything with the plugin's authors' website. We think that this could happen for the "Populate Anything" plugin with any other plugin that uses underscore. "Populate Anything" enqueues its own version of LoDash which is against WordPress guidelines. We believe this is a bug on the possible plugin and not really a compatibility conflict with Toolset.

Right now, we need you to report this to the theme authors and they can probably fix it, or reach to use for further assistance or copies of Toolset plugins toward testing or Toolset Integration.
Check my previous private reply(April 17, 2020 at 11:25 am), it has the email addresses of our 2nd Tier and our Support Manager, you can provide them to the plugin's authors.

All the best.

#1607333

We are also having the issue, and it is caused by the Toolset Views plugin