Forum Replies Created

Viewing 15 replies - 286 through 300 (of 397 total)
  • Plugin Author shift8

    (@shift8)

    Alright – this was resolved much quicker than expected. Legacy users (i.e. you) should be back to 10 pull zones. Again sorry for the inconvenience – we value all feedback!

    The plan is to push out more features and a proper support ticketing system as well as more endpoints in under-serviced regions like Latin America, Africa and the Middle East.

    Thanks!

    Plugin Author shift8

    (@shift8)

    We’re currently rolling out a system that is intended to balance capacity planning while still offering a high quality free service.

    What we will probably do in the next day or two is roll out legacy plans for those who signed up early, with enough pull zones. I apologize for the inconvenience but check back in a day or two and your account should be good to go.

    Thanks!

    Plugin Author shift8

    (@shift8)

    Hello,

    I see that your site is now deactivated and the site resolves properly now.

    Are you able to provide more information as to what was causing the 520 error? For example :

    – What element exactly was causing the 520 error? Was it just when loading the website or was it when loading content via the CDN?

    – Can you navigate to the Shift8 CDN Settings > Debug Info and paste the debug information here.

    Thanks!

    Plugin Author shift8

    (@shift8)

    Hello,

    You reached out to us directly and we resolved the problem for you. For the record it was a 3rd party caching plugin that was installed that contributed to this problem. The caching plugin was not clearing the cache properly or was not being manually cleared after deactivating the CDN.

    Thank you

    Plugin Author shift8

    (@shift8)

    Hello,

    The Deprecated message does not mean that anything is actually broken. It is an informative message. I will look at suppressing or resolving the message in an update, but it should not impact any functionality.

    Plugin Author shift8

    (@shift8)

    We will soon put a purge function in the shift8cdn.com dashboard.

    Until then , and even moving forward as a best practice, I would recommend using a versioning system for your JS/CSS files : https://developer.ww.wp.xz.cn/reference/functions/wp_enqueue_style/ (see “$ver”)

    This will add a query string at the end of the url when wordpress loads the CSS / JS files. All you have to do is increment the version number and then the Shift8 CDN will assume its a new file and not load from cache.

    Plugin Author shift8

    (@shift8)

    I’m going to close this issue because the GTMetrix score is influenced by their own internal list of CDN services. You are free to contact them to add our service if you like but there’s not much I can do from our end.

    Plugin Author shift8

    (@shift8)

    Shoot i didn’t realize it was two people that posted in this thread. Sorry! webpower, if you dont mind making a new thread for your issue that would be ideal so as not to confuse things.

    Plugin Author shift8

    (@shift8)

    Ah, here it is, confirmation that GTMetrix has a pre-defined list of CDNs that they use when detecting : https://gtmetrix.com/blog/updates-to-cdn-detection-dashboard-and-more/

    This means that they just need to add us to their list. Since this is just to improve a score, not improve page speed, I’ll leave that up to you if you want to try reaching out to them. I have improvements to the system and functions/features we want to add so our bandwidth internally is stretched.

    Plugin Author shift8

    (@shift8)

    Hello!

    Thank you for using the plugin 🙂

    First and foremost, we unfortunately cannot control how GTmetrix determines a CDN. My guess is that they dont consider us a public CDN because we dont qualify in their list of pre-defined known CDNs? Perhaps because we are pretty new, its difficult to say.

    This consideration, in my opinion, isnt super relevant because google doesnt care if you use an official CDN. They only care that your site is fast, which (hopefully) it is when using our CDN.

    As for your other issue :

    [12-Dec-2019 21:31:35 UTC] PHP Notice: Undefined property: stdClass::$error in /home/wow/mijndomijn.com/wp-content/plugins/shift8-cdn/components/functions.php on line 79

    wp-content/plugins/shift8-cdn/components/settings.php on line 46

    Can you confirm the following things :

    1. What is the version of the Shift8 CDN plugin you are using
    2. What are you doing exactly when that error is generated (i.e. clicking XYZ button, etc).

    Thanks!

    Plugin Author shift8

    (@shift8)

    Hello,

    Unfortunately the business reviews bundle is a commercial plugin so I cannot practically purchase a license just to troubleshoot.

    I am going to look into why some scenarios are causing the rewrites to not function. Some users have had luck implementing the CDN using other plugins like WP Rocket. Techncially you can use our CDN by entering the CDN url (you can get the url by clicking the test url in the plugin settings) into the settings of caching plugins like WP Rocket or W3 Total cache (which is free).

    The CDN url will look something like https://<your prefix>.wpcdn.cdn.shift8cdn.com , which is what you would need to enter into these plugins.

    If you did use another plugin to implement the CDN, make sure to turn off the plugin in the Shift8 CDN settings page (flip that big switch).

    Thanks,

    Kevin

    Plugin Author shift8

    (@shift8)

    Hello!

    Its supposed to rewrite static assets, especially within wp-content. Can you provide one URL with a static asset in that path that is not working?

    Also can you confirm what that plugin is called that your using? I’m assuming “business reviews bundle” but wanted to double check.

    Thanks!

    Plugin Author shift8

    (@shift8)

    Hello,

    Actually are you able to run the following test for me , as it would save a significant amount of time :

    1. Disable all plugins except Shift8 CDN
    2. Re-enable each plugin , one-by-one and verify each time you enable if the problem arises.
    3. Once you have identified the specific plugin , let me know here and I can look further.

    Thanks!

    Plugin Author shift8

    (@shift8)

    Well all this plugin does is rewrite URLs with static assets to use the CDN url.

    Technically you can use either another plugin (i.e. wp rocket) or use .htaccess / nginx rewrites to convert static asset urls to use the cdn , so :

    http://www.yoursite.com/wp-content/themes/yourtheme/style.css

    becomes :

    https://<YOUR-CDN-PREFIX>.wpcdn.shift8cdn.com/wp-content/themes/yourtheme/style.css

    If the Shift8 plugin is breaking, all that is breaking is the rewrites of the URLs. The actual CDN will always work , you just have to tell your site to rewrite those urls.

    In a future version, I could offer to generate nginx or apache rules that you can just add to your htaccess file. I would have to test those types of things as well. I dont imagine the plugin conflict issue will ever go away as its almost impossible to test conflicts with all wordpress plugins but I’ll try my best!

    Plugin Author shift8

    (@shift8)

    No worries, leave this with me. It might take a bit of time as these types of things are really tricky as most of the problems lie with a conflict with another plugin.

Viewing 15 replies - 286 through 300 (of 397 total)