MODx Bug/Feature Tracker and Feature Requests
Welcome to the MODx CMS Tracker. Please choose the appropriate project from the drop down menu and provide as much information as possible regarding your server environment and browser. Thanks!
FS#714 — Disabling demo content on upgrading
Attached to Project —
MODx
Opened by Olivier (mr_go) - Friday, 08 December 2006, 07:58AM
Last edited by Jason Coward (opengeek) - Saturday, 12 May 2007, 12:50PM
Opened by Olivier (mr_go) - Friday, 08 December 2006, 07:58AM
Last edited by Jason Coward (opengeek) - Saturday, 12 May 2007, 12:50PM
| Task Type | ToDo |
|---|---|
| Category | Install and Server Issues |
| Status | Implementing |
| Assigned To |
Jason Coward (opengeek) |
| Operating System | All |
| Severity | High |
|---|---|
| Priority | High |
| Reported Version | 0.9.2.2 |
| Due in Version | 0.9.7 |
| Due Date | Undecided |
| Percent Complete |
|
Details
Users could erase their database while upgrading version of modX by checking the demo content box. I think it could be interresting to disallow this option on upgrade.PS : sorry for my bad english... ;)
This task depends upon
This task blocks these from closing
Some people might genuinely intend to upgrade to the demo content, particularly if they had the older demo content. Disallowing the option is therefore a bad idea. There is already a mild warning, and users would have to actively check the demo content box.
What would be better would be an "are you sure?" prompt if this is selected.
Another thing that will help is to have the installer available in other languages to help avoid accidents from people not understanding the options.
- Field changed: Status (Unconfirmed → Implementing)
- Task assigned to Jason Coward (opengeek)
This will be addressed with the new installation services in 0.9.7, which feature a complete separation of the core install/upgrade process from the add-on install/upgrade process. The add-on installation/upgrade process will not occur until after the core install/upgrade is completed and confirmed. I think this should make it much clearer for the users so they don't accidentally overwrite their site. Furthermore, the package install process can make sure that the content being installed does not overwrite existing records, instead providing warnings and providing the user with options to continue and overwrite or not.