-
Posts
-
So by default it is running 100% of the time. In order to make code across our site as lean as possible I want to disable the global load. That way the code only loads on pages where the shortcode is being used. Sounds like a great feature to reduce code on other pages…
When I disable the global library load it fails to load correctly on pages with the grid shortcode. The items do not display their thumbnails. It just breaks. Is there a 2nd step to using this feature?
Hello There,
Thanks for writing in! To better understand the Global Settings along with it’s limitations, please check out this documentation: http://theme-one.com/docs/the-grid/#!/global_settings
Hope this helps. Please let us know how it goes.
The link just references the same page/elements I reference. It does not address the “Load Library” section.
To repeat…
If globally loading the library is disabled, it should ONLY load the code on pages where galleries are used. This would decrease load time across the site, and keep the galleries going on relevant pages.
Instead, everything breaks when load library is set to off. Please advise. We are actively attempting to decrease load time, and this plugin is adding a few minor milliseconds that could help us get the site loading quicker. This option should not break the whole gallery implementation.
Hi there,
I noticed this too but not most of the time. I’ll forward this for further checking, though I can’t provide any temporary fix.
Thanks!
Any update on this glitch? The plugin by default loads on every single page, substantially slowing down any site load times (by up to 4 seconds in my experience on enterprise hosting). If we check the box “Include The Grid library globally”, the site is slow, but ofcourse the plugin works fine on the pages it is used. If we uncheck the box, the site loads MUCH quicker, but the page where the code is used, does not get the CSS & JS files loaded.
Seems to be broken. Any help would be GREATLY appreciated.
Hello There,
We have already forwarded your concern to the creators of the plugin. No update from them yet. Rest assured they are already looking into this matter. Once they’ll have it figured out, it will be updated and will roll out an update release.
Thank you for you understanding.
