Meik Sievertsen dd1e25e830 #1340 ... git-svn-id: file:///svn/phpbb/trunk@5753 89ea8834-ac86-4346-8a33-228a782c2dd0		2006-03-29 08:37:33 +00:00
..
info	ok, thought about this now for too long. I think the best solution circumventing memory consumption and not introducing "hacks" is to seperate module information (and probably more in 3.2 for installation/uninstallation) from the main code.	2006-03-25 19:14:55 +00:00
acp_attachments.php	- Bug 1301	2006-03-28 16:46:49 +00:00
acp_ban.php	ok, thought about this now for too long. I think the best solution circumventing memory consumption and not introducing "hacks" is to seperate module information (and probably more in 3.2 for installation/uninstallation) from the main code.	2006-03-25 19:14:55 +00:00
acp_bbcodes.php	ok, thought about this now for too long. I think the best solution circumventing memory consumption and not introducing "hacks" is to seperate module information (and probably more in 3.2 for installation/uninstallation) from the main code.	2006-03-25 19:14:55 +00:00
acp_board.php	added ability to hide coppa groups (mainly applied to permission screens)	2006-03-28 17:10:07 +00:00
acp_bots.php	ok, thought about this now for too long. I think the best solution circumventing memory consumption and not introducing "hacks" is to seperate module information (and probably more in 3.2 for installation/uninstallation) from the main code.	2006-03-25 19:14:55 +00:00
acp_database.php	ok, thought about this now for too long. I think the best solution circumventing memory consumption and not introducing "hacks" is to seperate module information (and probably more in 3.2 for installation/uninstallation) from the main code.	2006-03-25 19:14:55 +00:00
acp_disallow.php	ok, thought about this now for too long. I think the best solution circumventing memory consumption and not introducing "hacks" is to seperate module information (and probably more in 3.2 for installation/uninstallation) from the main code.	2006-03-25 19:14:55 +00:00
acp_email.php	ok, thought about this now for too long. I think the best solution circumventing memory consumption and not introducing "hacks" is to seperate module information (and probably more in 3.2 for installation/uninstallation) from the main code.	2006-03-25 19:14:55 +00:00
acp_forums.php	ok, this should work now (multi-table deletion syntax changed between mysql 4.0 and mysql 4.1)	2006-03-26 11:36:54 +00:00
acp_groups.php	added ability to hide coppa groups (mainly applied to permission screens)	2006-03-28 17:10:07 +00:00
acp_icons.php	- Bug 1301	2006-03-28 16:46:49 +00:00
acp_jabber.php	#1304, #1335, #1336	2006-03-27 21:42:47 +00:00
acp_language.php	- Bug 1301	2006-03-28 16:46:49 +00:00
acp_logs.php	ok, thought about this now for too long. I think the best solution circumventing memory consumption and not introducing "hacks" is to seperate module information (and probably more in 3.2 for installation/uninstallation) from the main code.	2006-03-25 19:14:55 +00:00
acp_main.php	- Bug 1301	2006-03-28 16:46:49 +00:00
acp_modules.php	- Bug 1301	2006-03-28 16:46:49 +00:00
acp_permission_roles.php	ok, thought about this now for too long. I think the best solution circumventing memory consumption and not introducing "hacks" is to seperate module information (and probably more in 3.2 for installation/uninstallation) from the main code.	2006-03-25 19:14:55 +00:00
acp_permissions.php	added ability to hide coppa groups (mainly applied to permission screens)	2006-03-28 17:10:07 +00:00
acp_php_info.php	ok, thought about this now for too long. I think the best solution circumventing memory consumption and not introducing "hacks" is to seperate module information (and probably more in 3.2 for installation/uninstallation) from the main code.	2006-03-25 19:14:55 +00:00
acp_profile.php	ok, thought about this now for too long. I think the best solution circumventing memory consumption and not introducing "hacks" is to seperate module information (and probably more in 3.2 for installation/uninstallation) from the main code.	2006-03-25 19:14:55 +00:00
acp_prune.php	ok, thought about this now for too long. I think the best solution circumventing memory consumption and not introducing "hacks" is to seperate module information (and probably more in 3.2 for installation/uninstallation) from the main code.	2006-03-25 19:14:55 +00:00
acp_ranks.php	ok, thought about this now for too long. I think the best solution circumventing memory consumption and not introducing "hacks" is to seperate module information (and probably more in 3.2 for installation/uninstallation) from the main code.	2006-03-25 19:14:55 +00:00
acp_reasons.php	fixing some bugs	2006-03-28 14:04:55 +00:00
acp_search.php	- correctly use DISTINCT and GROUP BY in search related SQL [Bug #1256]	2006-03-26 01:36:26 +00:00
acp_styles.php	- Bug 1301	2006-03-28 16:46:49 +00:00
acp_users.php	#1340	2006-03-29 08:37:33 +00:00
acp_words.php	ok, thought about this now for too long. I think the best solution circumventing memory consumption and not introducing "hacks" is to seperate module information (and probably more in 3.2 for installation/uninstallation) from the main code.	2006-03-25 19:14:55 +00:00
auth.php	fix additional group related thingy (correctly display memberships)	2006-03-28 17:52:03 +00:00