• Resolved maryanadenia

    (@maryanadenia)


    Hi there!
    I am using the Pro version and after updating the Elementor plugin to version 3.1.0, some styles on the whole site stopped working for example pop-up forms are not called and full width does not work. Note that I am not blocking Elementor files.
    Thanks

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Gabe Livan

    (@gabelivan)

    @maryanadenia thanks for letting me know about a potential conflict between the plugins! Now, it’s difficult to guess what the problem could be without actually checking the pages themselves. Can you share them here? If you’re not comfortable making the URLs public on this forum, you can open a ticket here: https://www.gabelivan.com/contact/

    PS: I just had to debug a website using Elementor that didn’t work well. Some things from the website were messed up. The problem was that the website owner moved some CSS files from HEAD to BODY (changed the position) and this caused those CSS files to be deferred, basically, to load much later during the page rendering. One of those files was /wp-content/plugins/elementor/assets/css/frontend.min.css. The moment I moved it back to HEAD where it belongs, everything was loading back fine. Perhaps you’re having the same issue. If you have any CSS moved to BODY (especially Elementor files), move them back and see how the page loads.

    Just roll back to 3.0.10 and wait until this bug is fixed.

    Plugin Author Gabe Livan

    (@gabelivan)

    @eriksanders @maryanadenia just so everyone checking this ticket, would know (this was solved on private): the problem was not from Elementor, nor from Asset CleanUp (Lite or Pro), but from the fact that the wrong CSS/JS was unloaded in pages where it was needed.

    For instance, “wp-polyfill” (/wp-includes/js/dist/vendor/wp-polyfill.js) has been unloaded and along with it, other core files depending on it. For some reason, this file has been loaded by one of the active plugins or the theme for a certain purpose. Before unloading core files that aren’t loaded by default (e.g. I rarely noticed “wp-polyfill” loaded on most websites I’ve checked), it’s likely that it was loaded for a reason and if one thinks it was unloaded by mistake, that’s fair enough, but the browser’s console should be checked afterward for errors as well as the functionality of the page where it was unloaded.

    This was just a reminder to everyone reading this, to be extra cautious when unloading CSS/JS files, especially the core ones.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Conflict with Elementor Versión 3.1.0’ is closed to new replies.