Strange behaviour conflict with Caldera Forms Plugin

Resolved shaunbowen
(@shaunbowen)

7 years, 4 months ago

Hi there, I have noticed a strange behaviour that occurs when I activate Yoast SEO on any site with Caldera Forms and SiteOrigin Page Builder also installed.

Ordinarily Caldera forms will give every instance of the form on a page a unique ID, appending _1, _2, _3 to the end according to how many times the form is embedded on a single page.

Obviously most people will only put their contact form on a page once, so the ID will generally be #XXXXXXXX_1. However, when activating Yoast SEO, Caldera Forms thinks there are 3 instances of the form on the page and appends a _3 to the form ID.

As soon as I deactivate Yoast, the form will return to an ID with _1 on the end.

This is a problem, because there may be styles and items that target forms depending on the unique ID, which are then broken once Yoast is activated. The Caldera Forms Anti Spam plugin is one example, which no longer functions when Yoast is active.

Viewing 6 replies - 1 through 6 (of 6 total)

Jerlyn
(@jerparx)

7 years, 4 months ago

While we are not familiar with the plugin you are using, can you please guide us step-by-step on how we can replicate the issue?
Also, can you confirm if the same issue happens with everything updated to the latest version (WP, Yoast SEO 9.4, Caldera Forms, SiteOrigin Page Builder)?

Thread Starter shaunbowen
(@shaunbowen)

7 years, 4 months ago

Okay, to replicate this you need to install all the plugins above to a fresh WordPress install: Yoast, Caldera Forms and SiteOrigin Page Builder. Then create a page with a SiteOrigin row and two columns and add a caldera form to one of the columns.

You’ll see that the Caldera Form gets an ID with _3 appended to the end, even though it is the only form on the page and should therefore only have _1. If you create a page using the normal editor (ie. With no pagebuilder layout), the problem goes away and the form ID ends in _1 as intended.

I tried updating all plugins and WP to the latest versions but the error persists.

I added a different SEO plugin as a test and the problem no longer happens.

Plugin Support amboutwe
(@amboutwe)

7 years, 4 months ago

Based on the information you provided, we expect this to be a bug but are unsure if it’s something in our plugin or an integration with the other two plugins. We’re actively using the bug tracking on our GitHub repository so your best next step would be to create a new issue for our developers here. You will need an account to create a new issue. Don’t forget to include the URL to this conversation in your bug report.

As the issue is a conflict with other plugins, we highly recommend reporting the issue to the development or support team of the other plugins. Having both teams work on the issue is a benefit to you.

If you have not submitted an issue previously, this guide will help you submit a complete report which may result in a faster resolution.

Thread Starter shaunbowen
(@shaunbowen)

7 years, 3 months ago

Thanks for the reply, I have posted on the support forums for the other plugins too so hopefully someone will be able to spot where the error is.

devnihil
(@devnihil)

7 years, 3 months ago

@shaunbowen Thanks for also reaching out to the other plugin developers. Please let us know if we can be of any more assistance.

Plugin Support amboutwe
(@amboutwe)

7 years, 3 months ago

This thread has been marked as resolved due to lack of activity.

You’re always welcome to re-open this topic. Please read this post before opening a new request.

Thanks for understanding!