Details
-
Bug
-
Resolution: Fixed
-
High
-
2.5.8
-
Fresh installation of eZ Platform Enterprise v2.5.8
Description
Steps to reproduce:
1. Define site accesses and their groups as shown below:
# Siteaccess configuration, with one siteaccess per default siteaccess: list: [site, admin, admin2, site2] groups: site_group: [site, site2] # WARNING: Do not remove or rename this group. # It's used to distinguish common siteaccesses from admin ones. # In case of multisite with multiple admin panels, remember to add any additional admin siteaccess to this group. admin_group: [admin, admin2] default_siteaccess: site match: URIElement: 1
2. Define site accesses' scopes and shown below:
system: default: #existing keys admin_group: # System languages. Note that by default, content, content types, and other data are in eng-GB locale, # so removing eng-GB from this list may lead to errors or content not being shown, unless you change # all eng-GB data to other locales first. # For admin this needs to contain all languages you want to translate content to on the given repository. #languages: [eng-GB, fre-FR] page_builder: siteaccess_list: [site] content_tree_module: contextual_tree_root_location_ids: - 2 # Home (Content structure) - 5 # Users - 43 # Media - 48 # Setup - 55 # Forms subtree_paths: content: /1/2/ media: /1/43/ site_group: # design: main admin2: languages: [eng-GB, fre-FR] page_builder: siteaccess_list: [site, site2]
3. Go to [host]/admin2/content/location/42 - notice the content tree info: This location has no sub-items
4. Go to [host]/admin/content/location/42 - notice the content tree highlighted folder
Result:
Invalid content tree render in admin2 site access
Expected result:
The result of previewing content tree as admin2 site access should be the same as a result of previewing the admin site access content tree as there should be fallback to group settings.