Issue with visibility of Pages and Flex Objects for Group Editor in Multisite Setup

Support
1

I am using a Multisite setup with and everything works fine, except for one issue regarding user permissions for the Group Editor role. As an Admin, I can easily access the “Pages” menu on both websites and view all pages, including those in the new site’s env (["user/{$folder}/pages"]) directory.

The problem occurs when logging in as a Group Editor:

  1. The “Pages” menu item is not visible. The editor can only see the pages from the main website, not the pages in the new website’s env directory.
  2. A similar issue occurs with Flex Objects: The “Flex Objects” menu is visible, but the editor sees the message: “You do not have sufficient permissions for this action.”

Question:
What settings do I need to adjust for the second site in order to make the pages and Flex Objects visible to the Group Editor? Are there any missing permissions or configurations preventing the content from showing up properly?

My groups.yaml:

Administrator:
  access:
    site:
      login: true
    admin:
      login: true
      super: true
      cache: true
      configuration: true
      pages: true
      maintenance: true
      statistics: true
      plugins: true
      themes: true
      tools: true
      users: true
      tecart-buttons: true
      tecart-icon-navi: true
      tecart-blog-teaser: true
      tecart-blog-teaser-filter: true
      tecart-blog-author: true
      tecart-references: true
      tecart-references-branches: true
      tecart-references-filter: true
      tecart-news-teaser: true
      flex-objects: true
  readableName: Administrator
  enabled: true
Developer:
  access:
    site:
      login: true
    admin:
      login: true
      super: true
      cache: true
      configuration: true
      pages: true
      maintenance: true
      statistics: true
      plugins: true
      themes: true
      tools: true
      users: true
      tecart-buttons: true
      tecart-icon-navi: true
      tecart-blog-teaser: true
      tecart-blog-teaser-filter: true
      tecart-blog-author: true
      tecart-references: true
      tecart-references-branches: true
      tecart-references-filter: true
      tecart-news-teaser: true
      flex-objects: true
  readableName: Entwickler
  enabled: true
Editor:
  access:
    site:
      login: true
    admin:
      login: true
      super: false
      cache: true
      configuration: false
      pages: true
      maintenance: false
      statistics: true
      plugins: false
      themes: false
      tools: false
      users: false
      tecart-buttons: true
      tecart-icon-navi: true
      tecart-blog-teaser: true
      tecart-blog-teaser-filter: true
      tecart-blog-author: true
      tecart-references: true
      tecart-references-branches: true
      tecart-references-filter: true
      tecart-news-teaser: true
      flex-objects: true
  readableName: Redakteur
  enabled: true
2

Problem solved!

The issue was caused by how I configured the directories in user/env/subsite/config/plugins/flex-objects.yaml. I had changed the order and removed some entries, which caused the system to stop recognizing the pages. It turns out that simply commenting out unused items works, but deleting them or changing their order breaks the functionality.

By reverting to the correct order and commenting out instead of deleting, everything now works as expected.

enabled: true
built_in_css: true
extra_admin_twig_path: 'theme://admin/templates'
admin_list:
  per_page: 15
  order:
    by: updated_timestamp
    dir: desc
directories:
  1: 'blueprints://flex-objects/pages.yaml'
  2: 'blueprints://flex-objects/tecart-buttons.yaml'
  3: 'blueprints://flex-objects/tecart-icon-navi.yaml'
  4: 'blueprints://flex-objects/user-accounts.yaml'
  5: 'blueprints://flex-objects/user-groups.yaml'
#  6: 'blueprints://flex-objects/tecart-blog-teaser.yaml'
#  7: 'blueprints://flex-objects/tecart-blog-teaser-filter.yaml'
#  8: 'blueprints://flex-objects/tecart-blog-author.yaml'
  9: 'blueprints://flex-objects/tecart-news-teaser.yaml'
#  10: 'blueprints://flex-objects/tecart-references.yaml'
#  11: 'blueprints://flex-objects/tecart-references-branches.yaml'
#  12: 'blueprints://flex-objects/tecart-references-filter.yaml'
2 Likes