shift8

Hello!

Sometimes the upgrade takes a few minutes to propagate through our system and show up in the plugin settings page.

One thing you can do to speed that up is navigate to the plugin settings page and click the “Check” button. What that will do is force the plugin to check in with our servers and update the plugin status.

If the issue is still happening, please open a support ticket via our dashboard. We would be more than happy to help.

Thanks!

Hello,

So far I conducted some tests by implementing a multisite with our plugin and have not been able to reproduce the issue.

The next step is to continue with the multisite tests insofar as replicating the installed plugins with the hope that perhaps that combination of edge case conditions will reproduce the problem. The key obviously is to replicate the issue in order to identify what , if anything, should be fixed.

Thanks for your patience!

Hello!

This is definitely a unique problem, or at least a less common one. What you could do is add a second site in our dashboard for img.subdomain.com.

Then once that is done, change your configuration where you previously set images to go through img.subdomain.com to go through the new CDN url.

This means:

request for image > CDN URL > fetches from img.subdomain.com in the background.

I dont see why the above scenario shouldnt work. Let me know how it goes!

Hello,

In the shift8cdn dashboard website where you registered for an account. In the “sites” area you can just delete the domain there. After deletion it would take a few minutes to propagate the change across the network.

Thanks!

Hello,

Our rewrite plugin doesn’t work the greatest with lazy loading of images and we are currently working to improve it.

Right now with your english site, I notice that the images that work aren’t even going through the CDN anyways, probably due to how the slider system is loading images.

If you flip the deactivate switch in the CDN plugin settings page, does the portuges images show up? Can we rule that out? Because I dont even see the slider attempting to load any images there.

To temporarily work around this issue until we have better support for lazy loading of images in slider systems like this, I would recommend perhaps looking into W3 Total cache plugin and setting up our CDN via that plugin to see if it works :

1. Go to shift8 cdn settings page and turn off the switch for “enable shift8 cdn”
2. Install W3 Total Cache plugin
3. Browse to Performance tab (side menu) and click on “General Settings”.
4. Scroll down to the CDN section.
5. Check Enable and select Generic Mirror from “CDN Type” drop down.
6. Click on “Save all settings”.
7. In the side menu under Performance or in the horizontal menu at top of the page click on CDN.
8. Scroll down to the Configuration section and enter your pull zone URL (in this case yours would be https://xz0arjxuq0lz.cdn.shift8web.com)
9. Click “Save all settings”.

If you follow the above steps, the slider images will show up. But again first and foremost make sure that the alternate language images are even showing up in the first place even without the CDN enabled/activated. Thats what you need to confirm first.

Hello!

So just to clarify, you are using our service but facilitating the static asset rewriting via the fastest cache plugin, correct?

1. I have your plugin installed. Do I even need to worry about adding it to fastest cache?

I’d say if you are using a caching plugin that offers the ability to rewrite static assets to go through a CDN, then its ideal to use only one plugin instead of 2. Less plugins is always better.

2. What settings do I need to add to here?

Would you mind sharing the URL of your site? Or if you dont feel comfortable sharing the URL, can you provide the CDN prefix you are using? I can confirm you are using the correct url. There are two urls potentially for the CDN, one for paid users and one for free accounts.

Thanks

Hello,

I’m going to close this issue. Feel free to open a new issue or send an email to [email protected] directly.

Thanks!

@fierevere

Yup – got it.

This issue is tricky and I feel with the level of information available in the format of this forum is not enough to get to the bottom of the problem. The user can email us directly at [email protected] and we can try to troubleshoot further.

Thanks