Bug #5499
closed
Copy doesn't run update ordering
Added by krileon about 10 years ago.
Updated almost 10 years ago.
Start date:
07 September 2015
Description
When doing a copy the updateOrdering isn't being ran, which results in messed up orders for the copies. It should be ran in the TableBrowser when performing the copy action.
- Target version changed from CB 2.0.11 to CB 2.0.12
- Status changed from Assigned to Rejected
- Target version deleted (
CB 2.0.12)
- % Done changed from 0 to 100
It can't without parsing for the ordering node and checking ordering groups. Copied entries are also unpublished and a copy should be direct copy of its parent, including its ordering, so the behavior seams valid and correct. Don't think this needs to be changed and if it is then just null the ordering and let ->store handle it.
Also available in: Atom
PDF
Updated by 
Updated by