phpBB :: Knowledge base - Viewing article MOD Database Requirements

MOD Database Requirements

Here is a list of what is required in order for MODs to be accepted in to the MOD Database. If a MOD doesn't follow these requirements, it will be denied and the author will receive a private message saying it was denied and the reasons why it was denied.

MODs must use the MOD Template correctly
MODs must be written for subSilver. You may provide changes to other styles as well (see point s for packaging information)
MODs must be written in/for the English language (en-GB preferred). However you may supply the MOD with other languages (see point s for packaging information)
The owner/author of the MOD must be the one to submit it to the database
MODs must be written for the most recent version of phpBB within the version line it is written for (version lines are 2.0.x, 2.2.x, 3.0.x, 3.2.x, etc)
MODs must use the Database Abstraction Layer (DBAL) and have no hardcoded database functions (mysql_query, mysql_fetch_array, etc). If you are adding support for a new database type, it must be implemented via the DBAL.
MODs must use the template system and have minimal HTML in the php files. The HTML in the php files must not exceed what is currently found in phpBB.
All HTML found within the MOD (templates or php files) needs to be XHTML 1.0 Transitional compliant
MODs must use the language system so that MODs will work with multiple languages (no hardcoded text except in error messages)
MODs must be secure, this includes securing form variables
MODs must not use functions or anything that isn't included within php 4.1.0, you can use these functions as long as you make it very clear what is required (saying that php 5.0.4 is required in the author notes is acceptable)
MODs must do what the description and title of the MOD says it does
MODs must use $phpbb_root_path and append_sid appropriately
MODs must use measures to prevent sql injection (str_replace("\'", "'', $foo), addslashes(), and any other preventive measures)
MODs use the different polices in place like reserving a PAGE_ constant as well as any other polices in place
MODs must be bug free
The version of the MOD needs to signify that it is a stable release (see this article for more information)
At this time, MODs may not include anything stating that it is EasyMOD Compliant (please read this post)
MODs can either be compressed zip packages or a single .mod file. Zip packages need to be laid out in a way that the install file is easy to find and all add ons need to be put within a folder named 'contrib'. Translations need to go in a folder named 'translations' and it must be clear what each language each translation is.

There may be other things that your MOD may be denied for that isn't in this list. It is up to the MOD Team member who is looking at your MOD to make the final decision. If you don't think your MOD should have been denied, either a private message the person who denied or MOD or to the MOD Team Leader, wGEric.

Some good articles to read can be found in this topic. Some good articles that I would like to point out are: