Tagged: AWS CDN
- AuthorPosts
- JacobGuest
We have encountered an issue where images are no longer being served correctly across our environments. Our setup uses W3TC to manage and serve images from a Cloudfront URL.
Since updating to WordPress 6.7 images are being served from/app/uploads/
instead.Could you please investigate and let us know what might be causing this behaviour? Any guidance on resolving this or adjustments we should make to our config would be appreciated.
Thanks,
JacobMarko VasiljevicKeymasterHello Jacob,
Thank you for reaching out and I am happy to help!
What changes have you made after the latest update for WP as it does not automatically change the path for the images?
In W3 Total Cache, Performance>CDN, you can add the path to the Custom file list: section, save all settings and purge the cache, and make sure to completely purge the CDN alsoThanks!
ChrisGuestHi Marko,
Replying on behalf of Jacob – same team 🙂
The only change was updating WordPress itself from any version of 6.6.* to 6.7.*
Before the WP update, everything works fine.
After the WP update, image paths are no longer automatically replaced.We have not changed any W3TC settings or any other code/content anywhere else.
Thanks,
ChrisJacobGuestWe have identified the issue, if the environment is in development mode, this appears at the top of the screen:
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the w3-total-cache domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/web/wp/wp-includes/functions.php on line 6114
This doesn’t seem to cause any issues on production, but it is worth noting this breaks images if notices are enabled, please let us know if there is a patch.
Please let us know when this is fixed, thanks. - AuthorPosts