Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author pipdig

    (@pipdig)

    Hi Jay,

    The w.org plugins team closed the plugin temporarily since they don’t like us using the Cloudflare CDN for assets. We’ll be pushing an update later today so that the assets are loaded directly instead. There’s no cause for alarm and you can safely use the current plugin in the meantime 🙂

    +1 just following, hoping w.org allows an update soon.

    Plugin Author pipdig

    (@pipdig)

    We’re very close to pushing the update now. There are some assets used to generate the map on the settings page which are coming from Cloudflare’s servers. We’re moving those over to the plugin which will hopefully keep the w.org peeps happy 🙂

    At the end of the day it makes sense, the plugin guidelines state that all assets should be locally stored. It’s something we should have done from the start, but it seemed silly to store them locally when the Cloudflare CDN is freely available, and everyone using this plugin is also using Cloudflare anyway.

    Thanks for your work on this. Love the plugin.

    Curious though, how do you purposely store your assets on Cloudflare’s CDN? I thought they didn’t offer traditional object storage like a traditional CDN, just caching.

    Plugin Author pipdig

    (@pipdig)

    No problem Joe, glad you like the plugin!

    Cloudflare has a project which hosts open source libraries at https://cdnjs.cloudflare.com. This is where the assets were being called from to generate the map.

    Ah! got it. thanks!

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

The topic ‘Gone?! Wha?’ is closed to new replies.