Patch listing page

Patch manager provides a developer tool for managing patches to core and contributed modules.

Scary warning
Please think about Patch Manager module as a developer tool that should never be used on production sites. That is so because to apply patches Patch Manager relies on write access to source code of your site by server user. To use this module you need to change default file permissions of files that you want to patch, apply patch and then set permissions back to default. Doing it on production site could lead to security issues - so don't even think about it!



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 those 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 issue status changes [in the next version]


This module requires the following modules:

See the README.txt for more information.

Related modules

Possibly better solution is to use Drush to apply patches (see its make command) or Drush extension Drush Issue Queue Commands because they don't rely on insecure configuration.

You might also like the hacked module.

Project information