Posted by aidanlis on April 11, 2010 at 8:30am
Patch manager provides a developer tool for managing patches to core and contributed modules.
Patching core or contributed modules introduces a host of maintainability problems when it comes time to upgrade.
- patch files get lost, developers must re-find patches after each upgrade
- patch files conflict after an upgrade, no one can remember why the patch was made in the first place leading to regressions
- modules aren't upgraded because they were once patched and now it's difficult to work out if the problem has been fixed upstream
This module provides a solution to all of these problems:
- patches are stored on the filesystem, and tracked with the patch manager
- patches can be applied and rolled back with a button click
- an administration interface lists each patch along with the module, description and issue numbers
- patches are stored as nodes, allowing extra patch information to be added with CCK (e.g. redmine or trac issue numbers)
- notification of when the drupal.org issue status changes [in the next version]
This module requires the following modules:
- views
- cck (text submodule)
- filefield
- views_bulk_operations (optional)
See the README.txt for more information.
You might also like the hacked module.
Project Information
- Maintenance status: Actively maintained
- Development status: Under active development
- Module categories: Developer, Utility
- Reported installs: 142 sites currently report using this module. View usage statistics.
- Last modified: November 4, 2011