I had the same problem! I cleared the cache for the site and then it worked.
My client wasn't so happy!
Why is this happening?
For 2 weeks
Do you know the cause?
I also cleaned my cache, but does not help.
Is this a Muse or browser problem?
1 person found this helpful
Did you update to the newest version of Muse (published yesterday)?
(In most cases the browser cache is "responsible" for this behaviour: Your page is cached to load it faster, when you visit it again. If you update your site and open it in your browser again, your browser sometimes mixes up new data and cached data. Muse can do nothing about this. But: There was a bug concerning this issue in previous versions, which is fixed in the newest version of Muse.)
You can prevent caching within your browser!
• Safari: Preferences -> Advanced -> "Show Developer menu".
• Then Open the "Developer" menu and choose "Deactivate Cache".
(Maybe I didn’t match the correct English wording, because I use a German OS.)
It's a shame you can't switch it off for everyone visiting the website.
That's what I would like.
Would be a nice feature request for Google Chrome, Firefox, Safari, Edge, Internet Explorer, …
Yes, I agree. Could Adobe switch off the warning if it's created by Muse?
No. Because there are different way to upload your site (Built in FTP, different FTP-applications, Dreamweaver, …).
And this alert in many cases is correct and therefore useful. You can’t imagine, how many users think, it is enough to only upload this or that image, this or that HTML file.
If the warning was always correct then I would keep it but the code needs work I think. The trouble is that people coming back to your website after an update will get an error message when everything is really ok.
Please update your Muse to the latest build which was released a day before yesterday.
We have tried to sort out this thing. Let me know if the message still continues.
Thanks, I will let you know if it continues.
I'm on the latest version.
I am on the latest version of Muse, have cleared caches multiple times on various browsers, and published all files / only modified files from my Muse site and this error keeps popping up.
Any thoughts on this? It seems to be a rampant problem for many Muse users.