[Forminator Pro] Elementor issues

When I use the plugin or activate the elementor plugin it stops working.

  • Adam
    • Support Gorilla

    Hello Damian

    I hope you’re well today and thank you for your question!

    We don’t have any reports currently on Forminator stopping Elementor and I just tried replicate that on my own setup but they both are working fine there together.

    That would mean that it’s either something specific to this particular site or it’s an issue that we are not yet aware of. I would like to check it to see what might be causing it and how to fix it.

    To let me take a closer look, would you please enable support access to the site? To do so, please go to the “WPMU DEV -> Support -> Support Access” page in your site’s back-end and click on “Grant support access” button there.

    Let me know here once it’s done please, as I won’t be notified automatically. I’ll then access the site and investigate the issue so we could find solution to it.

    Best regards,
    Adam

  • Adam
    • Support Gorilla

    Hi Damian

    Thank you for enabling access!

    I checked the site and I can see the issue there. With Forminator enabled there’s also an “Internal Server Error 500” happening on one of admin-ajax calls and this seems to be related.

    Such error is usually related to either resource issues or to a conflict on site. There’ll be more testing necessary to pinpoint the problem then.

    The first thing to check would be WordPress debug output and since I don’t have any way to do it via support access, I’d like to ask you for a bit more help:

    1) please access your WP installation using either FTP or cPanel “File Manager” and add following lines to the “wp-config.php” file, right above the “/* That’s all, stop editing */” line

    define( 'WP_DEBUG', true );
    define( 'WP_DEBUG_LOG', true );
    define( 'WP_DEBUG_DISPLAY', false );

    Once they are there, enable Forminator again and try to edit some page with Elementor a few times. After that look into the “/wp-content/” folder on your server for the file named “debug.log”.

    Please download that file, upload it to some file storage of yours (like your Dropbox, Google Drive or similar account) and share direct link to it with me here.

    2) Could you please run a plugin conflict test too?

    – disable all the plugins except for free Elementor (so disable Pro but keep the basic one) and except Forminator
    – see if the issue is still happening
    – if it’s not happening, start enabling all necessary plugins back one by one after each one testing for the issue

    At some point it should start happening again and the last enabled plugin would be our culprit.

    Together with debug.log it should, hopefully, tell me what exactly is causing the issue and I’d look for a way to fix it (if necessary, I’ll include our developers in the case).

    Best regards,
    Adam

  • Adam
    • Support Gorilla

    Hi Damian

    Thanks for sharing the log.

    There’s an important event logged that seem to be related, that is a Fatal Error stating that there was insufficient memory available – that Elementor tried but wasn’t able to allocate more than 256M.

    However, that’s often a case of some additional conflict or “flow”. Yet, the first thing to check would be memory.

    Could you please go to “WPMU DEV -> Support -> System Information -> PHP” page and check the current value for “memory_limit”?

    If it’s higher than 256M (let’s say for sake of below example that it’s 512M) then edit your “wp-config.php” file and add this line right above the “/* That’s all, stop editing */” line

    define( 'WP_MEMORY_LIMIT', '512M' );

    Note please: there should only be one like like this so if there’s already one that sets WP_MEMORY_LIMIT to 256M simply edit it.

    After that check if issue is solved. If not it would confirm that the issue is related to some additional conflict and we’d need to identify that. In such case, could you please enable support access to the site for me again?

    Update me here, please, once it’s done.

    Best regards,
    Adam