Props
Users can report PMs to moderators which are then visible in a new MCP module
Hiding everywhere little buggers, eh?
This commit was manufactured by cvs2svn to create branch 'phpBB-3_0_0'.
#14621#14596info file changes
- viewtopic/forum search boxes should also use search config option and u_search permission [Bug #9850]- mcp_reports was still using some of the mcp_queue post_id logic, changed enough to report_id logic to make it work properly now. I hope I didn't miss any external places referring to mcp_reports which send it a post_id_list. I really wonder whether people don't test the MCP at all? Good that I noticed this myself when fixing an incorrect language string (No reports selected) message [Bug #9741]...
- check whether config.php exists- add <p> to installation dialogue- forgot to commit an mcp info file
Warn user links #2153
- a few adjustments to permissions, specifically with regard to global topics- forgot to change a line in permission trace [Bug #2100]- syntax highlighting for php5- [Bug #2093]
- various corrections related to permissions in the mcp, including [Bug #1994] and [Bug #1924]- fixed some quickmod bugs [#1994] and [Bug #1898]- browse reports/unapproved posts by topic id- correctly hide approval details- added return message to mcp_ban [Bug #1851]...
Banning makes more sense with usernames listed first, then IP then email as this is the most likely order of use
Fix a couple of issues in mcp_main
Fix a slightly odd naming that we just spotted
Fix the module insertion for UCP and MCP (the changes for the ACP had meant it was going in backwards!)
Remove the module entries from the schema data file and generate the list insteadThis should be the last major item with hard-coded id values in it
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.