Viewing 15 replies - 1 through 15 (of 48 total)
  • Same for me on a lot of websites, rollback to v3.24.0 save me!! :-((

    Yes, 3.24.1 broke the CSS on my single post pages. Pages and archives are fine.

    The single post pages are full width without any margins or padding.

    Rolling back to 3.24.0 fixes the issue..

    Same problem. Incomprehensible and quality control of zero.

    Ditto, seems to not be loading any of the css on my custom header. Looks fine in the theme builder but not on the front end.

    • This reply was modified 1 month, 1 week ago by nickmerk.

    Same issue… site is broken

    Same thing happening for me as well. And it’s a real pain because 3.23.4 has a XSS vulnerability and needs to be updated but 3.24.1 breaks the website. So either we wait for another fix, or update and then rollback to 3.24.0. And that’s not something I want to do on 100+ websites. Come on Elementor, figure it out.

    Same here, lots of broken sites spent hours trying to fix. 3.24.1 is broken and Elementor support as usual saying no issues, turn off auto updates. Really bad update and they should stop rolling it our or at least roll out a fix.

    Same for me. Updating to 3.24.1 broke my single post template.

    This is very strange because I have some sites that work, with or without cache, with or without WooCommerce, on different PHP versions. I notice less problems under PHP8.3 (9 websites).

    I confirm the broken design when updating to 3.24.1

    Same for me!

    Pulled my hair out in frustration trying to find the problem.

    • This reply was modified 1 month, 1 week ago by SietseB.
    Carlos Blázquez

    (@carlosblazquez4global)

    Hi!

    As I commented in this other thread:

    https://www.ads-software.com/support/topic/header-problem-53/#post-18012360

    I think the problem is the “search form” widget, replaced without contiunity solution by a plain “search” widget. So wherever you have an Elementor “search form” widget you will have a problem.

    Hope this helps.

    Same problem.

    Same problem.

    Same here, rolling back the regular version back to 3.24.0 seems to fix the problem (for now).

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