{ "uuid": [ { "value": "fb679f64-e559-4319-9a36-b508bc870415" } ], "langcode": [ { "value": "en" } ], "type": [ { "target_id": "daily_email", "target_type": "node_type", "target_uuid": "8bde1f2f-eef9-4f2d-ae9c-96921f8193d7" } ], "revision_timestamp": [ { "value": "2025-05-11T08:59:58+00:00" } ], "revision_uid": [ { "target_type": "user", "target_uuid": "b8966985-d4b2-42a7-a319-2e94ccfbb849" } ], "revision_log": [], "status": [ { "value": true } ], "uid": [ { "target_type": "user", "target_uuid": "b8966985-d4b2-42a7-a319-2e94ccfbb849" } ], "title": [ { "value": "Don't hack core" } ], "created": [ { "value": "2025-05-01T00:00:00+00:00" } ], "changed": [ { "value": "2025-05-11T08:59:58+00:00" } ], "promote": [ { "value": false } ], "sticky": [ { "value": false } ], "default_langcode": [ { "value": true } ], "revision_translation_affected": [ { "value": true } ], "path": [ { "alias": "\/daily\/2025\/05\/01\/hack", "langcode": "en" } ], "body": [ { "value": "\n
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
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
Most of the time, changes can be made within custom code that won't be overwritten and accidentally lost.<\/p>\n\n
But in cases where the source code needs to be changed, you can patch files instead<\/a>.<\/p>\n\n 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 If you can, commit the changes upstream.<\/p>\n\n Then you won't need to patch files and others will benefit from the contribution.<\/p>\n\n ",
"format": "full_html",
"processed": "\n 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 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 Most of the time, changes can be made within custom code that won't be overwritten and accidentally lost.<\/p>\n\n But in cases where the source code needs to be changed, you can patch files instead<\/a>.<\/p>\n\n 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 If you can, commit the changes upstream.<\/p>\n\n Then you won't need to patch files and others will benefit from the contribution.<\/p>\n\n ",
"summary": null
}
]
}