[
http://jira.magnolia.info/browse/MAGNOLIA-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean McMains updated MAGNOLIA-2100:
-----------------------------------
Attachment: 2100.patch
The problem is due to the fact that the config data is loaded into a HashSet,
which doesn't guarantee the order in which it will regurgitate its content.
By switching to a LinkedHashSet, we guarantee that the data will come out in
the order we put it in.
> FCK Editor: Browsable Repositories' Ordering Unpredictable
> ----------------------------------------------------------
>
> Key: MAGNOLIA-2100
> URL: http://jira.magnolia.info/browse/MAGNOLIA-2100
> Project: Magnolia
> Issue Type: Bug
> Components: admininterface
> Affects Versions: 3.5.4
> Reporter: Sean McMains
> Assignee: Philipp Bracher
> Attachments: 2100.patch
>
>
> To reproduce issue:
> 1. Create FCKEditor Paragraph
> 2. Type text, select it.
> 3. Click the "Insert/Edit Link" button in FCKEditor's toolbar
> 4. The link dialog appears.
> 5. Click "Browse Server" button
> 6. The content browser appears.
> Expected Behavior:
> Given the same configuration, the content menu (browsable repositories)
> should always be in the same order and default to the same repository.
> Actual Behavior:
> On some instances, we get "Website" by default. On others, we get "Documents"
> by default.
--
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/
----------------------------------------------------------------