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

[Content Staging] Not possible to sync if content language differs from parent node's language

    Details

      Description

      If you create any content in a language that differs from the parent node's language, the sync will fail with the following error:


      Event synchronisation action results:
      Object 121 to be synchronised to feed teste_sync: failure (HTTP error 400 (Bad Request)) [Event 4]

      Steps to Reproduce

      1. Set ContentStaging to sync with an English Folder as source.
      2. Inside the source folder, create two objects: one in English, one in German.
      3. Try to sync the objects

      Note: It might be related to EZP-20645

        Issue Links

          Activity

          Hide
          Eduardo Fernandes (Inactive) added a comment -

          QA Tested and Approved

          Show
          Eduardo Fernandes (Inactive) added a comment - QA Tested and Approved
          Hide
          Bertrand Dunogier added a comment - - edited

          Creating follow-ups for documentation: EZP-23359, EZP-23360.

          Show
          Bertrand Dunogier added a comment - - edited Creating follow-ups for documentation: EZP-23359 , EZP-23360 .
          Hide
          Bertrand Dunogier added a comment -

          The legacy REST API (v1) doc must be updated to document the X-Siteaccess header.

          If not specified, the REST calls will be executed with the default siteaccess. To specify one, it must be provided using the X-Siteaccess header.

          Note that host based mapping (like api.site.com) would also work to customize the REST API siteaccess.

          Show
          Bertrand Dunogier added a comment - The legacy REST API (v1) doc must be updated to document the X-Siteaccess header. If not specified, the REST calls will be executed with the default siteaccess. To specify one, it must be provided using the X-Siteaccess header. Note that host based mapping (like api.site.com) would also work to customize the REST API siteaccess.
          Hide
          Bertrand Dunogier added a comment -

          ezsystems/ezpublish-legacy#1070 merged to master@d80e31b

          Show
          Bertrand Dunogier added a comment - ezsystems/ezpublish-legacy#1070 merged to master@d80e31b
          Hide
          Bertrand Dunogier added a comment -

          Note: the fix requires, most likely, that an option is added to the wsproviders.ini file for the server, to specify the siteaccess (if it is indeed the same error).

          Show
          Bertrand Dunogier added a comment - Note: the fix requires, most likely, that an option is added to the wsproviders.ini file for the server, to specify the siteaccess (if it is indeed the same error).
          Hide
          Bertrand Dunogier added a comment -

          Pull-request for ezpublish-legacy: https://github.com/ezsystems/ezpublish-legacy/pull/1070.

          Show
          Bertrand Dunogier added a comment - Pull-request for ezpublish-legacy: https://github.com/ezsystems/ezpublish-legacy/pull/1070 .
          Hide
          Bertrand Dunogier added a comment -

          Reproduced successfully.

          Show
          Bertrand Dunogier added a comment - Reproduced successfully.

            People

            • Assignee:
              Unassigned
              Reporter:
              Eduardo Fernandes (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              5 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 - 2 hours, 30 minutes
                2h 30m