[
http://jira.magnolia.info/browse/MAGNOLIA-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Bracher updated MAGNOLIA-2173:
--------------------------------------
Summary: Moving / rename a page on author should not deactivate it
on public instances (was: Moving a page on author should not deactivate it on
public instances)
Fix Version/s: 3.6
> Moving / rename a page on author should not deactivate it on public instances
> ------------------------------------------------------------------------------
>
> Key: MAGNOLIA-2173
> URL: http://jira.magnolia.info/browse/MAGNOLIA-2173
> Project: Magnolia
> Issue Type: Improvement
> Components: admininterface, core
> Affects Versions: 3.5.8
> Reporter: Gregory Joseph
> Assignee: Philipp Bracher
> Fix For: 3.6
>
>
> This is really annoying, especially when "refactoring" an existing website.
> The problem with the current activation mechanism is that activating the
> moved page would activate it in its previous location, because activation is
> uuid-based and does not check paths.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
