| .. |
|
acp_attachments.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_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
|
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_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, 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_groups.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_icons.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_jabber.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_language.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_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
|
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_modules.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_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
|
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_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
|
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_search.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_styles.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_users.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_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 |
