params|character varying(255)|
|
ord|integer|not null default 1||
|
|
-The rows in tiki_layouts determine what layouts modules get displayed in and where they appear in that layout. These rows are what you are editing on the "Configure Layout" admin page. This brings me to the bug in question. You'll notice there is no groups column in the tiki_layouts table. It appears that currently the "Configure Layout" page is storing the group settings in the tiki_layout_modules table (pehaps rows, cache_time, etc as well -- im not sure). I believe the "configure layout" page should only be modifying columns in the tiki_layouts page. One exception being the case where a module is assigned to a layout before it has been activated on the "Active Modules" page. In this case a row must be inserted in the tiki_layouts_modules table in order to activate it as well as adding a row to the tiki_layouts table. Based on this I think we can just remove the "Groups:" section of the form on the "Configure Layouts" page.
|
+The rows in tiki_layouts determine what layouts modules get displayed in and where they appear in that layout. These rows are what you are editing on the "Configure Layout" admin page. This brings me to the bug in question. You'll notice there is no groups column in the tiki_layouts table. It appears that currently the "Configure Layout" page is storing the group settings in the tiki_layout_modules table (pehaps rows, cache_time, etc as well -- im not sure). I believe the "configure layout" page should only be modifying columns in the tiki_layouts page. One exception being the case where a module is assigned to a layout before it has been activated on the "Active Modules" page. In this case a row must be inserted in the tiki_layouts_modules table in order to activate it as well as adding a row to the tiki_layouts table. Based on this I think we can just remove the "Groups:" section of the form on the "Configure Layouts" page. |
|
-You'll also notice that the "Configure Layouts" page does not have the uber-complex javascript madness that the "Active Modules" page does. The reason I wrote all that javascript is so module options can be recalled for any module in the list. Otherwise the options for modules are lost every time they are displayed (e.g. the "Configure Layouts" page).
|
+You'll also notice that the "Configure Layouts" page does not have the uber-complex javascript madness that the "Active Modules" page does. The reason I wrote all that javascript is so module options can be recalled for any module in the list. Otherwise the options for modules are lost every time they are displayed (e.g. the "Configure Layouts" page). |
|
-So that's my basic rundown of how I see module management working. I hope this has made some sense. If I've been unclear or omitted anything just ask and I'll try to answer to the best of my ability. It's been a while since I've looked at any of this code so I could slightly wrong about some of the details. Anyway, if anyone wants to try and tackle this bug (or the other issue that is solved by the javascript on the "Active Modules" page but is still a problem on the "Configure Layouts" page) then go for it! Otherwise I'll get to it when I get a chance. I'm pretty swamped with other stuff right now but I'll try and knock ASAP unless someone beats me to it.
|
+So that's my basic rundown of how I see module management working. I hope this has made some sense. If I've been unclear or omitted anything just ask and I'll try to answer to the best of my ability. It's been a while since I've looked at any of this code so I could slightly wrong about some of the details. Anyway, if anyone wants to try and tackle this bug (or the other issue that is solved by the javascript on the "Active Modules" page but is still a problem on the "Configure Layouts" page) then go for it! Otherwise I'll get to it when I get a chance. I'm pretty swamped with other stuff right now but I'll try and knock ASAP unless someone beats me to it. |
|
Cheers,
|
Andrew Slater |
+!Module Layout Defaults |
+The following is an excerpt of code, used as default module layout values during installation. The code is found in __<package>/admin/schema_inc.php__ and will insert a module into the layout (as part of the install), using the following parameters. |
+{CODE()}$moduleHash = array( |
+ 'mod_server_stats' => array( |
+ 'title' => 'Server Statistics', |
+ 'groups' => array( 'Admin' ), |
+ 'ord' => 2, |
+ 'pos' => 'r', |
+ 'module_rsrc' => 'tikipackage:kernel/mod_server_stats.tpl' |
+ ), |
+); |
+$gTikiInstaller->registerModules( $moduleHash );{CODE} |