diff options
| author | Nicolas Lempereur <nle@odoo.com> | 2017-03-16 16:07:29 +0100 |
|---|---|---|
| committer | Nicolas Lempereur <nle@odoo.com> | 2017-03-16 22:07:29 +0100 |
| commit | fb05d8845d92b1ca9013307664fa6d52be64aa3d (patch) | |
| tree | ae10220f8b12bd860d07f4796d87afe30ff83e11 /addons/web_editor/static/src/xml/backend.xml | |
| parent | f50ba68be72c8b63af87e8dcd0e726e5e3b77092 (diff) | |
[FIX] web_calendar: events not appearing in arabic
Fullcalendar expect as `start` and `end` property of an event object:
> When specifying Event Objects for events or eventSources, you may
> specify a string in IETF format (ex: "Wed, 18 Oct 2009 13:00:00 EST"),
> a string in ISO8601 format (ex: "2009-11-05T13:15:30Z") or a UNIX
> timestamp.
(as seen in https://fullcalendar.io/docs1/event_data/Event_Object/)
Before this commit we could for example in arabic provide an invalid
date string "٢٠١٧-٠٣-١٦ ١٦:٠٠:٠٦" instead of "2017-03-16 16:00:06".
This commit solves this by always providing fullcalendar an ISO8601 date
string.
opw-705752
Diffstat (limited to 'addons/web_editor/static/src/xml/backend.xml')
0 files changed, 0 insertions, 0 deletions