CDN CNAME does not update domain in path to images

I just saw this in the 4.0.3 release notes:
Fixed CNAME issue in the srcset attribute when yar/month based folders are not used

I’m assuming that was ‘year’ and not yar… otherwise… yar there be treasure matey!
/end bad pirate joke

I disabled the year/month based folders as imo they’re the worst idea ever. I’m upgrading the plugin now, so we shall see if that was the issue.

• This reply was modified 6 years, 9 months ago by wlannistamps.

OK updated the plugin to latest (4.1.1).
src is still the blob storage.

I disabled all plugins, installed WordPress’ 2017 theme and refreshed

src still is blob storage but srcset now shows the cdn.

So… is this a matter of the src tags all being hard coded somewhere in the database? My next test will be to upload a new image and see if the new image src is the cdn, if so that will probably answer that, though a confirm would be nice.

OK, looks like WordPress is storing the paths to images in the database, and if we wish to update them, we need to do a find/replace. I uploaded a new image, and the src used the cdn, as well as the srcset. I’m closing this out.

Just a note — I used the WP Migrate DB plugin’s Find/Replace function (with the Update GUID option checked in the advanced options) to update the previously existing urls in the database to the CDN. I discovered that doing a simple find/replace in the SQL (either by hand or via a find/replace plugin) without updating the GUIDs will result in broken images and lots of problems, as the GUID serves as a security feature. Anyway, just in case anyone else runs into a similar problem, that’s how I resolved it. Hope to save you some headaches.