contains 4 subfolders (links, language, case, modules) that manage the various administration modules. The folder that contains the operating files is admin/modules, here we have the files that execute the different admin operations.
The folder admin/links instead says which admin module has to be called and puts a link in the admin area for that module.
Example (administration module for the FAQ):
if (($radminsuper==1) OR ($radminfaq==1)) {
adminmenu("admin.php?op=FaqAdmin ", "" _FAQ." ", "faq.gif");
} |
This module:
Verifies that administration rights are present (this module may be managed by either the superadmin or an administrator that has been qualified to do so on the FAQ level),
passes a case (op=FaqAdmin) that says to the admin.php file (that includes all the admin modules) which module to load, associates a value in order to translate the term “faq” and associates an icon for the visual administration (faq.gif).
The folder admin/case instead serves to define which module to use in certain cases. This is important when, using the same admin file, one needs to carry out different operations according to the case passed:
Case1 = insert Case2 = cancel etc... |
In fact it says which module to load on verification of a case. For example, in the module faq the cases are many, let's consider only the last 2:
case "FaqAdmin":
case "FaqCatGo":
include ("admin/modules/adminfaq.php");
break; |
Both cases load the file adminfaq.php but they make it carry out different operations. The first one loads the file in the default scheme, the second one instead gives the O.K. for the insertion of a new category. This happens through a string like
admin.php?op=FaqAdmin |
in the first case and
admin.php?op=FaqCatGo |
in the second.