View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 5941 | Composr | core | public | 2024-09-15 01:51 | 2024-11-18 17:30 |
| Reporter | Adam Edington | Assigned To | PDStig | ||
| Priority | normal | Severity | minor | ||
| Status | resolved | Resolution | fixed | ||
| Product Version | 11.beta4 | ||||
| Summary | 5941: Restore Comcode block categories | ||||
| Description | In v11, the majority of Comcode blocks live under the heading Main blocks; miscellaneous. When scrolling through the options, v10 headings made it much easier to locate the block you were seeking. | ||||
| Additional Information | The blocks aren't even listed alphabetically. | ||||
| Tags | Roadmap: v11 | ||||
| Attach Tags | |||||
| Attached Files | |||||
| Time estimation (hours) | |||||
| Sponsorship open | |||||
|
|
Oof, yes this is a big problem. I'll work on it. |
|
|
Automated response: Block wizard was not correctly categorising a lot of blocks block_helper_script was trying to use an optimised way of detecting to which addons each block belongs. But this didn't work for 80% of the blocks. This hotfix fixes the following issues: - Use actual hook object method get_file_list instead of trying to parse the code and cms_eval it (but unset them after we're done to save on memory) - Wrong character length was used for sources_custom/blocks/ (should have been 22, not 21, so custom blocks were not getting categorised) - Don't exclude blocks with the name 'block' in them; no idea why we were excluding these and dumping them into main blocks misc, but it caused the forum blocks to get put there when really forum blocks should be under their own "Forum blocks" section. |
|
|
Fixed in Git commit 1a1185481c (https://gitlab.com/composr-foundation/composr/commit/1a1185481c - link will become active once code pushed to GitLab) |
|
|
A hotfix (a TAR of files to upload) has been uploaded to this issue. Only apply this hotfix if you absolutely need it and cannot wait until the next release of Composr (releases are more reliable and strictly tested). As of Composr version 11, the recommended way to apply a hotfix is by following the same steps as an upgrade (https://baseurl/upgrader.php, use the hotfix on the step “Transfer across new/updated files”). The upgrader will automatically skip files belonging to addons you do not have installed or that are newer on disk than in the hotfix. Otherwise, you can manually extract and replace these files (do not replace if your on-disk file is newer than the one in the hotfix). Always take backups of your site or at least files you are replacing before applying a hotfix. Not sure how to extract TAR files to your Windows computer? Try 7-zip (http://www.7-zip.org/). |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-09-15 01:51 | Adam Edington | New Issue | |
| 2024-09-15 01:52 | Adam Edington | Description Updated | |
| 2024-09-15 01:53 | Adam Edington | Description Updated | |
| 2024-09-15 01:54 | Adam Edington | Description Updated | |
| 2024-09-15 01:54 | Adam Edington | Additional Information Updated | |
| 2024-09-15 01:57 | PDStig | Tag Attached: Roadmap: v11 | |
| 2024-11-18 16:56 | PDStig | Note Added: 0009607 | |
| 2024-11-18 16:56 | PDStig | Severity | Feature or Request => Minor Bug |
| 2024-11-18 16:56 | PDStig | Assigned To | => user4172 |
| 2024-11-18 16:56 | PDStig | Status | Not Assigned => Assigned |
