[MGNLSTK-948] multiselect doesn't show saved data Created: 04/May/12  Updated: 07/May/12  Resolved: 07/May/12

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: controls
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Robert Assignee: Federico Grilli
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Firefox 12


Attachments: PNG File Auswahl_004.png     PNG File Auswahl_005.png     PNG File Auswahl_006.png    
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

when you use "multiselect" control in a dialog, as shown in the screenshots (screen 005) you can save data - no problem here (screen 004). but if you wana edit the data, none is shown in the dialog (screen 006). it might be a wrong dialog setup, but i think it could as well be a bug.



 Comments   
Comment by Federico Grilli [ 04/May/12 ]

Hi Robert, thanks for reporting this. Which version of Magnolia are you on? Can you reproduce the bug on http://demoauthor.magnolia-cms.com? I tried but was not able to recreate the issue, i.e. at /demo-project/multimedia/video-player.html where you can assign multiple categories using a multiselect control. However this rings a bell, as something similar occurred to me some weeks ago. I had a dialog with a multiselect control and a custom control which imported jQuery in the dialog itself without using noConflict mode. This would basically let jQuery take over the $ variable as an alias for jQuery and conflict with Magnolia's own definition of the $. Eventually, this messed up a js object called MgnlDynamicTable (which is used by the multiSelect control) where the function call $(..) to retrieve the saved values returned a javascript error, hence no value was displayed.

Comment by Robert [ 07/May/12 ]

Hello Frederico,
thank you very much for the respond. I am using the Version 4.5.24.5.2 for this project. I haven't had implemented any jQuery at the time the bug occurred (except the scripts included with the magnolia standart [@cms.init/] and [@cms.area name="htmlHeader" content=content/]).
I have now solved the problem, using a individual component and a content-area.

Comment by Federico Grilli [ 07/May/12 ]

okay, glad that you found a solution

Generated at Mon Feb 12 07:31:56 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.