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

Publish on limited languages with multiple locations failing

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Medium Medium
    • Resolution: Invalid
    • Affects Version/s: 4.7.0
    • Fix Version/s: Customer request
    • Component/s: Language
    • Labels:
      None

      Description

      Steps to reproduce:

      1. Create new eZ Publish 4.7 installation, set with 3 languages. Used eng-GB, nor-NO and por-PT;
      2. Install all available service packs;
      3. Create the following structure:

      Home
      --Folder 1 (eng-GB)
      ----Article 1 (eng-GB, nor-NO)
      --Folder 2 (nor-NO)
      ----Article 1 (eng-GB, nor-NO)
      

      4. Go to Folder 2's "Translations" tab, uncheck "Use the main language if there is no prioritized translation." option, and click on the "Update" button;
      5. Go to Article 1's "locations" tab, and selected "Home / Folder 2 / Article 1" as the main location;
      6. Edit admin siteaccess site.ini [RegionalSettings], and set "ShowUntranslatedObjects=disabled" and also comment out "SiteLanguageList[]=nor-NO":

      [RegionalSettings]
      Locale=eng-GB
      ContentObjectLocale=eng-GB
      ShowUntranslatedObjects=disabled
      SiteLanguageList[]=eng-GB
      # SiteLanguageList[]=nor-NO
      SiteLanguageList[]=por-PT
      TextTranslation=disabled
      

      7. Go to Folder 1, edit Article 1 in new translation, choose language 3 (por-PT in my tests) and publish. The following error is generated:

      The draft could not be stored.
       
      The following locations are invalid:
      * A node in the node assignment list has been deleted.
      * No main node selected, please select one.
      

        Activity

        Hide
        Gunnstein Lye added a comment -

        Closing as Invalid. When removing a language from SiteLanguageList you cannot also disable ShowUntranslatedObjects, and still be able to deal with objects of that language.

        https://github.com/ezsystems/ezpublish-legacy/blob/2012.9/settings/site.ini#L890
        "Only objects existing in these languages will be shown (unless ShowUntranslatedObjects is enabled)."

        https://doc.ez.no/eZ-Publish/Technical-manual/4.x/Features/Multi-language/Configuring-the-site-languages/
        "If an object does not exist in any of the site languages, it will not be shown unless it is always available or if you configure the siteaccess to display untranslated content."

        Given the stated problem of the reporter...:
        "We have editors in 20 different countries, each with it's own admin siteaccess that limits the editor to only his language. The problem here can happen when two or more countries share the same content objects, which may also be located in different parts in the structure."

        ...the best solutions seems to me to have only one admin siteaccess with all languages in SiteLanguageList, and use roles and policies to limit what the editors can translate. E.g.:

        content / translate / Language( English )
        content / translate / Language( French )
        content / translate / Language( German )
        

        Show
        Gunnstein Lye added a comment - Closing as Invalid. When removing a language from SiteLanguageList you cannot also disable ShowUntranslatedObjects, and still be able to deal with objects of that language. https://github.com/ezsystems/ezpublish-legacy/blob/2012.9/settings/site.ini#L890 "Only objects existing in these languages will be shown (unless ShowUntranslatedObjects is enabled)." https://doc.ez.no/eZ-Publish/Technical-manual/4.x/Features/Multi-language/Configuring-the-site-languages/ "If an object does not exist in any of the site languages, it will not be shown unless it is always available or if you configure the siteaccess to display untranslated content." Given the stated problem of the reporter...: "We have editors in 20 different countries, each with it's own admin siteaccess that limits the editor to only his language. The problem here can happen when two or more countries share the same content objects, which may also be located in different parts in the structure." ...the best solutions seems to me to have only one admin siteaccess with all languages in SiteLanguageList, and use roles and policies to limit what the editors can translate. E.g.: content / translate / Language( English ) content / translate / Language( French ) content / translate / Language( German )

          People

          • Assignee:
            Unassigned
            Reporter:
            Nuno Oliveira (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 45 minutes
              45m