[Solved] Default Date Display in Custom Status when Language is Set to Japanese

In the “Set a Custom Status” feature, when I try to set “Clear after” with “Choose date and time,” there is an issue with the default date display.

As shown in the image, when the display language is set to English, today’s date is displayed by default. However, when the display language is set to Japanese, the date is displayed as “0006-MM-DD”.

This issue does not occur with other Asian languages (Chinese and Korean).
I am using version 7.8.15, which is self-hosted. This problem does not occur in any other 6.3.6 environment I have tested.

Therefore, it seems that the problem is not with Mattermost itself, but with my 7.8.15 environment.

7.8 is EOL. We highly recommend you update to 8.1.13 and then to 9.5.8

https://docs.mattermost.com/about/version-archive.html

https://docs.mattermost.com/about/release-policy.html

https://docs.mattermost.com/upgrade/upgrading-mattermost-server.html

https://docs.mattermost.com/about/server.html

Thanks for the reply.

I am not able to try the upgrade right away as it is something we use in-house.
Also, since this is not occurring with version 6, I feel it is unlikely that the upgrade will fix the problem.

I am checking to see if the .jsx file regarding date format settings and custom status in json is the cause.
However, I have not been able to find any files that seem to be the cause.

If you have any other information, I would appreciate it if you could point me in the right direction.

I suggest the upgrade not so much that I’m certain that it will fix the issue, as I believe it’s likely to fix the issue (something done after 6.x may very well have caused this, and it was already fixed later) and that because I don’t know the answer, I’d have to ask around, and the first thing anyone would say would be to upgrade :slight_smile:

You could look back in the changelog… I see “Japanese” mentioned several times. Unsupported legacy releases - Mattermost documentation

Thank you for your additional response.
So it could be an effect of the fixes made since version 6?

We are planning to upgrade our current environment in September or October, so I will check at that time.

We have not been able to contact you. Our apologies.
As per your response, we have resolved the issue by upgrading to 8.1.13.
Thank you for your support.

1 Like

Glad to hear the upgrade solved the issue for you, Ryot! Thank you for following up.