-
Bug
-
Resolution: Won't Fix
-
Major
-
None
-
5.0
-
None
It's a quite special use case and I guess the bug is in place since MAGNOLIA-2173:
- add new page a and activate it
- copy the page
- rename the original a to a1
- rename the copy to former a and activate it
=> so far so good, but now repeat it once again
- activate a1
- rename a1 to a12
- rename a to a1 and activate it
=> a1 should be duplicated on Public instance now
Acceptance criteria
- is related to
-
-
- Closed
-
-
MAGNOLIA-2173 Moving / rename a page on author should not deactivate it on public instances
-
- Closed
-
