Page move - cleaner way of handling metadata and container fields
-----------------------------------------------------------------
Key: JAHIA-2919
URL: http://www.jahia.org/jira/browse/JAHIA-2919
Project: Jahia Content Management Server
Issue Type: Improvement
Reporter: Benjamin Papez
Fix For: 5.1
As often editors are setting ACL, TBP, Workflow_mode on a container-level
rather than on the page-level (as for the menu mostly the container has just
one page-field), we need to make a cleaner and more transparent handling for
page move. Right now it is implemented like this, that when ACL or TBP is not
set at the page (just inherited), but it is set on the container, then these
IDs are applied also to the new target container, if it has no own settings
already.
Perhaps this should be more transparent and visually inform the user, what will
be copied besides the page-field and perhaps require user confirmation, if he
perhaps wants to overwrite some data. For instance workflow_mode is not yet
copied from source container to target container, so this would still need to
be implemented, as well as perhaps the copying of some parent container
metadata fields. What if there are other fields in the container defined
besides the page field - are they also moved if they are defined in the target
container, too? What if they have already been edited in the target container?
In Jahia 4 the user could also control, whether the source container should be
deleted after the move - this now is also not transparent anymore.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://www.jahia.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
jira_list mailing list
[email protected]
http://lists.jahia.org/cgi-bin/mailman/listinfo/jira_list
