A user, patrickemin, noticed a bizarre system banner stating a user’s last post was “34 years ago”—despite the user having registered only 3 months prior. The notice, visible to admins and TL2+ users depending on settings like returning user notice tlJammyDodger, sparked confusion. ludwikc suggested a possible translation error (e.g., “days” misrendered as “years”), while RGJ uncovered the truth: the user had posted before—patrickemin had manually altered the post date of a topic in “Histoire” to 34 years ago, triggering the misleading notice. David_Ghost warned that changing post dates can harm SEO, citing Google’s stance on content dating. patrickemin clarified the post was unpublished and dated retroactively, so SEO impact was negligible—and suggested adding a feature to set topic dates before publishing. The mystery was resolved, and the notice was traced to a manual date edit, not a bug or translation glitch.
Hi, funny thing, one of my user who never posted but was registered something like 3 months ago posted today, and the system put a banner (visible only to the admin I guess):
It’s been a while since we last saw braudpatrice. His last message was 34 years ago.
Thanks for the links, in my case I posted the topic then changed the date, seconds after the topic was published, for a very much older date, 34 years before ! So because the topic was not on Google index and because the date is not newer but much older, I think I don’t fall under the uses cases discussed in the articles you mention. BTW, I think having the ability to set a topic date before posting would be a bonus. I don’t think it’s possible ?