| 1 |
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
|
| 2 |
;; Update form enhancement module for Drupal
|
| 3 |
;; $Id$
|
| 4 |
;;
|
| 5 |
;; Original author: markus_petrux at drupal.org (September 2008)
|
| 6 |
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
|
| 7 |
|
| 8 |
OVERVIEW
|
| 9 |
========
|
| 10 |
|
| 11 |
The update_form_enhancement module enhances update.php user interface by
|
| 12 |
separating modules that are up to date from those that are not.
|
| 13 |
|
| 14 |
It uses standard form_alter hook to alter the form that is displayed on second
|
| 15 |
step of update.php script to select modules that need to be updated.
|
| 16 |
|
| 17 |
When all modules are up to date, a message is displayed for the site admin and
|
| 18 |
the update form remains unchanged. The site admin can still reapply any update
|
| 19 |
task should (s)he needs to.
|
| 20 |
|
| 21 |
When all modules have pending update tasks, a message is displayed for the site
|
| 22 |
admin and the update form remains unchanged. This particular scenario may never
|
| 23 |
happen, but anyway...
|
| 24 |
|
| 25 |
When some modules have pending updates and some are up to date, they are
|
| 26 |
grouped into separated collapsible fieldset. The fieldset used to group modules
|
| 27 |
with pending updates is displayed first and expanded, so site admins can
|
| 28 |
easilly check what's pending. The fieldset used to group up to date modules is
|
| 29 |
rendered last and collapsed.
|
| 30 |
|
| 31 |
|
| 32 |
|
| 33 |
INSTALLATION
|
| 34 |
============
|
| 35 |
|
| 36 |
- Copy the contents of this package to your modules directory.
|
| 37 |
- Goto admin/build/modules to install the module.
|
| 38 |
- That's all.
|
| 39 |
|
| 40 |
|
| 41 |
SUPPORT
|
| 42 |
=======
|
| 43 |
|
| 44 |
- Please use the issue tracker of the project at drupal.org:
|
| 45 |
|
| 46 |
http://drupal.org/project/update_form_enhancement
|
Parent Directory
| 
Revision Log
| 
Revision Graph