"value":"\n <p>I've worked on a lot of Drupal projects and there have been times when previous Developers have \"hacked\" Drupal core or contrib modules by editing them to add or change functionality.<\/p>\n\n<p>This is a short-sighted approach, as any changes to third-party code such as Drupal core or contrib modules would be lost when a new version is downloaded.<\/p>\n\n<p>Most of the time, changes can be made within custom code that won't be overwritten and accidentally lost.<\/p>\n\n<p>But in cases where the source code needs to be changed, <a href=\"\/daily\/2025\/01\/14\/patching-drupal\">you can patch files instead<\/a>.<\/p>\n\n<p>You can commit the patch file to your project to save the changes, but you're responsible for maintaining it and ensuring it applies to any future updates of the code.<\/p>\n\n<p>If you can, commit the changes upstream.<\/p>\n\n<p>Then you won't need to patch files and others will benefit from the contribution.<\/p>\n\n ",
"processed":"\n <p>I've worked on a lot of Drupal projects and there have been times when previous Developers have \"hacked\" Drupal core or contrib modules by editing them to add or change functionality.<\/p>\n\n<p>This is a short-sighted approach, as any changes to third-party code such as Drupal core or contrib modules would be lost when a new version is downloaded.<\/p>\n\n<p>Most of the time, changes can be made within custom code that won't be overwritten and accidentally lost.<\/p>\n\n<p>But in cases where the source code needs to be changed, <a href=\"http:\/\/default\/daily\/2025\/01\/14\/patching-drupal\">you can patch files instead<\/a>.<\/p>\n\n<p>You can commit the patch file to your project to save the changes, but you're responsible for maintaining it and ensuring it applies to any future updates of the code.<\/p>\n\n<p>If you can, commit the changes upstream.<\/p>\n\n<p>Then you won't need to patch files and others will benefit from the contribution.<\/p>\n\n ",