Meik Sievertsen 1a8c91b0d4 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. ...

git-svn-id: file:///svn/phpbb/trunk@5725 89ea8834-ac86-4346-8a33-228a782c2dd0

2006-03-25 19:14:55 +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

mcp_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

mcp_forum.php

- extended session_page and user_lastpage to hold a maximum of 200 chars (instead of 100) - session_page gets truncated to 200 chars

2006-03-25 12:07:13 +00:00

mcp_front.php

adjusting sql_freeresult a bit as well as our error handler (it now prints out if it is because of DEBUG_EXTRA being defined - which is not enabled within the betas/rc's and stable releases).

2006-03-22 17:30:20 +00:00

mcp_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

mcp_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

mcp_notes.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

mcp_post.php

- streamlined reports to consist of the feature set we decided upon (Nils, your turn now)

2006-03-12 23:19:55 +00:00

mcp_queue.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

mcp_reports.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

mcp_topic.php

- a bunch of bugfixes. :P

2006-03-21 19:23:34 +00:00

mcp_warn.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