View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0003851||Composr||catalogues||public||2019-07-20 02:53||2019-07-31 19:30|
|Reporter||Chris Graham||Assigned To||Chris Graham|
|Fixed in Version|
|Summary||0003851: Catalogue category sort order|
|Description||Currently there's a non-optional sort order field. It should be nullable.|
Then a new 'catalogues_subcategories_sort_order' catalogue field is needed to define the default sort order (parallels the "*_sort_order" config options). This replaces what is currently a hidden option (cc_sort_date__*).
Then a lot of code needs adjusting to make it consistent.
|Time estimation (hours)||2|
Actually it may be better to just remove the current sort order field, and have this catalogue option instead.
Right now there are no other category/entry-like content types that have manual ordering, just some resource types where it makes special sense, and Comcode pages.
There are issues for adding a lot more order fields, but I feel it's kind of bloaty, and I would rather have the system consistent until we feel the need to ramp the complexity up.
I've implemented what I said in my comment.
I'm reorganising issues so the concept of order-overrides is handled from one shared issue.
|2019-07-20 02:53||Chris Graham||New Issue|
|2019-07-20 02:58||Chris Graham||Description Updated||View Revisions|
|2019-07-20 03:02||Chris Graham||Note Added: 0006040|
|2019-07-20 03:02||Chris Graham||Tag Attached: Roadmap: v11|
|2019-07-31 01:03||Chris Graham||Note Edited: 0006040||View Revisions|
|2019-07-31 19:30||Chris Graham||Assigned To||=> Chris Graham|
|2019-07-31 19:30||Chris Graham||Status||non-assigned => resolved|
|2019-07-31 19:30||Chris Graham||Resolution||open => fixed|
|2019-07-31 19:30||Chris Graham||Note Added: 0006063|