Hello!
I just tested the bulk editor and experienced no issue with the removal of predefined metadata.
There might be an issue with the cache: If you update a post via WordPress, caching plugins recognize an update and flush its cache (or even flush it when the editor is loaded). However, the caching plugins might not clear the cache if you upload data via the XML file. The mixing of outdated cache with new data will cause storage to revert.
Does the issue occur after you upload the XML file’s data, flush the cache, and then bulk-edit?
Thread Starter
Oksana
(@qwerty100)
Hello, there is no caching plugin, I disabled all plugins. Tested on different PHP versions. Perhaps more information will help us understand what is happening https://docs.google.com/document/d/1-qmEQHQiq0o9SpDmZbOvp3lnEw2oPGzYS3ea9XA_-Gs/edit?usp=sharing
Thread Starter
Oksana
(@qwerty100)
I think the problem is not related to the cache, now it is solved by clicking the “refresh” button on the page. It seems to me that WordPress doesn’t know about the meta tags until the button is clicked, it’s a shame that the update cannot be massively – in which case the meta disappears.
Thank you for investigating, Oksana!
Yes, WordPress tabs don’t query the latest data automatically. If you’re working with multiple browser instances, you must refresh administrative pages to ensure your browser retrieves the freshest data after every update.
Working in WP-Admin with multiple tabs or with multiple users concurrently warrants issues. Browser tabs work as independent “caches” of information sent to them — which they can send back independently, likely overwriting and invalidating other tabs instantly.
This probably won’t ever change, although Gutenberg (Block Editor) pages could act a little differently — those are design decisions with which no data scientist could agree.
There are only two hard things in Computer Science: cache invalidation and naming things. – Phil Karlton
