View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003207 | Composr | core_upgrader | public | 2017-04-08 23:43 | 2019-07-10 20:53 |
| Reporter | Chris Graham | Assigned To | Chris Graham | ||
| Severity | Feature-request | ||||
| Status | resolved | Resolution | fixed | ||
| Product Version | |||||
| Fixed in Version | |||||
| Summary | 0003207: Easy custom code isolation | ||||
| Description | We have safe mode but it would make professional upgrading a little more methodical if the upgrader could move all custom code (including themes and theme files) into a subtree under an '_old_code' directory. Or, move it back from that. | ||||
| Additional Information | Update the sup_professional_upgrading tutorial to state using the upgrade for the quarantine. | ||||
| Tags | Roadmap: v11 | ||||
| Time estimation (hours) | 1.5 | ||||
| Sponsorship open | |||||
|
|
Upgrade tut_upgrade "Auxillary features" section if implemented. |
|
|
I've done this, but a bit differently. The integrity checker now always 'quarantines' rather than deletes - which means moving stuff under _old/. I think that's better: no need to have multiple options and a complex UI to manage them all. It doesn't touch themes. But you can easily use keep_theme=default in the URL to force the default theme. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-04-08 23:43 | Chris Graham | New Issue | |
| 2017-04-13 21:50 | Chris Graham | Note Added: 0004991 | |
| 2019-06-27 18:52 | Chris Graham | Tag Attached: Roadmap: v12 | |
| 2019-06-27 18:53 | Chris Graham | Tag Detached: Roadmap: v12 | |
| 2019-06-27 18:53 | Chris Graham | Tag Attached: Roadmap: v11 | |
| 2019-07-10 20:53 | Chris Graham | Assigned To | => Chris Graham |
| 2019-07-10 20:53 | Chris Graham | Status | non-assigned => resolved |
| 2019-07-10 20:53 | Chris Graham | Resolution | open => fixed |
| 2019-07-10 20:53 | Chris Graham | Note Added: 0006032 |
