diff options
| author | Denis Ledoux <dle@odoo.com> | 2016-05-09 11:31:45 +0200 |
|---|---|---|
| committer | Denis Ledoux <dle@odoo.com> | 2016-05-09 11:39:38 +0200 |
| commit | 7923999f1280f39c6505d2615b8bc1312cad0fb7 (patch) | |
| tree | 4bc50659960d193b58e93066e11328df1ec47a2b /addons/web/static/lib/jquery.mjs.nestedSortable/jquery.mjs.nestedSortable.js | |
| parent | dd714ace55bd70a855e660ff67823144163b6dce (diff) | |
[FIX] google_calendar: user invited to one recurring event occurence only
When a Google user was invited to one occurrence of a recurring event,
but not to the recurring event itself (and the other occurrences, therefore),
and the user owner of the recurring event did not sync his calendar in Odoo,
the event occurrence could not be synced in Odoo, because it attempted
to attach it to the parent/main recurring event, which was not present
in Odoo.
In such a case, Odoo now syncs the event occurrence as a simple classic
event. In addition, if the owner of the event sync his calendar with Odoo
afterwards, or if the user is invited later to the main/parent recurring event
and then sync again his calendar,
it then attach the event occurrence that was previously
synced to this main event, to avoid events duplication.
opw-676535
Diffstat (limited to 'addons/web/static/lib/jquery.mjs.nestedSortable/jquery.mjs.nestedSortable.js')
0 files changed, 0 insertions, 0 deletions
