Confusing creation of containers in Elementor v4

  • Resolved VisedFAQ

    (@visedfaq)


    1 month, 1 week ago

    Hi, I was looking forward to testing v4 on the new project, but instantly stumbled upon some issues. So, I’ve started building the header and the first container is a simple block with a blue background and the email address in it, it should be “boxed”, meaning the width should be contained in 1280px.

    So, first of all, I discovered that for new v4 elements I can’t define the “container” class, and, since I have a blue background and I need padding of 20px around the container for mobile devices, I need to have another div block in place for that. So, right from the start the editing experience is more complicated than v3, because in v3 I just use a “Container” widget, which has a “boxed” or “full-width” options built in and I can define padding in it easily, so even the structure inside the editor looks cleaner:

    https://cleanshot.com/share/lPGzgTtZ

    Okay, so I’ve created a custom class “.containr” for v4 Div block where I’ve defined a custom width of 1280px, and I’ve set the margins to “auto” so it is centered. It’s reflected correctly on the editor screen:

    https://cleanshot.com/share/skhWLRrz

    However, when visiting the live page, v4 and v3 blocks look different:

    https://cleanshot.com/share/9ynzgyzB

    Look at my settings in the Elementor editor (for a custom v4 container):

    https://cleanshot.com/share/ChYW0pPR

    None of these settings are applied to the actual rendered container on the live page (padding should be 0, margin should be auto and max-width should be defined):

    https://cleanshot.com/share/FJSdpFVr

    So, not only is the process of creating a basic container is much more complicated, involves two different div blocks and much more steps, it’s not even working properly – I see different styles in editor and on front-end. And the cherry on top is that you declare v4 less bloated than v3, but if we directly compare the DOM output for my v4 and v3 solutions, you will see they are almost identical:

    https://cleanshot.com/share/4b0zLCsm

    So, what is the point of all of these “improvements” if there’s literally zero performance benefit, more friction and time spent; and it’s generally bugged?

Viewing 10 replies - 1 through 10 (of 10 total)
  • Thread Starter VisedFAQ

    (@visedfaq)

    1 month, 1 week ago

    UPD: I was able to apply the styles only when I removed the custom .containr class and applied all the necessary styles locally for a Div element, which brings another question – what is the point of the class system if it doesn’t properly work?

    Thread Starter VisedFAQ

    (@visedfaq)

    1 month, 1 week ago

    UPD 2: guys, in all honesty, this is not a Beta that can be used on production websites, this is Alpha at best. Not only the new classes I declare are not saved, I’ve just reloaded editor and both my v4 Div blocks are broken:

    https://cleanshot.com/share/XWNr7z8v

    Thread Starter VisedFAQ

    (@visedfaq)

    1 month ago

    Hello, anyone there?

    Plugin Support Rica

    (@ricav)

    2 weeks, 6 days ago

    Hi @visedfaq,

    I consulted with our developers and they confirmed that we are indeed experiencing a bug related to the issue you described.

    This has been reported to our developers, and they’re working on implementing a fix in one of the future updates. You can also follow updates and future fixes through our official Elementor Changelog here: https://elementor.com/help/elementor-products-changelogs/

    Thank you for your patience while our team works on this. We continuously strive to improve Elementor’s functionality and resolve known issues as quickly as possible.

    Please don’t hesitate to reach out if you need anything further.

    Kind regards,

    Thread Starter VisedFAQ

    (@visedfaq)

    2 weeks, 6 days ago

    Hi @ricav ,

    Glad to hear that the issue was identified by the team, please do let me know when this is fixed so I can continue with testing the new version, thanks!

    Plugin Support Soyket

    (@soyele)

    2 weeks ago

    Hi,

    As shared, This has been reported to our developers, and they’re working on implementing a fix in one of the future updates. You can also follow updates and future fixes through our official Elementor Changelog here: https://elementor.com/help/elementor-products-changelogs/

    I will go ahead and close this ticket as there is no further action required at the moment. For any new issue you are welcome to open a new ticket here.

    Regards,

    Thread Starter VisedFAQ

    (@visedfaq)

    1 week, 5 days ago

    Hi @soyele @ricav ,

    I’ve tried the new 4.0.3 version where the changelog says “Fix: Classes not saving in various scenarios – Atomic Editor”. It still doesn’t work for me. The only thing that worked for me at the moment is to allow PUT calls on the server, as described by this gentleman on your GitHub.

    The thing is – allowing PUT calls is a security risk, so maybe you should have a look into this and update the method to, for example, POST? The issue was described on GitHub in August 2025 and hasn’t been fixed since then.

    Plugin Support Milos

    (@miloss84)

    1 week, 3 days ago

    HI there,

    Thank you for sharing these details, I understand your concern, especially regarding server security and the need to allow PUT requests.

    If this issue is already reported on GitHub, please rest assured that our developers are actively monitoring and working on reported cases like this. However, I’m afraid we’re not able to provide an exact timeline or ETA for when a fix will be released.

    In the meantime, since allowing PUT requests is currently a workaround and you’ve correctly identified the associated risks, you may want to evaluate whether this temporary solution fits within your server’s security policies.

    We truly appreciate your patience and feedback, as it helps our team prioritize and improve the product.

    Thread Starter VisedFAQ

    (@visedfaq)

    1 week, 3 days ago

    Hi @miloss84 ,

    The issue is that on GitHub this request is currently in “closed” status, and since it wasn’t fixed in 6-7 months already – I doubt it will be.

    The problem is that if we don’t allow PUT request, we are essentially left without any meaningful v4 features like assigning classes and overall class management. It means that we are stuck on version 3.

    Plugin Support Milos

    (@miloss84)

    5 days, 9 hours ago

    Hi there,

    Thanks a lot for taking the time to share this, and I’m really sorry for the frustration this situation has caused.

    We completely understand your concern here. If PUT requests aren’t supported, it does block meaningful use of v4 features like class assignment and management, which is definitely not ideal.

    I’ll make sure to pass this along to our developers with proper context so they’re aware of the impact. Hopefully, this will be addressed and improved in one of the upcoming releases.

    Really appreciate your feedback and patience on this

Viewing 10 replies - 1 through 10 (of 10 total)

You must be logged in to reply to this topic.

Tags