[MAGNOLIA-936] adminCentral tree should allow to copy single pages Created: 14/Jun/06  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia
Component/s: admininterface
Affects Version/s: 3.0 RC1
Fix Version/s: None

Type: New Feature Priority: Major
Reporter: Boris Kraft Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Magnolia adminCentral treeview combines the hierarchy information with the content of a page, which is somewhat natural for web pages, but occasionally strange. Since we do not want to change that, it should be made clear in the menu points if an action acts on a page (the content) or a tree (the hierarchy).

This becomes clearer when you look at the way it is now: "edit page" actually opens a page for editing, while "copy page" and "move page" act on the whole tree.

Finally, why I noticed this: thre is no way to copy a single page unless it is a leaf page. This is very annoying if you do have to copy a single page, as there is also no way to multi-select the child pages in order toi get rid of them once you were forced to copy them.

Suggestions:

  • rename the menu poimnt to make clear what acts on the tree and what on the single page
  • act a menu action that allows to copy a single page
  • nice-to-have: add multi-select


 Comments   
Comment by Magnolia International [ 20/Feb/07 ]

If you would have the possibility to copy a single page without its child pages, what would you expect to be happening to those child pages ?

Comment by Giancarlo Berner [ 20/Feb/07 ]

You are right, if you talk about MOVING a page. But sometimes you just want to DUPLICATE a page.

So copying just one page only makes sense. There are many situations where I copy just one page and indeed it would be nice if I would not have to copy the whole hierarchy. Not to mention that in some large hierarchies copying the page (with hierarchy) and then deleting the children takes a long time.

Just my 2cts.

Comment by Magnolia International [ 20/Feb/07 ]

sounds fair, I just wanted to make the use case clear

Comment by Boris Kraft [ 21/Feb/07 ]

GC said what I would have. Thats exactly the point - or think the other way - you need to restructure your content in such a way that the parent pages needs to be moved out of the way, but not the children. You copy the parent, and then are free to delete/change the content on the original page, or redirect to a child or whatever. If you can't copy the single parent page, this is awkward (since there is also no multi-select in adminCentral - hint hint )

Comment by zam6ak [ 02/Apr/07 ]

Why not have "Copy Page inc. sub pages" and "Copy page" in the context menu.
This would follow Activation example.

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 03:22:03 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.