From e90692bc720cf4c520ee36c603395cf1e1b80b45 Mon Sep 17 00:00:00 2001
From: marcus <marcus@36083f99-b078-4883-b0ff-0f9b5a30f544>
Date: Fri, 9 Jan 2009 14:21:48 +0000
Subject: Closes #668: Banning now works through a flag in the users_entity
 table. Database upgrade required. * Added ElggUser::isBanned(); * Added
 'banned' column to users_entity * Modified ban() and unban() * Modified pam
 functions to check $user->isBanned() * Modified login() to check
 $user->isBanned() * Modified sessions_init() to check isBanned() and destroy
 session accordingly * Modified profile views to highlight banned users and
 prevent menus for non-admin users.

git-svn-id: https://code.elgg.org/elgg/trunk@2554 36083f99-b078-4883-b0ff-0f9b5a30f544
---
 engine/schema/upgrades/2009010901.sql | 3 +++
 1 file changed, 3 insertions(+)
 create mode 100644 engine/schema/upgrades/2009010901.sql

(limited to 'engine/schema/upgrades/2009010901.sql')

diff --git a/engine/schema/upgrades/2009010901.sql b/engine/schema/upgrades/2009010901.sql
new file mode 100644
index 000000000..29eb68f29
--- /dev/null
+++ b/engine/schema/upgrades/2009010901.sql
@@ -0,0 +1,3 @@
+-- Add banned column refs #668
+ALTER TABLE `prefix_users_entity` ADD COLUMN `banned` enum ('yes', 'no') NOT NULL default 'no' AFTER `code`;
+
-- 
cgit v1.2.3

