summaryrefslogtreecommitdiff
path: root/addons/web/static/src/js/framework/session_instance.js
diff options
context:
space:
mode:
authorDenis Ledoux <dle@odoo.com>2016-05-10 16:05:47 +0200
committerDenis Ledoux <dle@odoo.com>2016-05-10 16:09:28 +0200
commita0366b3a66dd6e20bbc7ff7ffe8026779011859b (patch)
tree9e04726e6f4adb5f6046ea7a49a720233e85067e /addons/web/static/src/js/framework/session_instance.js
parent3954affc302143e98c98b2cc334c42d803f72847 (diff)
[FIX] google_calendar: do not copy user Google info
If a user syncs his calendar with Google, and a second user is created in the database by copying this first user, the Google information of the first user was copied (The Google account to sync, the token to use, the last syncrhonization date, ...), which is obviously wrong. On calendar syncrhonization, which can be done manually or automatically with the according cron, all events of the first user were created a second time, as a second user synchronized the same Google Calendar. opw-674141
Diffstat (limited to 'addons/web/static/src/js/framework/session_instance.js')
0 files changed, 0 insertions, 0 deletions