View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 2157 | Convertr | Upgrader bindings | public | 2016-01-30 15:18 | 2022-11-20 22:08 |
| Reporter | Chris Graham | Assigned To | Guest | ||
| Priority | normal | Severity | feature | ||
| Status | new | Resolution | open | ||
| Summary | 2157: Integrate into upgrader | ||||
| Description | For any themes being upgraded, the upgrader needs to apply any data/theme_patches/<version>.json files between the version subsequent to the version upgrading from to the version it is upgrading to. E.g. imagine we are upgrading to version 11.3.2 and have themes installed as follows: bob (for 11.3.1) sue (for 11.2.6) Imagine that the versions went 11.2.6 < 11.2.7 < 11.3.0 < 11.3.1 < 11.3.2 We would apply patches as follows: bob: 11.3.2 sue 11.2.7 sue 11.3.0 sue 11.3.1 sue 11.3.2 Actually it's done per-file, not per-theme, but you get the point. Theoretically 2 files in a theme may be sourced from 2 different versions. Note how we are doing this within a theme upgrade step. Currently the upgrader has a theme upgrade step with hard-coded operations, which we frankly have not had time to maintain. So we are plugging the Convertr engine in at this point. Any existing theme upgrade code in the upgrader (e.g. trying to apply diffs using .editfrom files) should be totally removed in deference to our new system. | ||||
| Tags | No tags attached. | ||||
| Attach Tags | |||||
| Sponsorship open | |||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-11-20 22:08 | Chris Graham | Assigned To | user4145 => |
| 2022-11-20 22:08 | Chris Graham | Status | Assigned => Not Assigned |
