Plan a sandbox for risky changes
Publishing a test layout, mapping or menu never touches the live site.
Life cycle: Plan, example 29 of 35. Worked out on the Fit & Healthy site of Exponential 6.0.15+.
Contents
On a copy of the installation
- A copy needs the code, a copy of
settings/and of the database, its ownvar/directory and a web server on another address. - These pages were written that way: every publish was on such a copy.
Which to choose
Drafts are enough for looking; a copy is needed for anything that must be published to be seen.
Check
- The copy's database is not the live one (compare a test user that exists only in the copy).
Related pages
- Measured steps and times
- Plan examples, every page
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.