youngcp

Most sites don’t usually delete the local copy from the server and just mirror it to the cdn, so it’s usually always available.

There were previous servers, the content was mirrored to the CDN but not downloaded back to the new server. The EC2 instances that host the WordPress are allocated with very thin storage provisions. Most of the storage is dealing with cache for the S3 mirrored/exported content already. Not gonna fork out for a lot of local storage, S3 is cheap.

If you use relative paths, as long as your css /js files are pointed to the cdn and being served from there

I shouldn’t have to use relative urls, especially in the cases where the content doesn’t exist nearby, just on the CDN.

I’m not going to ‘fix’ the existing absolute urls; if the plugin fails or is disabled I don’t want the client falling back to the PHP host, the load during an election season would tank the response of the site, and some of the content would just not exist.

If CloudFront fails we can deploy a fallback static content local instance from backups by updating the DNS records.

• This reply was modified 4 years, 4 months ago by youngcp.

Do you have any static.clearpathaction.org urls hardcoded on your css/js files?

Yes, there are lots of images and other content that was moved directly to the CDN and many of those URLs were in a previous WordPress instance or are mirrored from the current uploads directory.

Much of the CSS likely has static.clearpathaction.org as a base URL.

If you’re replacing those clearpathaction.org -> static.clearpathaction.org (static.clearpathaction.org -> static.static.clearpathaction.org) and using fvm_get_protocol to generate the URL, I can see how that’d be a problem, but that’s also a bug. You probably want to check for a ‘//’ prefix on the path, or barring that, check do a preg negative lookback or something to prevent replacing a subset of the domain.

• This reply was modified 4 years, 4 months ago by youngcp.

If you want a different path on the cdn than the one on the live site, then the plugin doesn’t support that. I don’t think also, any (or the majority at least) of cdn /cache rewriting plugins will support that either.

According to the configuration, the default path that would be used is;
https://static.clearpathaction.org/wp-content/uploads

Yet I specified;
https://static.clearpathaction.org/

If I chose https://static.clearpathaction.org/wp-content/uploads would the resulting URL be https://static.clearpathaction.org/wp-content/uploads/wp-content/uploads?

• This reply was modified 4 years, 4 months ago by youngcp.

Screenshot: https://pasteboard.co/Jh1jf0d.png

The CDN url is https://static.clearpathaction.org/
It is not https://static.clearpathaction.org/wp-content/uploads/

I’ll upload a screenshot of the configuration shortly.

I’m purging the cache and re-applying my changes so the site works for now.

$domain or site_url(); return https://clearpathaction.org

https://static.clearpathaction.org/wp-content/uploads/smile_fonts/ClearPathAction2015/ClearPathAction2015.ttf is not a misconfiguration, it is an incorrect URL.

https://static.clearpathaction.org/smile_fonts/ClearPathAction2015/ClearPathAction2015.ttf is the correct URL. Note the absense of /wp-content/uploads

Now wrong cache URLs visible on the home page after most recent purge.

Again, ping back as soon as you have had a look, I’d like to re-make my changes temporarily until you can suggest a code solution or configuration change.

Cache is being finicky about being purged quickly, since the cache is on the CDN;

https://clearpathaction.org/legislation/ shows the problem with the generated CSS URLs;

https://static.static.clearpathaction.org/cache/fvm/1594393582/out/header-2628aa93d24dcdf0ea90304934e2577347f21ac3.min.css

https://static.static.clearpathaction.org/cache/fvm/1594393582/out/footer-9e65b03e8c32311daa728fe0ac060f4201fd69e8.min.css

Woops I think the purge occurred before both fixes were undone… re-purging.
The subdomain fix was still in but the icon font paths were broken.

e.g. https://static.clearpathaction.org/wp-content/uploads/smile_fonts/ClearPathAction2015/ClearPathAction2015.ttf
should be; https://static.clearpathaction.org/smile_fonts/ClearPathAction2015/ClearPathAction2015.ttf

• This reply was modified 4 years, 4 months ago by youngcp.

Tell me once you got a look and I’ll fix the fvm_get_protocol to fix the static.static. subdomain, then you can take a look the CSS where it fails to properly update the path for the custom icon font (there should be an elephant in the middle instead of the ubiquitous square box indicating a missing character).

Ok, changes are undone.

The paths for the CDN are wrong, my settings for the paths are as follows;

CDN URL: static.clearpathaction.org

Cache path: /mnt/efs/web/clearpathaction.org/public/wp-content/uploads
(copied from default)

Cache url: https://static.clearpathaction.org/
(default: https://static.clearpathaction.org/wp-content/uploads)

Since you’re active right now, I’ll undo the changes have you look here;

https://clearpathaction.org/