Article “Last Updated” timestamp changes without content edits
Article “Last Updated” timestamp changes without content edits
Opening an article in the editor appears to trigger an autosave that updates the “Last Updated” timestamp, even when no content changes are made. I think this was not the issue before the new UI that's why I am opening this report. In any case, the “Last Updated” timestamp should only change when actual content edits are made.
Steps to Reproduce
– Open an existing article in the editor – Make no edits (don't even click in the article content) – Open the article in your world
Operating System
WindowsBrowser
Google ChromeRelated Entity
This behavior can cause confusion, especially during challenge judging periods where authors are advised not to edit submissions. It may also lead to timestamps being misinterpreted as intentional changes, potentially resulting in articles being unfairly disqualified.History
can you tell us an article of yours this happens to?
Of course, here you are: Article 1 If you need more, this happened to a great number of my entries from this world, as I was just navigating the dashboard and without making any changes in the articles themeselves.
Hey, I tried to reproduce this and couldn't, I also ran a test with the article you linked specifically and it didn't automatically update its updateDate. Is there a chance you changed the order of this or any other article inside its parent category? Because that is one case I can think of where a change is made indirectly without editing the article's content.
And can you still reproduce it? Btw are you using the Article & World Manager interface or the Old Version edit page?
It seems I cannot recreate it, which is weird. The article I sent you before was one that I placed in a different category, so probably that was the reason for the change on the timestamp (I didn't know this would happen until recently), but this also happened to articles that I merely opened (in the new editor if I remember correctly) like this one. I opened it again just now both in the old version edit and the new one, but the last update didn't change this time.
I will ask the other person that also noticed that behavior to take a look and share her finds here as well.
Thanks for the additional information and testing, I will be waiting for your response after the other user tries again!
This is really strange! I've just tried to re-create it but haven't been able to. It was definitely an issue in the earlier versions, as there was a lot of discussion in the discord server about it as well.
This was indeed an issue previously (some weeks ago) and was affecting users who had the Expanded Prompts feature on - perhaps part of what you saw was due to that, which has been resolved! Perhaps another fix fixed your case as a byproduct as well, but for now I will be closing this report and feel free to comment here if you manage to reproduce it again.
Find your way!
Resources
WHO WE ARE
LEGAL
Listen to our Podcast
