[MAGNOLIA-1899] activation: if the page (uuid) exist in different hierarchy content is activated to the old place Created: 28/Nov/07 Updated: 23/Jan/13 Resolved: 14/Jul/08 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | activation |
| Affects Version/s: | 3.0.6, 3.5 RC1 |
| Fix Version/s: | 3.6 |
| Type: | Bug | Priority: | Major |
| Reporter: | Philipp Bärfuss | Assignee: | Jan Haderka |
| Resolution: | Fixed | 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
|
||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||
| Description |
|
If you activate page /a/A (uuid=1) to a public instance where a page /b/B exists (uuid=1) the page is imported to /b/A You can run into this situation if you move/rename a page while the public instance is not reachable. As the page still exists in the same place in the public instance following activations will publish to the old place. Workaround:
|
| Comments |
| Comment by Magnolia International [ 11/Jul/08 ] |
|
Is this still the case for 3.6 ? |
| Comment by Jan Haderka [ 11/Jul/08 ] |
|
Still the same. The reason is possible uuid links so we can't simply activate page with different UUID on public. What we could do, is to check for the path and if parent path is different in public then in author, fail the activation with message describing the reason (difference in the paths) ... the other and possibly cooler option would be to move page to new path on the public as part of the activation. This way we would not need to deactivate pages immediately when moved. |