From 425b7e52351e36e36c6cdaa6ea4e910d6196e3eb Mon Sep 17 00:00:00 2001 From: Adrian Moennich Date: Tue, 12 Jul 2016 16:47:36 +0200 Subject: [PATCH] LiveSync: Do not check for legacy category --- livesync/indico_livesync/handler.py | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/livesync/indico_livesync/handler.py b/livesync/indico_livesync/handler.py index b88c2c6..9cb4a62 100644 --- a/livesync/indico_livesync/handler.py +++ b/livesync/indico_livesync/handler.py @@ -205,10 +205,8 @@ def _register_deletion(obj): def _register_change(obj, action): if not isinstance(obj, Category): event = obj.event_new - if event is None or event.is_deleted or event.as_legacy is None or event.as_legacy.getOwner() is None: + if event is None or event.is_deleted or event.as_legacy is None: # When deleting an event we get data change signals afterwards. We can simple ignore them. - # When moving an event it's even worse, we get a data change notification in the middle of the move while - # the event has no category... # Also, ACL changes during user merges might involve deleted objects which we also don't care about return _init_livesync_g()