Disable CDN by default

  • Resolved Nicholas Zein

    (@zeinnicholas)


    6 years, 3 months ago

    Hello.

    I’ve been experiencing slow loading times in a test environment only to discover that Statically was being loaded on a fresh install, forcing the page to wait for the CDN to respond, but since it wasn’t set up (and sometimes we already have our own solution) with the CDN API it was waiting to timeout in order to load the pages.

    I think the inclusion of support for the CDN is great, but it shouldn’t be on by default right from the get-go. If you want users to use the new feature I think it’s great, but you should instead place a notice to configure it, instead of enabling it right away.

    • This topic was modified 6 years, 3 months ago by Nicholas Zein.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Gijo Varghese

    (@gijo)

    6 years, 3 months ago

    @zeinnicholas Thanks for the suggestion.

    The aim of the plugin is to ‘work out of the box’ of 90% of the users (since 90% are using CDN).

    If you don’t want CDN, just turn it off.

    Thread Starter Nicholas Zein

    (@zeinnicholas)

    6 years, 3 months ago

    Yes, that’s what I ended up doing. I don’t mind really, I am most probably be using it on more projects from now on.

    But it took me a while to understand it was fetching the CDN. Maybe you could add a condition to only load the script if the API key is valid, or inserted (if the field is empty, do nothing). Then it wouldn’t happen to load without an API and be lost as it did, forcing the page to be “waiting for statically.io” until it times out.

    What do you think @gijo ?

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

The topic ‘Disable CDN by default’ is closed to new replies.

Tags