Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-27115

Admin siteaccess generation

    XMLWordPrintable

Details

    • Icon: Story Story
    • Resolution: Done
    • Icon: High High
    • None
    • None
    • Platform > Hybrid UI
    • None

    Description

      The Hybrid UI symfony prototype relies on the admin being accessed via a siteaccess (http://example.com/admin).

      The admin siteaccess(es) should be automatically defined, while allowing configuration and customization.
      Special settings, such as languages, must be searched for use-cases and covered.

      For now, one admin siteaccess is generated per siteaccess group, assuming that one group matches one repository (we need a separate admin siteaccess per repository because of settings). If there is only one group, the admin siteaccess is named admin. If there are several, they are named admin_<siteaccess_name>.

      Open questions:

      • when there is one siteaccess, how is the admin siteaccess named ?
      • where there are several siteaccesses, do we generate one or several admin siteaccess ? Do we add options for that ? How is each siteaccess named ?
      • how is the admin siteaccess matched when host mapping is used ?
      • how is the admin siteaccess matched when port based mapping is used ?

      Attachments

        Activity

          People

            Unassigned Unassigned
            bertrand.dunogier@ibexa.co Bertrand Dunogier
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: