Cleaning up administration module for 4.7
recidive - June 22, 2006 - 10:16
| Project: | Administration |
| Version: | HEAD |
| Component: | Code |
| Category: | feature request |
| Priority: | critical |
| Assigned: | recidive |
| Status: | needs work |
Description
Here is a patch that fixes several bugs found in administration module from cvs. Also, this patch adds the features in civicspace's zadministration module and civicspace.inc.
Features added:
- A "Switch to classic view" link at the top of dashboard page and a "Return to administration front page" for dashboard subpages;
- Move admin and admin/settings items to a single "configure modules" page in civicspace.inc;
- Improve menu generation process;
- New theming for civicspace.inc;
- A 'after_build' property to the
$configarray, this sets a function to be called after the menu generation process;
Bugs Fixed:
- Module settings not being saved (improved the administration settings form);
- Load the right CSS file;
- Remove empty sections/sub-panels and menu items of disabled/not installed modules;
- Remove deprecated zadministration.module;
- Added administration.install script that sets the weight of the module, so its functions are called finally.
The module is working fine with Drupal 4.7 and this patch, we need just to do some further tests.
Comments please!
| Attachment | Size |
|---|---|
| administration_4.patch.txt | 68.26 KB |

#1
Here is the images for the civicspace.inc theme. All images had to be in administration/images directory.
#2
I've striped out the patch with only the bugfixes part. Here is a more detailed list of the changes:
As soon as this patch has been commited I'll submit another one introducing the features we've made into the civicspace profile.
#3
I've only had a chance to do a cursory code review and testing with on this on 4.7.2. I'm going to go ahead and commit these changes but not move the 4.7 tag yet. I would really like a few people to take it and run it through it's paces before I tag it.
I'll change this to "fixed" and if people find issues with it we can reopen it.
Also, feel free to submit the second (feature) patch but I'm not even going to consider it until we're happy we these changes and they are tagged as 4.7
So, anyone willing to test this please download the CVS/HEAD version and post your findings back here.
#4
I tested the following:
* Module settings not being saved (improved the administration settings form);
I tested the form and changed between all the available menu's both disabled and enable and everything worked.
* Load the right CSS file;
I tested Default, CivicSpace, and Combined and each had a different CSS.
* Remove empty sections/sub-panels and menu items of disabled/not installed modules;
I enabled and disabled modules and they were accurately reflected in the interface. I need to test sections like Mail and subscription
* Remove deprecated zadministration.module;
Great.
* Added administration.install script that sets the weight of the module, so its functions are called finally.
This is a nice improvement over having to alphabetize the module.
#5
The patch looks ok to me. However, I didn't test it and I am also not very familiar with the module.
#6
We're newbies. We installed the civicspace distribution two days ago and the install went well. We are still exploring its capabilities (we come from Joomla world).
I then noticed the "switch to classic view" and thought it might provide a simplified menu structure, so i clicked it.
Bad things happened:
1. the ?q=sadmin querystring format changed to /sadmin
2. the only visible page was an Administrator page with a log of administrative actions - no other menus and no obvious way to get to any menus.
I poked around in a parallel installation that was still in the original format and found that the switch called a ?q=deactivate parameter. I took a chance and tried "/activate." It partially worked. It didn't restore the ?q= capability, but it brought back a stripped down version of the administrative dashboard.
Any help would be appreciated. We are still early in development and we can reinstall, but I would like to avoid this occurring again. If it did, I would like to be able to recover.
VU
#7
Setting this to "code needs work" due to grapes reported issues. I don't have time to test this today but if the original patch author has time to look at it that would be great.