[MGNLDATA-66] "sort by name" in type is ignored ? Created: 05/Aug/09  Updated: 15/Sep/15  Resolved: 23/Nov/09

Status: Closed
Project: Magnolia Data Module (closed)
Component/s: None
Affects Version/s: 1.3.2
Fix Version/s: 1.4.1

Type: Bug Priority: Major
Reporter: Magnolia International Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File TypeDefinition.java.patch    
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Example in the demo instance, the "category" type has its "sort by name" checkbox checked, but the tree does not display the nodes in alphabetical order. Am i missing something ?



 Comments   
Comment by Thomas Duffey [ 05/Aug/09 ]

I tracked this one down recently. The bean uses a different name for that property. In Admin Central go to:

Data -> Config (Dialogs) -> dataType -> tabCommon

and rename the "sortByName" content node to "sortedByName" and do the same to its "sortByName" node. Now edit that data type, re-select the "sort by name" checkbox and all is well.

I'm not sure if the patch for this should be on the Java side or the default Data Module config.

Comment by Jan Haderka [ 06/Aug/09 ]

Wow, nice detective work. Thanks.
I'd say we should keep node name sortByName and rename the property in TypeDefinition. For backward compatibility we should also probably keep the old name for while and delegate it to the new name.
And to be super nice, provide an update task that will search for sortedByName property and rename it to sortByName when found.

Comment by Bert Leunis [ 20/Nov/09 ]

Here is the patch Jan suggests.

Comment by Jan Haderka [ 23/Nov/09 ]

Applied as of r29952. Thanks for the patch.

Comment by Michael Mühlebach [ 15/Sep/15 ]

This ticket was closed because former resolved tickets are deemed to be closed now. If this assumption is untrue in this particular case please feel free to reopen the ticket again.

Generated at Mon Feb 12 05:11:01 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.