translation missing: zh-TW, field_time_entrie
I got this error message when I typed an invalid number to the time entry.
translation missing: zh-TW, field_time_entries 是無效的
Updated by Ondra Starek over 13 years ago
- Status changed from Closed to Reopened
I can reproduce this issue (I'm using Redmine from the trunk in revision 3735):
- create a required custom field for spent time,
- create new time entry without value in the field.
One of the two error messages, which appear as a result of these steps, is the message reported in this ticket.
Updated by Holger Just over 13 years ago
I can also reproduce this. It only occurs, if you try to create a TimeEntry during an issue update while that particular TimeEntry does not validate.
This is probably cause by a change to the behavior during issue update. The cause is probably in Issue#save_issue_with_child_records.
Updated by Raghu Sunderam over 13 years ago
Even i can reproduce this issue.
This issue appears to be very obvious.
I don't know how it missed your developers eyes.
Steps to reproduce
1) Create an issue and fill all required fields
2) Update the issue by entering a perfectly valid value in "Spent time" field, but don't select any options in "Activity" drop down list.
The issue appears to be not in validating the value entered in "Spent time" field, as 3, 7 are all perfectly valid values for Hour based field.
More the issue also not appeared to be related to Translation.
As i have using US English version, for that it self i am getting the following error.
"translation missing: en,
field_time_entries is invalid"
Updated by Felix Schäfer over 13 years ago
- Category changed from Translations to Issues
- Assignee changed from Azamat Hackimov to Holger Just
My guess is the "extra" validation error happens here source:/trunk/app/models/issue.rb#L495 . The problem appears to happen when you try to add an invalid time entry while updating the issue, this does not happen when logging time "on its own" through the "Log time" link. The flash then shows the validation errors for the TimeEntry as well as an error that the TimeEntry is invalid (probably as part of the error messages from the issue).