[MAGNOLIA-2753] In multiselect control allow storing UUID instead of the path Created: 30/May/09  Updated: 04/Nov/15  Resolved: 04/Nov/15

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

Type: Improvement Priority: Major
Reporter: Giancarlo Berner Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

MacBook Pro, Parallels/Windows XP, Mg 4.1, Tomcat 6, FF 3


Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

The multiselect control always stores the node name (the path) of a selected node. If (for whatever reason) the node name changes, the node stored with the multiselect control is going to be broken.

Please add a property allowing to select the store type (e.g. "path", "uuid").

Thanks!



 Comments   
Comment by Will Scheidegger [ 13/Aug/12 ]

This is in fact a single liner:

package info.magnolia.cms.gui.dialog;
public class DialogUUIDMultiselect extends DialogMultiSelect implements UUIDDialogControl {
}

That's it that's all! It behaves exactly like DialogMultiSelect, but because it implements the UUIDDialogControl interface (empty interface) the path values are converted to UUIDs before saving and vice versa.

-will

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:39:46 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.