“File successfully replaced” backend notice stays forever

Hi @netzstrategen,

Quick question: does the message stay there even if you go to another page after replacing the image?

Hi @sixaxis,

Sorry for the delayed answer, I was in vacation.

Yes, the notice persists while navigating to other pages. Even if I close it using the (x) button on the left, it appears back if I refresh the page or jump to some other page.

The version of the plugin we are using is 3.3.7, but I have tried updating to 3.4.2 (last) and I get the same issue (although the styling of the notice seems to have changed and it looks a bit narrowed, the (x) button slightly misplaced).

Hi there,

I suggest making sure you flush your website’s cache and then try again. Please do it in this order:
1) Cache plugins (WP Rocket, LiteSpeed Cache, SG Optimizer…)
2) Server cache (SiteGround, Bluehost…)
3) CDN cache (Cloudflare, StackPath…). Please do it from your CDN’s dashboard, not through your cache plugin or hosting dashboard.
4) Browser cache (Chrome, Firefox, Edge, Safari…)

Does that work?

Hi @sixaxis,

Clearing caches have no effect on the issue.

How do you prevent dismissed notices to appear again? Do you track them in a cookie? In the wp_options table?

Good morning,

Can you remove and re-install the plugin, and let me know if that works, please?

Thank you,

@sixaxis,

I am afraid that didn’t work either. The only way I can get rid of the notice is deactivating the plugin. But it comes back as soon as I activate it again.

Hi there,

That’s very strange. I just tried it myself again and the message goes away. Some more questions:

1. If only Enable Media Replace is activated, does the issue still happen? I’m thinking of some cache/optimization plugin affecting the backend too
2. Does it happen with every replacement method? https://i.imgur.com/B0cOtbm.png
3. Could you go to Tools > Site Health > Info and copy-paste here the info? There’s a button there “Copy site info to clipboard”

Thank you

@sixaxis,

I will check that and give you and answer ASAP.

I too am having this problem on a site, was it ever resolved?