What is wrong with updating the setting?
[Such a settings update][new setting] in my experience has **not** been backwards-compatible (prod page will break upon deploy) **nor** future-compatible (not using a custom template in future, prod page will break upon deploy).
### Fail Case
0. Deploy project
- with guide template setting path "B"
- to a server that guide template setting path "A".
1. Open existing page that uses "Guide: Getting Started" template.
2. Notice page _crash_…
(**unless** someone updated page after deploy via `/admin` UI to use guide template setting path "A" before visiting the page)
Overview
Overwrite template, instead of creating a new one, so that settings need not be updated.*
What is wrong with updating the setting?
[Such a settings update][new setting] in my experience has **not** been backwards-compatible (prod page will break upon deploy) **nor** future-compatible (not using a custom template in future, prod page will break upon deploy). ### Fail Case 0. Deploy project - with guide template setting path "B" - to a server that guide template setting path "A". 1. Open existing page that uses "Guide: Getting Started" template. 2. Notice page _crash_… (**unless** someone updated page after deploy via `/admin` UI to use guide template setting path "A" before visiting the page)
Related
Changes
Testing
Local
/apcd-cms/src/taccsite_cms/settings_custom.py
with pre–WP-519 settings.Remote
/admin
change template to original template path.UI