In previous versions of myPHPNuke, the admin menu would read the directory structure under the admin directory to find out what directories were available, extract the contents from those directories and build it's menu contents. From now on, the admin menu is not dynamically created anymore but is based on the number of arrays that divide all menu options in logical grouped drop down boxes. The advantage of this approach is that you can store anything in the admin directory without worrying about the site crashing because you don't have an item.php file.
The links in the menu are stored in two different places. To make it easier to modify these blocks they are separated into separate files that hold only the appropriate array. The arrays them selfs are pretty self-explanatory.
Keep in mind -> anything you add to either one of those arrays will only be available to super admins unless you make other adjustments in admin/menu/adminMenu.php.
The new directory in admin/menu is 'inc'
Submenus that are derived from top level menu items are a little more complex since permissions become more of a factor than the top level menus. While permissions are still a factor in top level menus, the config menu is only available to super admins, and each module item has it's own set of "allowed" admins beyond super user admins depending on what sub items that menu entails.
For example: database & misc. utilities are restricted to super user admins while articles & topics will be shown to super users AND admins with either article, topic, or auto article privileges.
Then each submenu is further split based on each section allowed admins. For articles this means: Admins with article permissions can view all submenu items in Article & Topics Section Admins with Topic Only will only get the submenu item "topics", all other menu items will be removed
|User Contributed Notes
|There are no user contributed notes for this page.|