Conflict with Forminator Plugin

  • Resolved harpo1984

    (@harpo1984)


    5 years, 5 months ago

    Hi Site Origin,

    There is a plugin conflict between Forminator and the SiteOrigin Page Builder. When inserting a Forminator shortcode, the form does not display.

    If I preview the Forminator shortcode inside the Site Origin Page Builder, there are no issues, but as soon as publish the change and view the live page. The form will not show.

    I have tried the following workarounds:

    1. Turn off “Automatically add paragraphs in the Site Origin Editor Widget”
    2. Insert following code into CSS: .forminator-custom-form { display: block !important; }

      3. However, none of these work.

      I have a staging site and changed the theme to Twenty Nineteen but still, the form would not display. It will only display when the Site Origin plugin is disabled which is not possible.

      Interestingly, when I look at the code in the WordPress Classic Editor after disabling Site Origin in the staging website, I can see the following has been wrapped around the Forminator shortcode:

      <div id="pg-884-5" class="panel-grid panel-no-style">
<div id="pgc-884-5-0" class="panel-grid-cell" data-weight="1">
<div id="panel-884-5-0-0" class="so-panel widget widget_sow-editor panel-first-child panel-last-child" data-index="6" data-style="{&quot;background_image_attachment&quot;:false,&quot;background_display&quot;:&quot;tile&quot;}">
<div class="so-widget-sow-editor so-widget-sow-editor-base">
<div class="siteorigin-widget-tinymce textwidget">

[forminator_form id="2546"]

</div>
</div>
</div>
</div>
</div>

      I am assuming it’s this code that is causing the issues.

      Kind regards,

      Simon

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Support Andrew Misplon

    (@misplon)

    Hi Simon

    Thanks for posting.

    I’ve tested a basic form and it seems to insert normally using a Text or SiteOrigin Editor widget. To troubleshoot the problem, try the inverse of the test you’ve already run. Test with only Forminator, Page Builder by SiteOrigin and the Classic Editor plugin if in use. Temporarily deactivate all other plugins. In this state, insert your shortcode into a Text widget and re-test. If the issue persists, leave the plugin setup as described and also switch to a default theme like Twenty Nineteen. The goal is to try find a working baseline.

    Thread Starter harpo1984

    (@harpo1984)

    Hi Andrew,

    Thanks for the swift reply.

    I’ve carried out your reverse tests and can confirm the conflict is with Yoast SEO and the SiteOrigin page builder. If I deactivate Yoast SEO the shortcode for Forminator works no problem.

    Yoast SEO and Forminator work fine on other sites that don’t use the SiteOrigin Page Builder, so it’s definitely not a conflict between Forminator and Yoast SEO.

    Kind regards,

    Simon

    Plugin Support Andrew Misplon

    (@misplon)

    Hi Simon

    Thanks for your feedback. I can make use of all three plugins together. Here is how that looks: https://imgur.com/a/oxgjKrS.

    Did you make use of Twenty Nineteen while running the previous test?

    What you can try doing now is start checking for errors. Here is how you can check for JS errors: https://www.ads-software.com/support/article/using-your-browser-to-diagnose-javascript-errors/#step-3-diagnosis

    Thread Starter harpo1984

    (@harpo1984)

    Hi Andrew,

    Yup, I tested with the custom theme and Twenty Nineteen. There are no console errors showing in the Twenty Nineteen theme when all three plugins are active together.

    If I deactivate Yoast SEO everything works fine and the form shows.

    Here is the server info:

    Server architecture Linux 3.12.18-clouder0 x86_64
    Web server Apache/2.4.39 (Unix) mod_hive/6.25 OpenSSL/1.0.1e-fips mod_fastcgi/2.4.6
    PHP version 7.2.19 (Supports 64bit values)
    PHP SAPI cgi-fcgi
    PHP max input variables 6000
    PHP time limit 300
    PHP memory limit 768M
    Max input time 1000
    Upload max filesize 32M
    PHP post max size 32M
    cURL version 7.59.0 OpenSSL/1.0.2r
    Is SUHOSIN installed? No
    Is the Imagick library available? No
    .htaccess rules Custom rules have been added to your .htaccess file.

    Kind regards,

    Simon

    Plugin Support Andrew Misplon

    (@misplon)

    Thanks. Please, try enabling WP_DEBUG and WP_DEBUG_LOG in your wp-config.php file located in the WordPress root. Recreate the issue then check the debug.log file in the /wp-content/ folder to see if there is anything relevant printed.

    https://codex.www.ads-software.com/WP_DEBUG

    Additionally, please check the shortcode in a Text widget in a new Page Builder page.

    Please, also export the form and upload it to Dropbox/Drive or WeTransfer and send me the link. This is the first time I’ve installed Forminator, I assume exporting is supported.

    Plugin Support Andrew Misplon

    (@misplon)

    Please, also confirm if you’re using Yoast SEO free or if you have the premium version. And is Forminator the standard version or is there a pro/premium version in use?

    Thread Starter harpo1984

    (@harpo1984)

    Hi Andrew,

    No errors show in the log file.

    I checked in a new page builder page and it will not work with Yoast enabled. It’s the Free version of Yoast being used. The shortcode won’t work in the Text Widget or SiteOrigin Editor Widget.

    Additionally using a Forminator widget also doesn’t work while Yoast and SiteOrigin are enabled together.

    The free version of Forminator from www.ads-software.com is being used, although there is currently no difference between the Free and Pro versions.

    Here is the link to the export with Firefox send: Form Export

    ( The file will expire after one day or two downloads, whichever comes first )

    Kind regards,

    Simon

    Plugin Support Andrew Misplon

    (@misplon)

    Thanks. If you deactivate Load form using AJAX in the Behavior section, the form should load. Let me know how that goes.

    Thread Starter harpo1984

    (@harpo1984)

    Hi Andrew,

    That solved the issue.

    So where does that leave us? Is it a conflict then between all three plugins?

    Thanks so much for the swift help!

    Kind regards,

    Simon

    Plugin Support Andrew Misplon

    (@misplon)

    Super, glad that helps. For the moment, we’ll need to call this a limitation. We’re a very small team, operating with limited resources. As a result, support and development time has to be assigned quite carefully. If more users report this issue and request that this problem be resolved, we can then look at assigning development time. I’d love to assign that time now but due to the limitations we operate under, it isn’t possible until the problem is more severe and the number of impacted users is greater. I’ll log this on GitHub shortly as plugin conflict. WPMU might be able to take a look, it would be awesome if you can also report this issue to them.

    Plugin Support Andrew Misplon

    (@misplon)

    Issue logged here: https://github.com/siteorigin/siteorigin-panels/issues/679. Thanks for reporting.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Conflict with Forminator Plugin’ is closed to new replies.