Hi all,
looking for help concerning a weird issue. Suddenly, throughout our Confluence 6.8.0, all timestamps concerning documents and attachments have crazy values like 57.19.2018 (mm.dd.yyyy).
On a hunch, changed format in general settings, but no effect other that the order is changed, but still wrong / weird dates.
Checked some of the tables in database, like Content / Contentid et al and found dozens of correct values, but none of those crazy values.
I have uploaded a picture describing our problem to here http://abload.de/image.php?img=screenshotfrom2019-02aak9p.png (runs some ads, sorry, free service).
This beaviour is consistent, in document history, recently updated and all other views....
Basics have been checked, like system date. Database is Mysqld 5.7.25 and the connector version 8.x.. Has been like this for almost a year and this problem never occurred so far.
Really appreciate any good hint.
Cheers,
Michael
Hi Michael,
mm stands for minutes, and MM stands for months:
I suspect because you used mm instead of MM, it's showing the minutes rather than the months.
Could you have a look and let me know?
Regards,
Shannon
Hi Shannon,
thanks for your reply.
I just checked the current, active format in 'general config', which is:
Indexing Language German
Encoding UTF-8
Time Format hh:mm
Date Time Format dd.mm.yyyy, HH:mm
Date Format dd.mm.yyyy
I restored an older backup and found it was like this before:
yyyy-mm-dd, HH:mm
yyyy-mm-dd
So, as far as the variables go, the only thing that changed is the order, so I drilled deeper and nagged a few people, which brought to light someone "tweaked" this setting and the big appeared before the order was switched (from US to German style).
So, in short, I checked the link you posted and of course it has to be different.
This worked for me: dd.MM.yyyy
And if I knew something about Java, I might have known about SimpleDateFormat class :D
Thanks a lot. Easily fixed.
Regards,
Mike
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Happy to hear you were able to resolve this! I used to see the problem a lot back when I worked on the Cloud team, so when I saw your post I knew immediately what it could be.
Take care, and have a pleasant week.
Regards,
Shannon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.