Administrator can't access to a site scope in the CKEditor File Browser if he isn't a site member

• Type: Bug
• Status: Closed
• Resolution: Won't Fix
• Affects Version/s: 6.0.X EE, 6.1.X EE, 6.2.X EE, Master
• Fix Version/s: 6.0.X EE, 6.1.X EE, 6.2.X EE, Master
• Component/s: UI Infrastructure, UI Infrastructure > WYSIWYG
• Labels:
  • ee-ts
• Fix Priority: 3
• Similar Issues: Show 5 results ; ;

  LPS-36455	CKEditor file browser should open in same folder as current scope
  LPS-43513	CKEditor resources browser set to wrong path by default
  LPS-39716	Site Administrator can't see Draft blogs of Site Members when the portlet is page-scoped
  LPS-46867	On an android device (4.3 and below) using the stock browser, the scope selector icon in Site Administration does not appear
  LPS-43296	Site Administrators for site A can add content to site B through an Asset Publisher on Site A that is scoped to include Site B

User with the Administrator Role can access to all Sites/Documents & Media in the Control Panel, but not in the CKEditor File Browser, so, he can't create WebContent and link documents that he is allowed to manage.

Steps to reproduce:

As test / superadmin:

1. Create an Organization, Org1.
2. Edit Org1 and create the Org1 site.
3. Create another Site, Site1.
4. Create an user3, and set Regular Role: Administrator.

As user3:

5. Go to Control Panel > Sites: User1 can access to all sites, including Org1 and Site1, also can access to Documents & Media Library of the Sites.
6. Go to Control Panel > Sites > Org1 > Content: Web Content, and add a new content.
7. Click on the Image button of the rich text editor and Browse Server.

Result: user3 (Administrator) can't access to the root folder of Org1. See user3.png.

Expected: user3 (Administrator) can access to all the root folders.

If you add user3 as member of Org1 or any Site, you are allowed to view the root folder, however, an administrator doesn't need to be member of a Organization or Site to access to any resource.

[Jose Jimenez]

It's the expected behavior because the number of root folders can be huge in many environments, including root folder of users, communities, organizations, site templates and global.

The administrator can set himself as member of the desired scope as workaround.