• Hi Elementor Team,

      I am facing a frontend rendering issue on my Elementor homepage.

      Current behavior:

      • Elementor editor works normally
      • The page and sections display correctly inside Elementor editor
      • Frontend becomes blank or fails rendering on the live homepage
      • The issue appears connected to one older HTML-heavy imported section

      Important findings:

      • Newly built native Elementor container sections work correctly
      • When the older imported HTML-heavy section is removed, frontend starts working normally again
      • This suggests the issue is isolated to that specific section/container structure

      Additional observations:

      • Larger custom HTML/CSS sections seem to trigger the issue more frequently
      • Elementor editor preview may still display correctly while the live frontend fails
      • Native Elementor widgets/containers appear stable

      What I already tested:

      • Regenerated CSS & Data
      • Switched between Elementor Canvas and Full Width
      • Cleared Astra header/footer conflicts
      • Cleared cache
      • Tested clean native Elementor sections
      • Isolated the problematic section

      Possible causes:

      • corrupted Elementor container/widget data
      • invalid flexbox/container structure
      • broken generated CSS/assets
      • rendering conflict from HTML-heavy Elementor section

      Would appreciate guidance on:

      • identifying the corrupted section
      • repairing container structure
      • fixing frontend rendering
      • regenerating valid Elementor assets

      Thank you.

      • This topic was modified 1 day, 18 hours ago by naresh73.

      The page I need help with: [log in to see the link]

    Viewing 5 replies - 1 through 5 (of 5 total)
    • Thread Starter naresh73

      (@naresh73)

      Additional important information:

      The original homepage issue appears strongly connected to larger HTML-heavy Elementor sections.

      Observations:

      • Native Elementor containers/widgets generally work correctly
      • Larger custom HTML/CSS imported sections often trigger blank frontend rendering
      • Elementor editor preview may still display correctly while the live frontend fails
      • When the problematic HTML-heavy section is removed, frontend starts working normally again

      Also, the original homepage data and sections are still present inside Elementor backend/editor.

      This may help identify:

      • corrupted Elementor section/container data
      • invalid flexbox/container structure
      • frontend asset generation issues
      • HTML widget rendering conflicts
      • broken generated CSS

      Thank you.

      • This reply was modified 1 day, 18 hours ago by naresh73.

      I am having a similar problem rendering my frontpage.

      Uncaught SyntaxError: Invalid or unexpected token (at elementor-frontend-js-before:3333:2901)

      Uncaught ReferenceError: elementorFrontendConfig is not defined
      at 8309 (VM1191 frontend.min.js:1:25891)
      at webpack_require (webpack.runtime.min.js?ver=4.1.0-dev1:1:169)
      at 7603 (VM1191 frontend.min.js:1:19846)
      at webpack_require (webpack.runtime.min.js?ver=4.1.0-dev1:1:169)
      at VM1191 frontend.min.js:1:31903
      at webpack_require.O (webpack.runtime.min.js?ver=4.1.0-dev1:1:539)
      at VM1191 frontend.min.js:1:31922
      at webpackJsonpCallback (webpack.runtime.min.js?ver=4.1.0-dev1:1:5496)
      at VM1191 frontend.min.js:1:90

      https://www.infinitee-designs.com/

      @infinitee You are currently using Elementor 4.1.0-dev1 beta version on your website. Would recommend to roll back to a stable version of Elementor which would be 4.9 at the moment.

      I rolled back to 4.09 and a few earlier versions but there was no change.

      Disabling LiteSpeed fixes the frontend.min.js problem but leaves me without my site being cached.

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

    You must be logged in to reply to this topic.