In the CMS world, a patch is a small text file which contains a set of changes to make to some code, usually a module or plugin.
You may have already heard the term patchin the context of other software, such as the security patches that Microsoft releases for the Windows operating system. That kind of patch is a similar idea: it's a small piece of software that changes a larger program.
But for a CMS, such as WordPress or Drupal, patches are slightly different.
A Microsoft security "patch" is designed to be applied automatically, but a CMS "patch" is usually a change that will not be applied automatically.
When CMS developers want you to apply changes automatically, they'll release an update, such as a Drupal "minor update". A patch, on the other hand, is an optional change, usually not from the official developers, and you have to run some specialized commands to apply it.
On a CMS, a patch is a way to get special changes right away, instead of waiting for the developer to get around to rolling these changes into an official update. So don't think of CMS patches the way you think about obligatory security patches with other software. If CMS developers think you need to apply security changes, they'll release an update.
The Drupal community is especially active in their use of patches. They encourage you to improve the code and post your changes as a patch, so that others (including the developers) can try your patch. If a patch is helpful, developers will often roll the patch into the official code for the module.
When you have a problem with a module, you may find the solution as a patch. Read more about when (and whether) to patch a Drupal module.
You may have already heard the term patchin the context of other software, such as the security patches that Microsoft releases for the Windows operating system. That kind of patch is a similar idea: it's a small piece of software that changes a larger program.
But for a CMS, such as WordPress or Drupal, patches are slightly different.
A Microsoft security "patch" is designed to be applied automatically, but a CMS "patch" is usually a change that will not be applied automatically.
When CMS developers want you to apply changes automatically, they'll release an update, such as a Drupal "minor update". A patch, on the other hand, is an optional change, usually not from the official developers, and you have to run some specialized commands to apply it.
On a CMS, a patch is a way to get special changes right away, instead of waiting for the developer to get around to rolling these changes into an official update. So don't think of CMS patches the way you think about obligatory security patches with other software. If CMS developers think you need to apply security changes, they'll release an update.
Patches and Drupal
The Drupal community is especially active in their use of patches. They encourage you to improve the code and post your changes as a patch, so that others (including the developers) can try your patch. If a patch is helpful, developers will often roll the patch into the official code for the module.
When you have a problem with a module, you may find the solution as a patch. Read more about when (and whether) to patch a Drupal module.
SHARE
