This project is not covered by Drupal’s security advisory policy.
The Client UI Control module is intended to cleanup and "hide" options from clients that could potentially break a site after site handoff. The first iteration/release of this module simply provides a settings form to select certain themes which should be hidden from view on the theme listing page.
There are many more settings/forms I'd like to modify/hide from my clients, and will be implemented in future releases.
The current feature set of the Client UI Control module is as follows:
- Select themes to hide from the theme listing on /admin/appearance
- Select modules to disallow enabling/disabling on /admin/modules
Hiding themes from the interface
There are two ways to disable themes via the Client UI Control module. If you have not modified your settings.php to disable themes using the $conf method, you will have a form available to disable selected themes at admin/config/user-interface/client_ui_control.
You may also use site specific settings to hide themes from the interface by adding hidden themes in settings.php in your default or site specific directory.
$conf['client_ui_control'] = array(); $conf['client_ui_control']['themes'] = array( 'bartik', 'garland', 'stark', 'seven', );
Disabling modules in the interface
There are two ways to disable modules via the Client UI Control module. If you have not modified your settings.php to disable themes using the $conf method, you will have a form available to disable selected modules at admin/config/user-interface/client_ui_control.
You may also use site specific settings to disable modules from being modified (enabled or disabled) by adding hidden modules in settings.php in your default or site specific directory.
$conf['client_ui_control'] = array(); $conf['client_ui_control']['modules'] = array( 'views', 'views_ui', 'panels', 'context', );
Note: The functionality to "hide" modules differs from themes. When disabling themes, it's easy to hide them completely from the interface, and not worry. However, the same method to actually "hide" using hidden=TRUE on a module actually will make it so it cannot be updated by drush, and will not show updates on the available updates page. The module "disabling" method uses required=TRUE to "lock" the checkbox on the modules list page, making whatever its current state is unchangeable.
Warning: Modules CAN still be enabled disabled via drush, BUT if your client is using Drush, you have a whole other ball of issues to deal with...
If you have a idea on a feature that should be added to this module, please submit an issue.
- Maintenance status: Actively maintained
- Development status: Under active development
- Module categories: Administration
- Reported installs: 60 sites currently report using this module. View usage statistics.
- Downloads: 3,058
- Last modified: 1 December 2014
- This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.