Start a New Discussion
ReadyNAS Board Restructure Coming Soon - Please Read and Comment
World's First Mesh WiFi System with Amazon Alexa Built-in and Harman Kardon Audio - Orbi Voice
NETGEAR Insight Pro Network Management System enables higher profitability for Resellers
A Huge Step Forward for Insight is Here! #Blog
NETGEAR Insight IM5.0 Network Management Now Available
The NEW Nighthawk Pro Gaming Router & Nighthawk Pro Gaming Switch - Power To Win!
Introducing Orbi Pro - Secure and Simple WiFi for Your Small Business
The log message pop-up window needs to have the date localised. That means 7th Feb 2016 here...
I don't see any problem with the date format of the warning or alert of your backup job. The same format is being used by ReadyNAS replicate as well.
NETGEAR Community Team
@BrianL You may be from North America? Where 07/02/2016 means July 2nd.
Many other areas have dates where that would mean 7th Feb.
Everywhere else* in the user interface I have looked displays the date in the long form, as per the left right of the screen shot, 'short-day' mmm dd yyyy
As I can't see a localise setting, unless it is based on time-zone, I assume there was a design choice to use the above long form to get around the dd/mm v's mm/dd confusion.
* System Log, Backup Job logs & Job list, System Device Time# (& pop-up settings), UPS Alert Emails, Share file listings...
# everywhere else uses 24hr time format, I can't see why Devive Time uses AM/PM...and add the Alarm time above too, should be 24hr.
The Volume Schedule shows as dd 'long-month' which could probably change to dd mmm IMO
I see value in providing more time and date formatting options for the web ui (and others have asked for that).
Since log files are also used by netgear support, it would be problematic to have multple date formats there. Netgear would need to make sure that any alternative date formats were self-descriptive. That is, they can't allow 07-02-2016 to mean either July 2nd or Feb 7th depending on a localization setting. They could possibly allow 2-July-2016.
I can't edit the OP.
Let me rephrase. And I'm just talking about the Web GUI.
Chane the Alert display pop-up to use the format that is already used everywhere else. (which also includes 24h time)
(I had presumed the dates everywhere else were localised, hence the title)
Whether that is localised, if that happens via time-zone, or just globally 'short-day' mmm dd yyyy, whatever.
I did not intend to ask for localisation everywhere. Or in the internal logs.
ATM it is inconsistent, which can lead to bad errors if someone confuses the date.
While at it, fix the only other place where 12h time is used (Device Time).
BTW, "Since log files are also used by netgear support, it would be problematic to have multple date formats there.", I just looked at some of the downloaded system logs, they have a very varied range of dates/times, if they have them at all.
@Michael_Oz wrote: I just looked at some of the downloaded system logs, they have a very varied range of dates/times, if they have them at all.
Yes. But that is different from having a specific log file that has 07-02-2016, with the interpretation of that string depending on a localization setting somewhere else.
I suspect customizing the GUI w/o changing the format in the logs themselves would be difficult. It might be better to just to use 02-July-2016 everywhere. Personally I'd be fine with 24 hour times.
Sorry for coming in late, but standardising on a single date format that is unable to be misinterpreted across the board would help.
The YYYY-MM-DD format of 2017_07_02 is the 2nd of July 2017 no matter where you are... it takes a bot of getting used to, but worth a thought.
All logs should use ISO 8601 date formats (like YYYY-MM-DD). See https://en.wikipedia.org/wiki/ISO_8601. County and user background don't and shouldn't matter.
All displayed dates and times should be displayed as preferenced by the user using the UI.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.