• Resolved jessejones

    (@jessejones)


    Previously I flagged issues with Simply Static and Elementor here in this support thread:
    https://wordpress.org/support/topic/elementor-file-issues-not-including-css-js-etc-w-dynamic-urls/

    Same issues are occuring again w/ Elementor 3.13+ (newest version). No issues are occuring with the site when using it as a regular WordPress site.

    For the changes in the newest versions of Simply Static, what was done to address Elementor and other theme builders? How are the CSS/JS being extracted?

    This is how the URL path looks (the bundle is dynamically generated):
    /wp-content/plugins/elementor-pro/assets/js/nav-menu.3347cc64f9b3d71f7f0c.bundle.min.js

    The bundle appears in the DOM so depending on how the nav-menu js is extracted, it should be included.

    These are the error messages in Chrome Console.

    caught TypeError: Cannot read properties of undefined (reading 'setLocaleData')
        at (index):879:9
    
    nav-menu.3347cc64f9b3d71f7f0c.bundle.min.js:2 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'value')
        at child.onInit (nav-menu.3347cc64f9b3d71f7f0c.bundle.min.js:2:4132)
        at Module.e.each.n.<computed> [as onInit] (frontend-modules.min.js:2:17086)
        at Module.trigger (frontend-modules.min.js:2:16898)
        at Module.e.each.n.<computed> [as trigger] (frontend-modules.min.js:2:17086)
        at child.Module (frontend-modules.min.js:2:17184)
        at child (frontend-modules.min.js:2:17449)
        at child [as constructor] (frontend-modules.min.js:2:17449)
        at new child (frontend-modules.min.js:2:17449)
        at e.exports.addHandler (frontend.min.js:2:2510)
        at frontend.min.js:2:3029
    
    nav-menu.3347cc64f9b3d71f7f0c.bundle.min.js:2 Uncaught TypeError: Cannot read properties of null (reading 'reset')
        at child.stretchMenu (nav-menu.3347cc64f9b3d71f7f0c.bundle.min.js:2:3822)
        at Module.e.each.n.<computed> (frontend-modules.min.js:2:17086)
        at dispatch (jquery.min.js:1:43177)
        at y.handle (jquery.min.js:1:41161)
Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter jessejones

    (@jessejones)

    One additional detail to add:
    Latest versions of Simply Static show nearly double the number of pages/files then older versions. No page counts were increased.

    I was able to temporarily resolve this by going down to older versions Simply Static.

    Thread Starter jessejones

    (@jessejones)

    The Simply Static versions were:
    2.3.1 – Simply Static Open Source
    1.3.1 – Simply Static Pro

    Going to versions below x.3 resolved it.

    Thread Starter jessejones

    (@jessejones)

    Going through the error messages again, this seems like this could be more of a Webpack issue then anything else. Any page builder/theme that uses Webpack, e.g. Divi, Elementor, etc, will probably be effected depending on how the JS is fetched.

    • This reply was modified 2 years, 10 months ago by jessejones.
    Plugin Author patrickposner

    (@patrickposner)

    Hey @jessejones,

    just a quick update here.

    It took quite a while, but it seems we have figured it out now.
    We will fetch the asset URLs directly from the outputted JSON configuration to ensure we extract and download the JS files even if there are lazyloaded via Webpack.

    Fingers crossed, the official update will follow soon!

    Cheers,
    Patrick

    Thread Starter jessejones

    (@jessejones)

    Thanks for the follow up @patrickposner and that sounds like a great idea! 🙂 I think this should resolve any theme or plugin that uses webpack or lazy loading.

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

The topic ‘Simply Static > Elementor Nav Dropdown not working’ is closed to new replies.