Utility

litwol - March 20, 2007 - 04:00

The Utility module is a grouping of commonly-needed utilities that are simple to code, everyone wants, but nobody actually codes them.

Right now, we have the following features:

Collapse the module page's fieldsets.
This utility automatically collapses fieldsets on the admin/build/modules page. This speeds up the enabling or disabling of modules, since only the set of modules you're interested in can be expanded for editing. Why wade through all your modules every single time you go to this page? Collapse them!

There is also a counter for each fieldset that numbers every module in that group and reports on how many are enabled. Example: Core - optional [9] of [23]

Module Weight
This utility allows you to change module weights without having to make the change directly in the database. Very helpful for development or modules that require to be run in specific order.

Permissions Fieldset Manager
Similar to the System Modules above, except this encloses the permissions (admin/user/permissions) for each module in a fieldset. Those may either be all collapsed/expanded, or individually.

Type Defaults
This is a feature that sets all publishing and comment options for all content types. It also has the ability to exclude certain types.

Log_Clear
Looking at your logs and wishing you could get rid of just "this kind of message?" Too lazy to fire up PHPMyAdmin to do it (isn't that what Util is for). In searching DO, it seems there are lots of others who would like this.

So here is a function that adds a "Clear" button in the "Filter log" field set on the "Recent log" page. Note: This does not show up on the Util page at all.

Logged_in_as
Ever code up a little block to show user id and maybe roles? Well, here it is. Note: This does not show up on the Util page at all.

Please add feature requests for anything you want.

Version Status

With the increasing adoption of Drupal 6 and the maturing of D7, we feel the time has come to place our 5.x-1.x version into “maintenance only” mode. From now until we release a 7.x version there will be no new development on the 5.x-1.x version; we will, however, provide a best effort to fix bugs.

Issues

As with all contributed modules, when considering submitting an issue review the existing issues list. (Don't forget to select "<all>" for the "Status" field.)

  • Gather all the appropriate information. This may include (but is not limited to):
    • Drupal version.
    • Browser type and version.
    • Database type and version.
    • Error messages, if any.
    • Module settings.
  • Submit the issue. If other modules are involved, you may need to submit the issue to those modules as well.
  • PHP prior 5.2 and MySql 4

    Due to end-of-life on PHP4 and MySql4, we no longer actively support either of those products. If a problem arises, we will make an effort to work around it, but will not make a guarantee. Drupal 7 will require PHP 5.2 or higher and MySql 5 (or Postgres 8); if your host is not at these levels yet, please encourage them to get there ASAP.

    Update.php

    As with all modules, please make sure you run update.php after updating this module, even if no updates are identified.

    Development version status

    The development versions (-dev) are where the newest stuff is, including any bug fixes and new features. We try to make sure it is tested before we commit anything, but occasionally a bug will get by us. Your help on testing this code is greatly appreciated.

    Current Features being tested in Development
    Update.php required: Yes

    Releases

    Official releasesDateSizeLinksStatus
    6.x-2.32008-Jun-0511.77 KBRecommended for 6.xThis is currently the recommended release for 6.x.
    Development snapshotsDateSizeLinksStatus
    6.x-3.x-dev2009-Oct-1024.47 KBDevelopment snapshotDevelopment snapshots are automatically regenerated and their contents can frequently change, so they are not recommended for production use.


     
     

    Drupal is a registered trademark of Dries Buytaert.