Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-3662

Can't Restrict Content Editors to Specific Languages

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Won't Do
    • Neutral
    • None
    • 4.4.3
    • admininterface
    • None

    Description

      One of our customers has suggested that it would be useful to be able to limit content editors' access to the languages for which they're responsible. Currently, there's no way to use the one-tree approach to i18n without granting an editor with access to a page access to all the translations for that page.

      It would seem to make sense to me that adding a DENY ACL to config /modules/extended-templating-kit/config/sites/demo-project/i18n/locales/de would keep an editor from using the German translation in the demo-project site, but it doesn't work.

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              pbaerfuss Philipp Bärfuss
              seanmctex Sean McMains
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Checklists

                  Task DoD