| Summary | "Failed to parse time string" error |
| Queue | Nag |
| Queue Version | 4.2.9 |
| Type | Bug |
| State | Duplicate |
| Priority | 2. Medium |
| Owners | Horde Developers (at) , mrubinsk (at) horde (dot) org |
| Requester | alex (at) mail (dot) fliker09 (dot) tk |
| Created | 05/19/2016 (3458 days ago) |
| Due | |
| Updated | 05/25/2016 (3452 days ago) |
| Assigned | 05/19/2016 (3458 days ago) |
| Resolved | 05/25/2016 (3452 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
Assigned to Michael Rubinsky
State ⇒ Duplicate
Bug: 14348Assigned to
State ⇒ Assigned
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ "Failed to parse time string" error
Queue ⇒ Nag
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
A fatal error has occurred
Failed to parse time string (24/05/2016 15:43)
1. Nag_SaveTask_Controller->processRequest()
/var/www/horde/nag/task/save.php:18
2. require() /var/www/horde/nag/app/controllers/SaveTask.php:16
3. Nag_Form_Task->renderActive() /var/www/horde/nag/task.php:147
4. Horde_Form->renderActive() /var/www/horde/nag/lib/Form/Task.php:190
5. Horde_Form_Renderer->renderFormActive() /usr/share/php/Horde/Form.php:500
6. Horde_Form_Renderer->_renderForm()
/usr/share/php/Horde/Form/Renderer.php:219
7. Horde_Core_Ui_VarRenderer->render()
/usr/share/php/Horde/Form/Renderer.php:274
8. Horde_Core_Ui_VarRenderer_Nag->_renderVarInput_NagDue()
/usr/share/php/Horde/Core/Ui/VarRenderer.php:92
9. Nag_Form_Type_NagDue->getInfo()
/var/www/horde/nag/lib/Ui/VarRenderer/Nag.php:75
10. Nag::parseDate() /var/www/horde/nag/lib/Form/Type/NagDue.php:18
11. Horde_Date->__construct() /var/www/horde/nag/lib/Nag.php:179
I also try to create New Event in Kronolith and got no error. Paying
attention to the dates I observed that there Month/Day/Year format is
used, instead of Day/Month/Year which caused Nag crash. Where is the
problem - on my side or Nag's?