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

Staging: whitespace in a a required text block field causes sync failure



      Steps to reproduce:

      Prepare the environment:

      • Prepare 2 eZ Publish 4.7 installations, fully patched. One will be your source server, and the other will be the target server;
      • Install eZ Content Staging 4.7.1 on both installations. More details here:


      Note: when installing eZ Content Staging 4.7.1 in the source server, make sure to use:



      1. Create a new content class on source installation:

      Name : Required test
      ID : required_test
      Container : Not checked

      Object name pattern : <name>

      Add two attributes as the following :

      Attribute Type : Text line

      • Name of the attribute : Name
      • ID of the attribute : name
      • Is required : checked

      Attribute Type : Text block

      • Name of the attribute : Description
      • ID of the attribute : description
      • Is required : checked

      2. Submit the creation of the class;
      3. Export the new class through a package and then import it on the target installation.

      Reproduce the issue:

      1. On source installation, create an object for the new "Required test" class:

      Name: Required text block with space

      Since the description field is required, enter a whitespace in it (ASCII CODE 32).

      2. Publish object (validation passes even with a whitespace);
      3. Go to "setup" tab -> Content staging, and sync the new object. The following error is generated:

      Event synchronisation action results :
      * Object 10112 to be synchronised to feed 47ezfc_cs2.com: failure (HTTP error 400 (Bad Request)) [Event 19]

      The folowing error is generated on var/log/error.log:

      [ Dec 03 2014 17:17:18 ] [] eZContentStagingEvent::syncEvents:
      Failed syncing event 19, transport error code: HTTP error 400 (Bad Request)

        Issue Links


          Transition Time In Source Status Execution Times Last Executer Last Execution Date
          Open Open Confirmed Confirmed
          5m 36s 1 nuno.oliveira@ez.no 03/Dec/14 7:09 PM
          Confirmed Confirmed InputQ InputQ
          15h 47m 1 Paulo Lopes (Inactive) 04/Dec/14 10:56 AM
          InputQ InputQ Development Development
          1d 1h 44m 1 Bertrand Dunogier 05/Dec/14 12:40 PM
          Development Development Development Review Development Review
          12d 23h 25m 1 Bertrand Dunogier 18/Dec/14 12:06 PM
          Development Review Development Review Development Review done Development Review done
          3d 23h 7m 1 Bertrand Dunogier 22/Dec/14 11:13 AM
          Development Review done Development Review done Documentation Review done Documentation Review done
          23m 57s 1 Bertrand Dunogier 22/Dec/14 11:37 AM
          Documentation Review done Documentation Review done QA QA
          5m 24s 1 pedro.resende@ez.no 22/Dec/14 11:43 AM
          QA QA Closed Closed
          6h 27m 1 pedro.resende@ez.no 22/Dec/14 6:10 PM
          Closed Closed Reopened Reopened
          14d 23h 17m 1 André Rømcke 06/Jan/15 5:28 PM
          Reopened Reopened Closed Closed
          29s 1 André Rømcke 06/Jan/15 5:28 PM


            • Assignee:
              Nuno Oliveira (Inactive)
            • Votes:
              0 Vote for this issue
              4 Start watching this issue


              • Created: