[MAGNOLIA-2731] When activating versioned content, current ordering info is used instead of the one from time of versioning Created: 15/May/09 Updated: 10/Jan/14 Resolved: 04/Dec/13 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | activation, admininterface |
| Affects Version/s: | 4.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Jan Haderka | Assignee: | Unassigned |
| Resolution: | Outdated | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||
| Description |
|
When activating versioned content (e.g. using workflow), the content order information is not versioned, hence the current ordering information is used instead. As far as I can tell this have been in the code since ever (and there is even notice to that effect in ActivationCommand), but no issue actually exists. |