shift8

Hello!

There are a few potential culprits in terms of plugin conflicts that may be contributing to your problem.

WebP Express appears to try to route requests for images to a WebP extension. This may be interfering with the way that our plugin may be trying to rewrite requests to go through the CDN.

Better AMP may be doing similar things in terms of interfering with the way that Shift8 CDN will rewrite requests for static assets.

To rule these out, try disabling WebP express first, and see if the issue resolves. If not , try disabling Better AMP and see if that resolves your issue.

If these steps still dont resolve the issue, feel free to let me know your site url so I can attempt to analyze the site. If you dont want to share the url here, feel free to email [email protected]

Hello!

First of all I love your avatar image 😉

Second I apologize if the CDN url for your site isn’t clear, I’ll look into making a more obvious way to make that clear in the next plugin update.

Basically you can see the URL for the CDN if you click the “test” url on the main plugin settings page.

That said , I looked up your site and found that your CDN prefix is “1hfqh7nplkiaa”

This means the CDN url would be https://1hfqh7nplkiaa.wpcdn.shift8cdn.com/whatever.jpg

If the plugin is not rewriting all the static assets to go through the CDN , please let me know as I’m not sure if thats your problem. If it is your problem , perhaps you could try disabling the following plugins :

• Leverage browser caching
• WP-Optimize
• Speed booster pack

You could try disabling one at a time to see if one specifically is contributing to the problem. You could also try clearing the cache of all plugins, but what may be happening is that your not seeing the CDN right away because those other plugins are caching your site before the CDN url is rewritten. Does this make sense?

Its very difficult to troubleshoot these plugins beyond what I’ve done here , but what I’ve described is your most likely culprit.

Thanks!

Hello!

Is that to be expected? I read another post in this forum and think it is…?

Yes indeed! I am thinking about pushing a plugin update to change that image to something less ambiguous! Perhaps an image of the words “TEST IMAGE”?

When i press the YELLOW check button in the core settings tab I get the following message

So you need to head to shift8cdn.com and register for an account. Once registered, you add your site in our dashboard. Once thats done, you can go back into the plugin settings and paste the API key, prefix and the URL that you entered when adding the site to our dashboard.

Then hit save and you can then hit the “check” button. All that check button does is communicate with our service and verify all the settings are correct. So long as you have the API key set in the plugin settings, the “check” button can populate the rest. Hit save after hitting check if your not sure!

Thanks for using the plugin!

it shows the “no signal” image.

Hello!

This is expected. The test image is actually the “no signal” image. We decided to just use that test image to show that the CDN is working. When I click the test url , I see the test.png loaded from the CDN.

Apologies if the image itself caused the confusion. Maybe we’ll look into using something different as a test image. I’m open to suggestions! 🙂

Hello!

Thank you for providing this. Are you able to provide the debug info from the plugin and paste it here?

To do that :

1. Go to WP Admin > Shift8 > CDN Settings
2. Click the “Debug Info” tab
3. Copy the debug info displayed and paste here

Thank you!

Closing due to inactivity – feel free to open a new issue if you want to revisit

Hello!

Best way to confirm this is to disable the WP Mobile menu plugin and clear any respective caches. If the problem resolves itself then that likely is what is causing the issue. If that is indeed the case, you might want to reach out to their support forum to see if they can help.

My best guess is that plugin is rewriting URLs that is conflicting how our plugin is rewriting URLs , causing them to break.

Its pretty hard to troubleshoot since the trigger of the problem is (potentially) with that plugin.

Thanks

Sam,

So sorry you are having these problems. I will reach out to you directly via email and we will definitely have this sorted.

Thanks