Background Images

SO I did a little testing. the Plugin is clearly copying images to the CloudFront CDN. IN the case of regular image tags, images are generally being pulled from the CDN.

However, background images and items refered to in CSS are not. I can obviously hardcode the URLs in the CSS to pull from the CDN. BUt this hardcoding seems really unwise.

Is there a needed setting so that relatively linked CSS page content source img urls are prepended with the CDN URN?

I would think localsite image references in a site’s CSS would commonly need to be dynamically have their URN changed so that they pull from the CDN.

(PS. We are using DIVI as our theme. I can manually use hardcoded image references in most of the theme designer editor components. I’d just not prefer to hardcode them by hand).

Just seems like I’m missing some basic capability in the Amazon AWS CDN plugin. PRobably something I didnt do in setting it up corretly.

Hello @csbwebmaster

I am sorry for the delay in my reply.

The plugin relies on the the media links to be (in your case) https://christianservicebrigade.ca/wp-content/uploads/...

some of the media on your website is loaded as
src="/wp-content/uploads/...

I think this is why the media do not load from cloudfront.

No worries on the delay, Lucky It’s not unexpected to be patient!

??

All of the images are in the uploads folder.

Let me see if I understand you.

What it appears is that the logic you are using in the plugin requires ABSOLUTE URL references (beginning in our case with ‘https://christianservicebrigade.ca/…’ in order to be rewritten. And that relative URL references are not rewritten. is that right?

The DIVI theme, when using a background image picker, puts relative URLS in place (like many themes / plugins do) to local media sources.

I don’t know that I can globally tell DIVI or WordPress to hardcode all URLS to absolute.

SO i’m not sure what to do.

You are not alone. Lot of other users have had the same issue and I am unable to devote time to work on this plugin.

Keep a check on the update, I’ll fix this in the next release.

That would be great.

I do like how easy you made the plugin. It is almost perfect for my needs. SOme of the others add such a level of overhead and complexity or do not really support AWS Cloudfront as anything but an ancillary CDN. I get that CLOUDFLARE is probably more popular today. BUt I don’t use it for many very important reasons.

I appreciate what you are doing and know what it’s like to give your time and effort. I thank you.

If you do take this up in a future release, that would be great. Perhaps the plugin should have a configuration option to additionally rewrite relative URLS for selected assets available via the CDN.

(I wonder also if you could have a box where users can select what TYPES they want to come from the CDN. JPG, TIFF, ICO, PDF, PNG, and others. Might give the flexibility to decide what assets can be redirected through the CDN.

(we do have some PDFs or other doc types that we make available regularly).

Anyways, not suggesting that you incorporate these ideas. Just putting them forward. I know they would take quite a bit of time to code, test, release, support.

??

Thanks for the response. I think I’ll hard code them for now. At least the bigger images that I want to have come from the CDN. (We have a lot of high-rez background images that take a lot to pull from our HOST. My organization likes them. it’s just that it puts a load on our host server to serve them).

??

Support for relative URLs has been added to the plugin