Every time I create or update a new post this notice appears immediately. I was wondering why as it is a bit irritating. Is there anyway to post pone the notice until after a certain time limit. Because if I want to undo a certain change I can just ctrl z.
The backup of this post in your browser is different from the version below. Restore the backup
This will replace the current editor content with the last backup version. You can use undo and redo in the editor to get the old content back or to return to the restored version.
On every update?! That does sound annoying. I canāt replicate it yet, so can you provide more info?
For example, is the post published or in draft? Have you tried with all plugins deactivated? (I suspect itās triggered by one of them and, if we know which, it will be easier to address this.)
Also, which version of CP are you using? I remember we addressed something like this for unpublished posts, and that fix is in the latest nightly. We are planning to release v. 2.3.0 on Thursday, so that will have the fix too.
Currently I have no plugins activated and the versions are CP 2.2.0 and CP Theme 1.0.0. Here is a screenshot I took after updating a post and then clicking on the next or previous tabs.
It also shows up immediately upon opening the post for the first time or after updating it. Maybe the new update will resolve it.
I have made some new modifications in my child theme functions.php file to add the hero image and a couple other features so I will try removing them one by one also to see if that is the culprit.
Thanks. I know the fix was for unpublished posts, and I can see that his one is published, so Iām not sure whether the new version will resolve this. On the other hand, I remember that the cause was a problem with some browsersā local storage, so it might.
Could you try using a different browser? And which operating system are you using?
So I typically use Chrome and Firefox (current versions) and in Chrome it shows up immediately even when first opening the post. In firefox it only shows when I update the post or move between the previous/next links. I am using Windows 11.
This has been happening to me too for ages. I just ignore it. Optimizing the database (via a plugin) fixes it, until next edit.
There are a few weird things that have crept in over the last few CP updates, such as trying to move widgets in the admin dashboard crashes the site with an āAw, Snap!ā.
My computer has been acting up a bit, though no tests or scans actually find a problem, so I have no put much weight on it being a CP issue; I do have a site or two where the save/update button goes gray and stays gray, the only way to save is to copy the entire page, reload, paste it back in and save right away. The problem is also intermittent, sometimes I can save just fine and sometimes the button goes gray for longer than I think it should for auto save, but does come back. I have turned off revisions which did not help, but I also donāt think that actually stops the auto save process, though I did not spend much time trying to figure that out. This is using up to date versions of Chrome and Windows 11.
Now that I read @EliteStarServices, whose experience with the save/update function mirrors mine exactly, I can see that I was probably reporting the same problem earlier, except that I was associating it with Shield Security Pluginās decision no longer to support CP.
I also wrote in that post that āthe odd thing about the page-update saving (after edits) is that it comes and goes . . . But the recent issue with sluggishness has occurred only since I upgraded to 2.2.0 ā and [yet] today . . . the page-updates are generally normal, i.e., faster than during the odd sluggish period of this past week or so.ā
Although I, too, have just learned to live with these intermittent issues, Iām pretty sure they started with CP 2.2.0 and that the problem with Shield was a different issue entirely.
This isnāt a CP-only issue. It happens frequently to me when updating a WP site I manage, if I leave the edit screen to do something else on another tab or browser window. The only fix Iāve found is to save before I leave the edit screen to do something else, whether itās āsave draftā or āupdateā.
Like @raygulick , Iāve seen this happen on WP sites too. The problem we found when @Doug reported these symptoms is that the relevant code did not account for all the ways in which whitespace can be produced in HTML (and so an unaccounted-for character is treated as meaningful when it shouldnāt be). WP has that exact same code.
The fix we added to the nightly, and which will be in v.2.3.0, adds a couple of other methods of creating whitespace to the regex involved, so it should stop this problem (unless, of course, what is being reported now has a different cause).
EDIT: As for āAw, snapā, I donāt think CP contains such a string. That sounds like a Chrome problem.
That could be, I am down to two WP sites, and they are for testing plugin compatibility, so I do not really edit content. My machine also has some sort of an intermittent issue that I am not able to pin down, so I was not so sure that wasnāt playing a role.
Interesting as Iāve never had this issue with any of the wordpress sites I manage. Have to keep an eye out to see if it rears its ugly head there as well.
I had the same issue with ClassicPress (only) on my desktop PC (Chrome). But not my MacBook (older MacOS). Yeah, its an older PC but only this issue on CP. Not WordPress, WooCommerce, etc.
Probably there is something peculiar to Chrome and CP.
Using Chrome and the same version of CP, together with Classic SEO, I canāt reproduce this. So far as I can see, the fix we introduced that I mentioned above seems to have addressed this. I suggest you clear all caches, especially your browser cache.
My guess is that your browser (and maybe your server or CDN too) have cached the previous versions of CSS and JavaScript. Thatās why you need to clear them.
For Chrome, click on the vertical dots at the top right, then click Settings. Now choose Privacy and Security ā Delete browsing data and select the Basic tab. Check ONLY the Cached images and files box, and then click Delete data.
This will ensure that the copies your browser has made of various sitesā CSS and JS files and images will be deleted, and so will force the browser to fetch fresh copies.
