[MAGNOLIA-2100] FCK Editor: Browsable Repositories' Ordering Unpredictable Created: 02/Apr/08  Updated: 23/Jan/13  Resolved: 03/Apr/08

Status: Closed
Project: Magnolia
Component/s: admininterface
Affects Version/s: 3.5.4
Fix Version/s: 3.5.5

Type: Bug Priority: Major
Reporter: Sean McMains Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File 2100.patch    
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

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.



 Comments   
Comment by Sean McMains [ 02/Apr/08 ]

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.

Comment by Magnolia International [ 03/Apr/08 ]

thanks for the patch (although it seems "funny" since the import is missing )

Comment by Sean McMains [ 03/Apr/08 ]

Right you are! Sorry about that – I noticed it after I'd submitted the patch, and hadn't had a chance to fix it.

Thanks for including the fix so quickly!

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