View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 5628 | Composr | core_form_interfaces | public | 2024-02-27 20:06 | 2024-10-17 18:04 |
| Reporter | PDStig | Assigned To | PDStig | ||
| Priority | normal | Severity | minor | ||
| Status | resolved | Resolution | fixed | ||
| Summary | 5628: Change forms with many tick boxes to multiselects to reduce POST size | ||||
| Description | In v11, there are some forms that use form_input_tick, but could have many ticks. This could cause issues on servers limiting the number of POST parameters that can be submitted. Ticks add 3-4 POST parameters per tick. I had this issue on a server which hard-cut parameters off after 500. Update the following screens to use multiselects instead of ticks to reduce POST parameter counts: * admin_modularisation * cns_warnings hooks (needs done for the karma non-bundled addon as well) - Actually for "content deletion" (not posts) we could use all_and_not to make it easier to mass-delete spam content. We don't want to do this for points and karma though because we want staff to more carefully review those items. * Ideally the profile data tab, but we do need the descriptions * Anything else you can find | ||||
| Additional Information | You may wish to add an "estimated POST parameter count" calculation within catalogues and to give an attach_message warning if a catalogue has so many fields the POST count could exceed a certain value (let's say 250). Or, just document this potential problem and include the estimated number of POST parameters for each field type. Additional optimisation: Add a hidden field in cns_warnings hook for deleting content containing all of the content that were offered for deletion. That way, it'll be easier to use all_and_not. | ||||
| Tags | Roadmap: Over the horizon, Roadmap: v11 partial implementation | ||||
| Attach Tags | |||||
| Time estimation (hours) | |||||
| Sponsorship open | |||||
|
|
We already have a workaround for this. See modsecurity_workaround. |
|
|
Ack, I already did this change for modularisation and cns_warnings. Part of me wishes to keep the change for another reason... multiselect takes up less space on the screen. This is especially important for cns_warnings as it loads content / points ledger records from the last 7 days. Even though there is a max, that's still a lot of tick boxes especially on mobile. And it makes the screen very long. But then again multiselect is also not as mobile friendly. Hmm... I may need to think this one over. |
|
|
I would say if there is a good native solution that isn't hacky, that doesn't require our hack (modsecurity_workaround), that's better. Less hacks is better. If multi-select doesn't work well on mobile that's interesting, but I think fundamentally there's no reason that shouldn't work well - so maybe mobile browsers need to be better. Or maybe down the line we need to have some kind of abstraction over multiselects. I think multiselects are good. |
|
|
I'll check into it. I still need to replace my phone. I'll hold this issue. Once I have my new phone in, I'll see how easy multiselects are. If they're acceptable on mobile, I'll resolve the issue. I would test it in my desktop browser but I want to understand the UX ease of use as well... e.g. the physical interaction on the phone screen of selecting stuff. |
|
|
I just kind of think on some level the wider development community shouldn't jump through hoops if Apple/Google etc haven't made a proper web UI for multi-selects. There's no fundamental reason why that should be hard. If everyone just doesn't use a part of the web standards base because the big companies can't be bothered to support it properly, it enables that behavior. That's me putting principles about practical UX though. |
|
|
I think we've done enough on this issue for 11.0 for now. Modularisation and cns_warnings has multiselects. Those were the big areas. |
|
|
Actually, we also need this on addon install screen and on file integrity scan. (Problem with file integrity scan is it's part of installer which uses a minimal interface). |
|
|
Added ModSecurity workaround for modularisation page and addon install page. Issue rejected for file integrity scan. It cannot be implemented reliably. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-02-27 20:06 | PDStig | New Issue | |
| 2024-02-27 20:06 | PDStig | Status | Not Assigned => Assigned |
| 2024-02-27 20:06 | PDStig | Assigned To | => user4172 |
| 2024-02-27 20:06 | PDStig | Tag Attached: Roadmap: v11 | |
| 2024-02-27 20:08 | PDStig | Additional Information Updated | |
| 2024-02-27 20:09 | PDStig | Additional Information Updated | |
| 2024-02-27 20:09 | PDStig | Description Updated | |
| 2024-02-27 20:10 | PDStig | Description Updated | |
| 2024-02-27 20:11 | PDStig | Description Updated | |
| 2024-02-27 20:16 | PDStig | Additional Information Updated | |
| 2024-02-27 20:18 | PDStig | Description Updated | |
| 2024-03-24 18:34 | Chris Graham | Note Added: 0008418 | |
| 2024-03-25 16:55 | PDStig | Note Added: 0008436 | |
| 2024-03-25 16:55 | PDStig | Note Edited: 0008436 | |
| 2024-03-27 13:38 | Chris Graham | Note Added: 0008456 | |
| 2024-03-27 13:56 | PDStig | Note Added: 0008463 | |
| 2024-03-28 14:05 | Chris Graham | Note Added: 0008471 | |
| 2024-07-31 20:57 | PDStig | Tag Detached: Roadmap: v11 | |
| 2024-07-31 20:57 | PDStig | Tag Attached: Roadmap: v11 partial implementation | |
| 2024-07-31 20:57 | PDStig | Tag Attached: Roadmap: Over the horizon | |
| 2024-07-31 20:57 | PDStig | Note Added: 0009029 | |
| 2024-07-31 20:58 | PDStig | Note Edited: 0009029 | |
| 2024-10-17 17:08 | PDStig | Note Added: 0009482 | |
| 2024-10-17 17:10 | PDStig | Note Edited: 0009482 | |
| 2024-10-17 18:04 | PDStig | Status | Assigned => Resolved |
| 2024-10-17 18:04 | PDStig | Resolution | open => fixed |
| 2024-10-17 18:04 | PDStig | Note Added: 0009483 |
