Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • seavashr Friend
    #1033035

    JA Builder loads these two assets (to display edit button and activating the editor) to ALL pages and even to non-logged in users!

    • /plugins/system/jabuilder/assets/css/jabuilder.css
    • /plugins/system/jabuilder/assets/js/jabuilder.js

    I don’t think extra assets should be be added to make the page heavier and thus loads slower, as well as extra process on the server.

    These assets should be loaded only on:

    1. 1) Pages created by JA Builder
    2. 2) For users with Edit permission

    I hope your team could add this to the road-map.

    Regards

    Saguaros Moderator
    #1033171

    Hi,

    Thanks for raising this up. I will pass to the team for further consideration.

    Regards

    terp Friend
    #1034522

    Thanks for the post…was wondering why they are being called everywhere on demo pages, so searched the forums and found your thread.

    Aside from that, are there more calls for js/css files that unnecessarily add to the overhead?

    I can’t find a lot of good sites to test, but every page done with PB has extremely large CSS files and a ton of js…but unsure if this is related to other components, as usually compressed and I can’t determine what exactly is PageBuilder-related overhead.

    Saguaros Moderator
    #1034622

    Pls stay tuned and wait for the news from the team.

Viewing 4 posts - 1 through 4 (of 4 total)

This topic contains 3 replies, has 3 voices, and was last updated by  Saguaros 7 years, 6 months ago.

We moved to new unified forum. Please post all new support queries in our New Forum