How to stop updates from overwriting custom templates
Replacing central configuration folders during an update wipes out your custom additions, such as third-party ADMX files or WordPress functions.php edits. This forces you to manually re-apply your changes every time the software updates.
What people tried
Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.
- 1Keeping vendor and third-party templates staged separately and re-copying them after the update
- 2Clearing out stale ADML files in the language subfolder to avoid mismatched pair errors
- 3Using a code injection plugin
- 4Creating a child theme
- 5Dropping a standalone PHP file into a must-use plugins directory
In their words
Unedited, grouped by where they were said, most upvoted first within each place, each linked to the thread it came from.
“But when Wordpress core updates, does functions.php also get overwritten sometimes? How often is this specific file updated? I wouldn't want to keep editing the file with my edits every time WP has an update.”source ↗
“one thing that bites people: dumping the whole PolicyDefinitions folder into the central store wipes the Edge/Chrome/Office/third-party ADMX you added.”source ↗
Where this came up
People with this problem also raised
- 7How to revert unwanted software UI and design updates
- 16Why won't my store data update through the API?
- 2How to change the mobile menu icon in WordPress block themes
- 11Why built-in software AI features don't fit real work
- 9How to handle undocumented legacy database changes
- 8How do you manage DCIM and IPAM data in a GitOps workflow?