This was something I just noticed that should be addressed. In the Vae backend, the ordering of elements is not case-sensitive. For example, this is how a list of entries would be ordered by the title name in the backend:
18th Century
antler Tip
Black Diamonds
Diamond Comet
Diamond Loop
Diamond Sticks
Diamond Tibetan Masks
Jaipur Jaunt
Misshape Diamond Ball
Natural Tulsi Wood Luxe
Pearls
RK Hand
Ruby Kobo Assortment
So if I leave the sorting of a collection to the 'Sort Entries by' feature in the backend, this is how the Entries are ordered.
However, if I am ordering Entries using the order="" attribute
<v:collection path="slides" order="collection/title">
or the order option in the $options array in vae()
$collections = vae('/collections',array('order' => 'title' ));
The order of the entries will be like this:
18th Century
Black Diamonds
Diamond Comet
Diamond Loop
Diamond Sticks
Diamond Tibetan Masks
Jaipur Jaunt
Misshape Diamond Ball
Natural Tulsi Wood Luxe
Pearls
RK Hand
Ruby Kobo Assortment
antler Tip
The order needs to be one way or the other I think. Anyone have thoughts on this?
hmmm, well the nerd in me thinks keeping it case sensitive gives you more options because you can then apply a case changing string function before you do the sorting, but...
Yes, I think the more user/client friendly way is to have it case insensitive. I just dont see a client wanting to order it the case sensitive way ever.
It looks like you're new here. If you want to get involved, click one of these buttons!