Conflict between XPro and Formidable Pro (latest versions)

Hi. I am getting the error - Uncaught TypeError: document.forms[i].id.search is not a function - <img on all of my pages at https://mysalus.org. Looked at several similar threads but could not find an applicable remedy. I think this is XPro 2.4.5 and/or Formidable Pro v 03.04.03 related as I just noticed this in the past several days after updating both Xtheme and Formidable.

I am running WP 5.0.2 with classic editor. When checking for plugin conflicts, deactivating the Formidable Pro v 03.04.03 did make the errors disappear (Formidable Forms activated but does not seem to be the conflict). Checking themes, with FF Pro activated and 2017 theme active, the errors also disappeared. So I am thinking there is a conflict between Formidable Pro and X Pro - but have no idea as to why or how best to address.

Thoughts? Thank you.

src="//tco-forum-uploads.s3.amazonaws.com/original/3X/8/5/85c16f4d61a999de3a144368ccde4995848c2b67.jpg" width=“690” height=“485”>

Hi there,

Since you are having issues with a third party plugin, it would be best to get in touch with the developer due to the fact that there is simply no way to account for all of the potential variables at play when using another developer’s plugin or script. Because of this, any questions you have regarding setup, integration, or troubleshooting any piece of functionality that is not native to X will need to be directed to the original developer.

Thank you for your understanding.

I appreciate that you can not address third party plugins. The reason I reached out is that the Formidable Pro plugin works as it is supposed to on the 2017 theme ( common denominator for testing plugins and themes?).

Based upon testing with wp 2017 theme where errors are not thrown with Formidable Pro activated, would this not indicate that the errors are more theme related?

I plan to contact Formidable support team, but have been here before (caught between) and if I have followed the wp troubleshooting guide of identifying plugins and theme conflicts, starting with Xpro support seemed to be logical.

Any clues on what to include in my message to Formidable support? Especially if their plugin does not cause errors on wp2017 theme?

Thank you

Hi @dsthompson,

The 2017 theme is different from the X theme. The 2017 theme is a minimal one without other features that may conflict with other libraries and plugin. It shouldn’t be the basis of how the other themes should work. For example, if a plugin uses isotope library that conflicts the theme’s isotope library, then it’s only normal to have a conflict. And it can’t be compared to a 2017 theme that doesn’t use that library.

And with our theme and builder, some plugin should be integrated to work properly (like the bundled plugins and recommended plugins). Then about the formidable form plugin, it’s been added to our issue tracker and still needs review. But I couldn’t provide any workaround as a support, and it’s also a 3rd party plugin. It’s more on feature request as it may need to be integrated for it to work properly :slight_smile:

Thanks!

OK. Seems like I need to choose

Hi @dsthompson,

With the current status of Formidable Pro and X theme, I think yes, it’s unavoidable. Still, we’ll look into this and again, I can’t provide any workaround at this moment.

Thanks for understanding.

Hi. Just wanted to update this ticket and let you know that FormidablePro team (Strategy 11) let me know that they have contacted you (Themco) regarding getting a license of XPro to do further testing on their end - shich I much appreciate. Not sure how many other XPro users are using Formidable Forms, but both XPro and Formidable are foundational components of my site and I need to gain confidence that the two can work together and hope you can support their request?

Hello @dsthompson,

I’ll forward this thread to the person in charge handling the 3rd party plugins bundled in the theme. He will get in touch with Formidable Pro team shortly.

Thanks.

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.