Frans Allen

Hi Albert,

Thanks for reaching out! Great questions!

This plugin should work with any caching plugins. I believe some users using it alongside caching plugin the same as yours.

WP2Static or Simply Static works well! We also plan for integration with WP2Static in the future.

Albert, this is the official plugin of Statically CDN, as far as I know, we are compatible with ourself ??

This plugin optimizes your static assets, you can still use Cloudflare for your website.

Let me know if this helps.

Best,
Frans

Your origin URL is your website URL. In your case please enter https://www.technews47.com.

For the Not Found, maybe add slash / in the end? Please try to ask the author of your caching plugin too for how to use Statically CDN URL in their plugin.

Hi there!

Many thanks for reaching out!

Currently, we do not rewrite URLs from another plugin to the CDN URL. Otherwise, you can set CDN URL on your caching plugin.

It’s NOT not working ?? just need a correct settings. Ok, let’s give this a trick, under your caching plugin, set the CDN URL the same as Statically CDN URL e.g https://cdn.statically.io/sites/example.com and for Origin URL the same with your website URL, that is for rewriting functionality by your caching plugin: find Origin URL on HTML and rewrite into CDN URL. Please contact the author for support.

For the question about WebP, please check https://twitter.com/staticallyio/status/1245731494330421248?s=19. We only convert image to WebP when it’s not larger than the original.

Let me know if this helps.

Best,
Frans

Glad it worked for you!

I will mark this as resolved, please don’t hesitate to reopen if you have any related questions.

I have cleared some CDN cache for your site, but not all because this feature is still limited. Now, try again and if the issue still exists, check the Browser Console, there will be useful information when an error occurs. If you need another purge cache, please use this form.

You can only use the hostname if you have a custom domain for Statically. Since the free CDN format is cdn.statically.io/sites/example.com and this is not a hostname, it won’t work. Even so, you can contact them and ask for CDN setting that uses a URL instead of a hostname.

It fixed globally. However, the truncated version of the asset might still be cached on the CDN, that’s probably why this happened. If you want to tell us which sites are still experiencing this issue, we will be happy to fix everything for you.

Hi, based on your report you said “The page is normal but some broken of font and small parts”, this issue happened on the CDN and has been fixed, please check your site again.

See this too https://cdn.statically.io/screenshot/rehub.catuyen.com

• This reply was modified 4 years, 11 months ago by Frans Allen.

Thanks @whateverfree2, that should work for @mfa95 to serve image Only.

@mfa95 re: WP Core assets, in the upcoming v0.5 there’s an option to turn this off. Here’s the preview:

https://upset.dev/uploads/Screenshot%20from%202020-04-17%2000-30-55.png

I’m not sure how you mean by closed site, what I know is that CDN can’t work if your site can’t be accessed through the internet or requires authentication. Your site must be on the internet or be accessible by our server.

Should work with any caching plugin, just enter the right format of CDN URL e.g https://cdn.statically.io/sites/example.com.

Let me know if you have other questions.

Best,
Frans

Thanks for the tips! We will add this to our list of possible improvements.

The file minifier is done on the CDN so there is no option to disable this via the plugin at this time. But it should still work even if the file has been minimized at origin because this feature is not so aggressive and will maintain the original content.

I went into this problem and found that one file was truncated during the minification process. The file was rehub-theme/style.css. This happened to our side and now it has been resolved so this should not happen again.

Hi @whateverfree2,

I just checked your page and it seems normal now.

Maybe it happened when our CDN was trying to connect with your origin or the minification process. Improving this section is on our radar, I don’t have a date yet but we hope it will be much better soon.

Best,
Frans

Hi there,

With your current settings should work to exclude JS and CSS files.

The https://cdn.statically.io/wp/ only for WordPress core assets and should not have an effect on assets that change frequently. This should be safe. The upcoming v0.5 has the option to turn off the CDN for WP Core assets. Please stay tuned!

the js and css cache is also active

I checked your page and no other JS or CSS files are served using CDN. Try clearing the cache in your cache plugin. That may be your case.

Best,
Frans

I have seen your page, based on what I see you shouldn’t defer jquery.js because that might be important in the template you are using. Try removing defer in jquery.js and it should work.

Hi @cstrand89,

Thanks for reaching out!

You can add .css,.js to Asset Exclusions, this will exclude CSS and JS files from the CDN.

Usually, assets cannot be loaded because the origin does not support HTTPS, if this is your case, please consider enabling HTTPS for your site.

Let me know if you need further assistance.

Best,
Frans

Hi @whateverfree2,

Can you see errors in the browser console and send them here?

I’m trying to demonstrate your website here and it looks good.

Best,
Frans

Hi @whateverfree2,

Thanks for reaching out!

If I understand correctly, the minified CSS & JS files generated by your cache plugin are not included on the CDN? If so, try using the Statically CDN URL in that plugin too, because usually, it has a different process.

Best,
Frans