Opened 16 years ago
Closed 15 years ago
#8136 closed defect (duplicate)
Trac does not work when server date format is set to Bulgarian
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | i18n | Version: | 0.11.2.1 |
| Severity: | major | Keywords: | datetime locale |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
I'm using Trac 0.11.2.1 on Windows Server 2003 x64, ActiveState Python 2.5 and Apache 2.2.10. The server system language (Control Panel → Regional Settings) is set to Bulgarian, and particularily, the date format is set to dd.M.yyyy 'г.' (note the special suffix)
Trac fails everywhere dates are involved. I cannot create milestones. I cannot view the repository changes in the timeline.
The error reported is similar to:
Error: Invalid Date "17.3.2009 г." is an invalid date, or the date format is not known. Try "DD.MM.YYYY г." instead.
Additional bug: The suggested date format does not work! If I enter the date in the suggested format, I receive the same error. The format that works is the ISO one, YYYY-MM-DD.
For us this is a blocker, as I said we cannot even create milestones. Before we find by sheer luck that ISO dates work, we edited the database manually.
Attachments (0)
Change History (3)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
| Keywords: | datetime locale added |
|---|---|
| Milestone: | → 0.11.5 |
| Severity: | critical → major |
| Version: | 0.11-stable → 0.11.2.1 |
comment:3 by , 15 years ago
| Milestone: | 0.11.6 |
|---|---|
| Resolution: | → duplicate |
| Status: | new → closed |
Superseded by #2182, the locale shouldn't be taken into account.
Note: the command-line tool trac-admin has the same behaviour as the web interface.