View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002222 | Composr | core_abstract_interfaces | public | 2016-02-24 22:33 | 2019-11-12 19:34 |
| Reporter | Chris Graham | Assigned To | Chris Graham | ||
| Severity | Feature-request | ||||
| Status | resolved | Resolution | fixed | ||
| Product Version | |||||
| Fixed in Version | |||||
| Summary | 0002222: AFM pre-check | ||||
| Description | A pre-check call for the AFM that can be done before trying to remove addons (or whatever). This allows us to check we have the file-system permissions we need to finish an operation before starting changing other stuff first like DB structure. | ||||
| Tags | Roadmap: v11, Type: Usability (major) | ||||
| Time estimation (hours) | 1 | ||||
| Sponsorship open | |||||
|
|
To catch most cases we can do it just by implementing some simple check in force_have_afm_details. We'd pass in the path to somewhere that needs writing to. This works as the vast majority of AFM processes are either re-entrant, or work only under one folder. For the _multi_action/_addon_install/_addon_uninstall functions, we must pre-check with a list of files being removed. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-12-08 12:43 | Chris Graham | Tag Attached: Type: Usability | |
| 2016-12-08 12:50 | Chris Graham | Tag Renamed | Type: Usability => Type: Usability (major) |
| 2017-05-01 16:49 | Chris Graham | Category | core => core_abstract_interfaces |
| 2018-08-09 01:00 | Chris Graham | Note Added: 0005790 | |
| 2019-06-27 19:04 | Chris Graham | Tag Attached: Roadmap: v11 | |
| 2019-11-12 19:34 | Chris Graham | Assigned To | => Chris Graham |
| 2019-11-12 19:34 | Chris Graham | Status | non-assigned => resolved |
| 2019-11-12 19:34 | Chris Graham | Resolution | open => fixed |
