[MAGNOLIA-367] ordering of nodes with jcr orderBefore Created: 03/May/05  Updated: 23/Jan/13  Resolved: 16/May/06

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 2.1 Final
Fix Version/s: 3.0 RC1

Type: Task Priority: Major
Reporter: Philipp Bärfuss Assignee: Boris Kraft
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

In the current implementation we are using the a magnolia sequencenumber to order elements (move, copy, ...).

This is stored in the MetaData. The common getChildren() does not use it after the cleaning up of the API.

As a current workaround you can use:

getChildren(itemType, ContentHandler.SORT_BY_SEQUENCE)

In future we order the nodes with the jcr method orderBefore.

First we have to change the Tree (move, paste)



 Comments   
Comment by Fabrizio Giustina [ 04/May/05 ]

added ContentHandler.SORT_BY_SEQUENCE to ContentNodeIterator tag, sorting of paragraphs didn't work anymore.

Comment by Philipp Bracher [ 04/May/05 ]

There are other places to do that:

  • template drop down (i will do it)

We should also check the node moving in the tree view. somtimes i get a fuzzy behavier

Comment by Philipp Bracher [ 04/May/05 ]

templates are ordered again

Comment by Philipp Bracher [ 11/May/05 ]

Tabs ordering adapted

Comment by Philipp Bracher [ 16/May/05 ]

I searched through the code to find the places where we have to pass the ordering explicitely:

Everything should work now the way it worked before the change.

This does not make the task obsolete, because we will definitly change to the jcr ordering.

  • Ordering dialog controls
  • Ordering during past
  • Ordering during moving paragraph
Generated at Mon Feb 12 03:16:43 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.