Ticket #1750 (closed defect: fixed)

Opened 13 years ago

Last modified 13 years ago

Wrong ordering in navigation portlets relying on treecaches

Reported by: gracinet Owned by: fguillaume
Priority: P2 Milestone: CPS 3.4.3
Component: CPSCore Version: TRUNK
Severity: minor Keywords: Tree


This is supposed to bring up all sections up to depth n, in ZODB ordering:

portal_trees.sections.getList(start_depth=1, stop_depth=n)

But the result seems to be ordered by id (or rpath). On the other hand the following call works as expected.


This looks like a really funny side-effect type bug.

Change History

comment:1 Changed 13 years ago by gracinet

  • Status changed from new to closed
  • Resolution set to fixed

Done in [49846]. Ordering was probably broken for visible subfolders of hidden ones.

Note: See TracTickets for help on using tickets.