contextinst
commented
7 years ago Good to get this explicit. Yes, the same mantra applies in the WP world. My approach has been:
- never hack core
- rarely hack 3rd party plugins and track your hacks for the sake of upgrades to those plugins; put custom functionality into your own plugins or your theme's functions.php file
- never hack other parties themes; rather use child themes to override whatever you want to modify in the parent theme.
How does this sound as a starting policy?
I haven't been as careful as might be good with doing backups prior to upgrades. As we get automated backups running, we should think about whether and when to do manual backup in association with upgrades.
I usually upgrade new core versions of WP as soon as they are out. I did so yesterday with WP 4.8 for BFCom.
wunluv
As we continue to hack away at BFCom, its good practice to have a clear update path to new versions of WP core. Coming from a Drupal background, the mantra there was never hack core. Do we have a similar approach with WP, whereby required functionality is realised through plugin and theme layers?
A new WP core was released today: "Today there is a new release of the core WordPress open source software, version 4.8 "Evans", named in honor of the great jazz pianist Bill Evans. https://wordpress.org/news/2017/06/evans/"