WPIntell

Source evidence

Problems with File Renaming

Advanced Media Offloader · support · 2026-01-27T09:47:00+00:00

complaintsentiment
highseverity
0.86relevance
6replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

4 / 23 rows with source links

17.4% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

19 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
stefancodeqo resolved
I am using advanced media offloader for my store, but am encountering lots of problems with missing images lately. This is due to errors in file naming. Files seem to have suffixes in their names that result in an 403 error when trying to load them on the page. This both happens with the “-scaled”-Tag added by WordPress itself and renaming using https://meowapps.com/media-file-renamer/ Is there any way that I can get this more stable? I have versioning enabled, so it is not as easy to find all the files and rename them manually. Thanks! Hi @stefancodeqo Thanks for reaching out! Could you please provide more details? Probably adding some examples. Are you facing this issue with the images that you are trying to rename? Or is it only with the image that has the -scaled suffix? Could you please mention which cloud provider are you using? Hi @stefancodeqo I’m marking this ticket as resolved due to inactivity. You can open the ticket again or create a new one if you need more help. Sorry for the late reply, I am using Hetzner Object Storage via the Any S3 Compatible Storage Option. So far I haven’t had an issue with the provider. My main problem was, that pictures in the product pages just did not show up correctly, because the media attachment in WordPress and the saved URL were not the same. Most of the times, the problem was resolved by removing the “-scaled”, or “-mfrh-original” suffix from the end of the filenames manually, or at least check if the version without suffix exists, and if so, to apply the changes (I wrote a little wp plugin to do that). By the way, it did not cause problems for all my images, only around 8000 out of the 36000 total images. Anyhow, I am currently refraining from using any media renaming as long as this causes issues for me. I will be using Imagify or some other image processor plugin to convert my images to modern image formats in the next weeks (probably first on a staging site) and will get back to this forum if I encounter any new issues. In addition to this: I’ve seen quite a lot of bad reviews of the plugin Modern Image Formats (not being able to revert the use of the modern versions and the plugin not serving correct versions). I originally wanted to use WP Rocket’s tool imagify, but that does not seem to work with Advanced Media Offloader. Do you have any other recommendations regarding this? Hi @stefancodeqo Thanks for reaching out! Have you been able to resolve the issue you were experiencing? Regarding the Image Optimization plugin, we have released a new version that includes compatibility with both EWWW Image Optimizer and the Imagify WordPress plugin. Hi, thanks for the answer. I did not really find a solution to the first problem, I had to manually fix the image links unfortunately, but now I have it somewhat working. I’ll check out the new Image Optimizing compatibility, thanks for the update!

Comments

6 shown
Masoud Golchin 2026-01-29T20:22:00+00:00

Hi @stefancodeqo Thanks for reaching out! Could you please provide more details? Probably adding some examples. Are you facing this issue with the images that you are trying to rename? Or is it only with the image that has the -scaled suffix? Could you please mention which cloud provider are you using?

Masoud Golchin 2026-02-04T09:50:00+00:00

Hi @stefancodeqo I’m marking this ticket as resolved due to inactivity. You can open the ticket again or create a new one if you need more help.

stefancodeqo 2026-02-04T12:42:00+00:00

Sorry for the late reply, I am using Hetzner Object Storage via the Any S3 Compatible Storage Option. So far I haven’t had an issue with the provider. My main problem was, that pictures in the product pages just did not show up correctly, because the media attachment in WordPress and the saved URL were not the same. Most of the times, the problem was resolved by removing the “-scaled”, or “-mfrh-original” suffix from the end of the filenames manually, or at least check if the version without suffix exists, and if so, to apply the changes (I wrote a little wp plugin to do that). By the way, it did not cause problems for all my images, only around 8000 out of the 36000 total images. Anyhow, I am currently refraining from using any media renaming as long as this causes issues for me. I will be using Imagify or some other image processor plugin to convert my images to modern image formats in the next weeks (probably first on a staging site) and will get back to this forum if I encounter any new issues.

stefancodeqo 2026-02-10T11:20:00+00:00

In addition to this: I’ve seen quite a lot of bad reviews of the plugin Modern Image Formats (not being able to revert the use of the modern versions and the plugin not serving correct versions). I originally wanted to use WP Rocket’s tool imagify, but that does not seem to work with Advanced Media Offloader. Do you have any other recommendations regarding this?

Masoud Golchin 2026-03-04T11:44:00+00:00

Hi @stefancodeqo Thanks for reaching out! Have you been able to resolve the issue you were experiencing? Regarding the Image Optimization plugin, we have released a new version that includes compatibility with both EWWW Image Optimizer and the Imagify WordPress plugin.

stefancodeqo 2026-03-04T13:20:00+00:00

Hi, thanks for the answer. I did not really find a solution to the first problem, I had to manually fix the image links unfortunately, but now I have it somewhat working. I’ll check out the new Image Optimizing compatibility, thanks for the update!