Replies: 3 comments
-
This hook would definitely be (more) useful if it was possible to set by entry source, although I get where Brandon is coming from. In addition to under-the-hood troubles, having per-source sortable attributes also involves updating UI elements such as the actual sorting menu. I'm guessing it all would involve a substantial amount of refactoring to make possible. Would be really, really awesome if there was a way, though. |
Beta Was this translation helpful? Give feedback.
-
This is easier said than done with the current architecture (see http://craftcms.stackexchange.com/a/8716/9 for an explanation). But we will keep this in mind as we look at ways to improve things in Craft 3. |
Beta Was this translation helpful? Give feedback.
-
Totally agreed. Sortable attributes shouldn't be forced to include fields that the section isn't using. |
Beta Was this translation helpful? Give feedback.
-
Please give us an option to set
modifyEntrySortableAttributes
per entry source. I think the hook is pretty much useless without it.I don't want the Client to be able to sort the "Blog" section by "Opening Time" for example!
Beta Was this translation helpful? Give feedback.
All reactions