[MGNLMIGRATION-231] Content migration tasks' support of update single page migrate all children instead. Created: 14/Mar/13 Updated: 29/Mar/13 Resolved: 22/Mar/13 |
|
| Status: | Closed |
| Project: | Migration 4.4 to 4.5 (closed) |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.2.2 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Robert Šiška | Assignee: | Robert Šiška |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Description |
|
updateSinglePage() methods are run recursively without any check, so adding '#' to migrate only one page doesn't have an effect. This is relevant to multiple content migrating tasks. |