Support » Plugin: Elementor Website Builder » Elementor 3.05 still injects .elementor-row ?

  • Resolved ninchaaaaa

    (@ninchaaaaa)


    Hi!

    I have two websites that are using Elementor (a lot more actually, but I’m working on updates those two at the time).

    I updated a few days ago the two websites to version ^3.x on development environments.

    Since the update, I noticed from the changelog (and the broken front end :D) that modifications were made to the Elementor generated HTML (mostly removing .elementor-row from generated HTML). I made the consequent CSS fixes and updated, then everything was fine.

    The problem is that something like an hour after, I noticed that one of the two websites started back using the old injected HTML (I.E .elementor-row elements are back in the outputed HTML).

    More infos :
    – There is no cache (desactivated wp-fastest-cache)
    – The other website shows no rollback to the old structure
    – The two websites share same WP version, same theme, and something like 80% of plugins in common

    Can you provite more info about the mechanic involved to migrate to the new HTML structure? Are there any migrations helper that force the old structure in some way?

    Thanks and have a good day!
    Cheers

Viewing 2 replies - 1 through 2 (of 2 total)
  • Hi,

    This option is disabled for upgraded websites.
    The option is active by default for fresh installs.
    Go to Elementor > Settings > Advanced tab > Improved DOM Optimization
    and check the status.
    For more information about this new tool:
    https://docs.elementor.com/article/673-what-is-the-optimized-dom

    Please note that this is just the beginning. There will be further improvements to reduce the HTML markup and also to remove unused assets.

    Regarding your issue with the classes that came back, it can help if you share one of the pages with the issue, and more information about the environment of this site (exact Elementor versions used, server cache used, etc.)
    In short, there is a legacy mode that calls back the classes, but this should not happen if the “improved dom optimization” option is disabled.

    Also, the plugin cache is only one cache that affects the websites. The browser cache and the server cache also affect the websites.

    Hi,

    Thanks for your response. 🙂

    Providing the option is wonderful! Activating the option did solve the problem, now the new HTML seems to be in place on the two websites and I can’t see the old elements anymore.

    Thanks again and have a good day!
    Charlie

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.