-
Bug
-
Resolution: Fixed
-
Major
-
3.0.6, 3.5 RC1
-
None
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:
- delete the old page in the public instance
- to find the old page (with the same uuid) execute a jcr query (Tools / JRC Queries): select * from nt:base where jcr:uuid='the-uuid'
- is depended upon by
-
MAGNOLIA-2131 Moving nodes can create inconsistent website-trees on author and public system
- Closed
-
MAGNOLIA-2173 Moving / rename a page on author should not deactivate it on public instances
- Closed
- supersedes
-
MGNLXAA-7 activation: if the page (uuid) exist in different hierarchy content is activated to the old place
- Closed