Milos

Hi there,

Thank you for contacting us.

Here you have documentation related to the user role feature.

https://elementor.com/blog/wordpress-user-roles-elementor-role-manager/

Hope this helps.

Dear Customer,

Thank you for reaching out to us and for providing such a detailed description of the issue. We completely understand your frustration here, as dealing with overlapping plugin functionalities can be incredibly tedious, especially when you are trying to clean up your site and avoid relying on temporary “patch” plugins. Since your MailPoet popup works perfectly on a standard WordPress test page, it is clear that the core integration is functioning correctly. The issue lies in how Elementor optimizes and loads code, which ultimately blocks the script triggers for MailPoet specifically on pages built with the page builder.

The primary reason for this behavior usually stems from the advanced optimization features included in Elementor version 4.0.9 Free. While these features are designed to boost your site’s loading speed, they achieve this by delaying script execution or restructuring the underlying HTML markup of the page. When Elementor alters this structure or delays element rendering, MailPoet’s initialization script essentially misses its cue to fire because it cannot detect the expected page layout in that split second. To resolve this, we recommend navigating to Elementor, then Settings, and clicking on the Features (or Experiments) tab in your WordPress dashboard. From there, try changing the status of
Improved Page Actions Layout and Optimized Markup to Inactive, as turning these off usually restores the necessary paths for third-party scripts immediately.

Another common culprit could be the specific page layout template you are using within Elementor. MailPoet relies on standard WordPress hooks located in the site’s footer to inject and trigger its popup code globally. If your homepage or other affected pages are set to the “Elementor Canvas” template, Elementor completely strips away your theme’s native header and footer, which accidentally removes the hidden code MailPoet needs to display the form. We highly recommend checking the page settings for your homepage to ensure the layout is set to “Elementor Full Width” instead, which keeps your theme’s essential hooks intact while still allowing you to design with Elementor.

If all of these settings are already correct and the issue persists, it means Elementor is finishing its page layout rendering only after MailPoet has already attempted and failed to launch the popup. To bridge this timing gap, you can add a tiny code snippet to your site’s footer via a child theme’s functions.php file or a code snippets plugin. This script listens for Elementor to finish initializing and then forces MailPoet to check the page for popups half a second later:

JavaScript

jQuery(window).on('elementor/frontend/init', function() {
    setTimeout(function() {
        if (typeof MailPoet !== 'undefined' && typeof MailPoet.InitializePopups === 'function') {
            MailPoet.InitializePopups(); 
        }
    }, 500);
});

Hope this helps,

HI there,

I completely understand your frustration, especially considering how long the issue has been open and the fact that the root cause appears relatively straightforward once identified.

Unfortunately, from the support side, we don’t have direct visibility into the internal development prioritization process or the technical complexity behind the final implementation and testing requirements. That said, I absolutely agree that the issue has been lingering for too long without a proper resolution.

I’ve added your findings and feedback to the internal report specifically highlighting the reproducibility and the apparent root cause you identified. Hopefully, this helps move the issue forward faster.

And thank you again for taking the time to investigate and share the details.

Kind regards,

Hi there,

VIdeo – https://www.loom.com/share/573d9709aac3425abd9fc4d443bac4bf

Since you are an Elementor Pro user, you can open a support ticket at my.elementor.com ref: https://elementor.com/help/how-to-submit-a-support-ticket/ I’d also suggest you check out Elementor Community Group on Facebook.

We have created it to connect Elementor users together and share knowledge, Global Elementor Community.ww.wp.xz.cn rules state that commercial products are not supported here.

Hi,

Thanks for reaching out.

From what you described, this sounds like a responsive layout issue rather than a problem with Elementor itself. The desktop layout can look correct, but mobile often needs separate adjustments for spacing, positioning, section height, column order, margins, and padding.

In particular, I would recommend checking whether the CTA button or images are using absolute positioning, negative margins, or fixed section heights, as these can cause elements to overlap or get cut off on mobile devices.

Please review the following Elementor documentation and guides on creating responsive websites:

• https://elementor.com/features/responsive-design/
• https://elementor.com/blog/responsive-website/
• https://elementor.com/blog/elementor-responsive-webdesign-principles/

Best regards,

Hi there,

Thank you for contacting us.

You can check this documentation about global site settings:
https://elementor.com/help/global-layout-settings/

I hope this helps.

Hi there,

Thanks for contacting us and hope you are doing well and having a great day.

To rule out the possibility of a plugin or theme conflict, please deactivate all your plugins not just elementor addons (besides Elementor). If it solves the issue reactivate them one by one to find the culprit. If it didn’t help, switch your theme (temporarily) to a default WP theme such as Twenty Nineteen and see if it makes any difference.

Also, this could happen due to our Elementor performance experiments you can try to deactivate them. To deactivate them you can go to Elementor > settings > features

Performance features currently in the experimental stage are:
Element Caching – Elements caching reduces loading times by serving up a copy of an element instead of rendering it fresh every time the page is loaded. When active, Elementor will determine which elements can benefit from static loading – but you can override this.
Inline Font Icons – This experiment renders icons as SVGs without loading the Font-Awesome and eicons libraries. Since SVGs are vector-based images which are rendered using the browser’s engine, they do not increase server requests which improves performance

I am looking forward to hearing back from you soon.

Kind regards,