Difference between revisions of "Module"
From TUTOS
Iqelekosaba (Talk | contribs) |
|||
Line 1: | Line 1: | ||
+ | ---- | ||
+ | <div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;"> | ||
+ | ---- | ||
+ | =[http://ehyloxame.co.cc This Page Is Currently Under Construction And Will Be Available Shortly, Please Visit Reserve Copy Page]= | ||
+ | ---- | ||
+ | =[http://ehyloxame.co.cc CLICK HERE]= | ||
+ | ---- | ||
+ | </div> | ||
A TUTOS module is a feature that could be simply attached to a existing TUTOS System. | A TUTOS module is a feature that could be simply attached to a existing TUTOS System. | ||
Physically it is a subdirectory within the TUTOS installation. | Physically it is a subdirectory within the TUTOS installation. | ||
Normally the admin only needs to include a module config file (mconfig.pinc) into the main config file ([[config.php]]) to activate a module. | Normally the admin only needs to include a module config file (mconfig.pinc) into the main config file ([[config.php]]) to activate a module. |
Revision as of 08:03, 24 November 2010
A TUTOS module is a feature that could be simply attached to a existing TUTOS System. Physically it is a subdirectory within the TUTOS installation.
Normally the admin only needs to include a module config file (mconfig.pinc) into the main config file (config.php) to activate a module.