From 3efaedbbec2078a425631b9d5d70cd9c5d954778 Mon Sep 17 00:00:00 2001 From: TLSM Date: Thu, 22 Sep 2022 20:45:59 -0400 Subject: [PATCH] Temporarily fix permas propagating as shadows. --- files/classes/user.py | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/files/classes/user.py b/files/classes/user.py index fc9abc2aa7..c8db922e0c 100644 --- a/files/classes/user.py +++ b/files/classes/user.py @@ -840,11 +840,14 @@ class User(Base): g.db.add(self) g.db.commit() return - if u.is_suspended_permanently: - self.shadowbanned = u.banned_by.username - g.db.add(self) - g.db.commit() - return + ## Disabled pending better solution: permabans haven't propagated for + ## most of Summer 2022. We've gotten somewhat used to this. Think we only + ## want them to propagate on account creation? Or at least needs discussion. + # if u.is_suspended_permanently: + # self.shadowbanned = u.banned_by.username + # g.db.add(self) + # g.db.commit() + # return @property @lazy