View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 5540 | Composr | core | public | 2024-01-08 20:56 | 2024-03-30 03:47 |
| Reporter | PDStig | Assigned To | PDStig | ||
| Priority | normal | Severity | feature | ||
| Status | resolved | Resolution | fixed | ||
| Fixed in Version | 10.0.45 | ||||
| Summary | 5540: Add minimum required Composr version property to every addon / block / module / theme | ||||
| Description | As we prepare v11 alpha for its first bleeding edge release, we need to make sure people do not accidentally install v10 components into v11 and vice versa. Add a couple of new properties to every addon / block / module / theme's info function: min_cms_version - float max_cms_version - float min_cms_version is required. It defines the minimum version of Composr required to install the addon / block / module / theme. In v11, this is set to 11.0. Any / all components that either do not have this property set, or it is set < 11.0, will trigger an error when someone tries to install or upgrade it. max_cms_version - optional, but recommended when there is a later version of Composr out that the component would not work. Again, if Composr's version is > this version, trying to install or upgrade it will result in an error. If possible, when exporting a component, it should set min_cms_version to the version of the software when exported and the developer did not define this property. | ||||
| Additional Information | min_cms_version support needs implemented in v10 as well. While we do not need to define this property on any components (this would cause unnecessary upgrading of every addon, which we don't want), v10 needs to at least error if someone tries to install a v11 component on v10. For backwards compatibility, v10 should allow installing any component that has min_cms_version undefined, but v11 should error if you try to install something with this property undefined (min_cms_version is a required property for all components starting in v11). Document this all as well. And add unit tests for these properties. | ||||
| Tags | Risk: Changes core website behaviour , Roadmap: v11 | ||||
| Attach Tags | |||||
| Time estimation (hours) | |||||
| Sponsorship open | |||||
|
|
Also had to add required addon property. Add a unit test to check that this is defined and matches the file's @package. |
|
|
Implemented in v11. Need to do the v10 part still. |
|
|
Implemented in v10 and v11 |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-01-08 20:56 | PDStig | New Issue | |
| 2024-01-08 20:56 | PDStig | Status | Not Assigned => Assigned |
| 2024-01-08 20:56 | PDStig | Assigned To | => user4172 |
| 2024-01-08 20:57 | PDStig | Tag Attached: Roadmap: v11 | |
| 2024-01-08 20:57 | PDStig | Tag Attached: Risk: Changes core website behaviour | |
| 2024-01-08 20:59 | PDStig | Description Updated | |
| 2024-01-08 21:00 | PDStig | Additional Information Updated | |
| 2024-01-08 21:01 | PDStig | Additional Information Updated | |
| 2024-01-08 21:03 | PDStig | Description Updated | |
| 2024-01-09 19:47 | PDStig | Note Added: 0008172 | |
| 2024-01-11 23:17 | PDStig | Note Added: 0008177 | |
| 2024-01-13 21:57 | PDStig | Status | Assigned => Resolved |
| 2024-01-13 21:57 | PDStig | Resolution | open => fixed |
| 2024-01-13 21:57 | PDStig | Note Added: 0008183 | |
| 2024-03-30 03:35 | PDStig | Project | Composr alpha bug reports => Composr |
| 2024-03-30 03:47 | PDStig | Category | General / Uncategorised => core |
