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

    Details

      Description

      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:

      https://doc.ez.no/Extensions/eZ-Publish-extensions/eZ-Content-Staging/eZ-Content-Staging-1.x/Installation

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

      TransportClass=eZRestApiEmbeddedClientStagingTransport471
      

      Pre-requisites:

      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
      Description:

      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 ] [127.0.0.1] eZContentStagingEvent::syncEvents:
      Failed syncing event 19, transport error code: HTTP error 400 (Bad Request)
      

        Issue Links

          Activity

          Nuno Oliveira (Inactive) created issue -
          Nuno Oliveira (Inactive) made changes -
          Field Original Value New Value
          Description h4. 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:

          https://doc.ez.no/Extensions/eZ-Publish-extensions/eZ-Content-Staging/eZ-Content-Staging-1.x/Installation

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

          TransportClass=eZRestApiEmbeddedClientStagingTransport471

          * - Pre-requisites:*

          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

          Submit the creation of the class

          2. 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
          Description:

          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:

          {noformat}
          Event synchronisation action results :

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

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

          {noformat}
          [ Dec 03 2014 17:17:18 ] [127.0.0.1] eZContentStagingEvent::syncEvents:
          Failed syncing event 19, transport error code: HTTP error 400 (Bad Request)
          {noformat}
          h4. 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:

          https://doc.ez.no/Extensions/eZ-Publish-extensions/eZ-Content-Staging/eZ-Content-Staging-1.x/Installation

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

          TransportClass=eZRestApiEmbeddedClientStagingTransport471

          *Pre-requisites:*

          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

          Submit the creation of the class

          2. 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
          Description:

          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:

          {noformat}
          Event synchronisation action results :

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

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

          {noformat}
          [ Dec 03 2014 17:17:18 ] [127.0.0.1] eZContentStagingEvent::syncEvents:
          Failed syncing event 19, transport error code: HTTP error 400 (Bad Request)
          {noformat}
          Nuno Oliveira (Inactive) made changes -
          Description h4. 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:

          https://doc.ez.no/Extensions/eZ-Publish-extensions/eZ-Content-Staging/eZ-Content-Staging-1.x/Installation

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

          TransportClass=eZRestApiEmbeddedClientStagingTransport471

          *Pre-requisites:*

          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

          Submit the creation of the class

          2. 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
          Description:

          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:

          {noformat}
          Event synchronisation action results :

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

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

          {noformat}
          [ Dec 03 2014 17:17:18 ] [127.0.0.1] eZContentStagingEvent::syncEvents:
          Failed syncing event 19, transport error code: HTTP error 400 (Bad Request)
          {noformat}
          h4. 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:

          https://doc.ez.no/Extensions/eZ-Publish-extensions/eZ-Content-Staging/eZ-Content-Staging-1.x/Installation

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

          {noformat}
          TransportClass=eZRestApiEmbeddedClientStagingTransport471
          {noformat}

          *Pre-requisites:*

          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

          Submit the creation of the class

          2. 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
          Description:

          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:

          {noformat}
          Event synchronisation action results :

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

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

          {noformat}
          [ Dec 03 2014 17:17:18 ] [127.0.0.1] eZContentStagingEvent::syncEvents:
          Failed syncing event 19, transport error code: HTTP error 400 (Bad Request)
          {noformat}
          Nuno Oliveira (Inactive) made changes -
          Description h4. 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:

          https://doc.ez.no/Extensions/eZ-Publish-extensions/eZ-Content-Staging/eZ-Content-Staging-1.x/Installation

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

          {noformat}
          TransportClass=eZRestApiEmbeddedClientStagingTransport471
          {noformat}

          *Pre-requisites:*

          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

          Submit the creation of the class

          2. 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
          Description:

          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:

          {noformat}
          Event synchronisation action results :

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

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

          {noformat}
          [ Dec 03 2014 17:17:18 ] [127.0.0.1] eZContentStagingEvent::syncEvents:
          Failed syncing event 19, transport error code: HTTP error 400 (Bad Request)
          {noformat}
          h4. 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:

          https://doc.ez.no/Extensions/eZ-Publish-extensions/eZ-Content-Staging/eZ-Content-Staging-1.x/Installation

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

          {noformat}
          TransportClass=eZRestApiEmbeddedClientStagingTransport471
          {noformat}

          *Pre-requisites:*

          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
          Description:

          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:

          {noformat}
          Event synchronisation action results :

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

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

          {noformat}
          [ Dec 03 2014 17:17:18 ] [127.0.0.1] eZContentStagingEvent::syncEvents:
          Failed syncing event 19, transport error code: HTTP error 400 (Bad Request)
          {noformat}
          Nuno Oliveira (Inactive) made changes -
          Status Open [ 1 ] Confirmed [ 10037 ]
          Paulo Lopes (Inactive) made changes -
          Status Confirmed [ 10037 ] InputQ [ 10001 ]
          Bertrand Dunogier made changes -
          Status InputQ [ 10001 ] Development [ 3 ]
          Assignee Bertrand Dunogier [ bertrand.dunogier@ez.no ]
          Nuno Oliveira (Inactive) made changes -
          Affects Version/s 5.3.3 [ 13484 ]
          Hide
          Bertrand Dunogier added a comment -

          Issue reproduced.

          Show
          Bertrand Dunogier added a comment - Issue reproduced.
          Bertrand Dunogier made changes -
          Status Development [ 3 ] Development review [ 10006 ]
          Bertrand Dunogier made changes -
          Summary eZ Content Staging 4.7.1: whitespace in a a required text block field causes sync failure Staging: whitespace in a a required text block field causes sync failure
          Show
          Bertrand Dunogier added a comment - PR https://github.com/ezsystems/ezcontentstaging/pull/39 .
          Bertrand Dunogier made changes -
          Remote Link This issue links to "PR ezsystems/ezcontentstaging#39 (Web Link)" [ 14506 ]
          Bertrand Dunogier made changes -
          Status Development review [ 10006 ] Development Review done [ 10028 ]
          Bertrand Dunogier made changes -
          Affects Version/s 5.2 [ 12582 ]
          Affects Version/s 5.1 [ 11280 ]
          Affects Version/s 5.0 [ 10300 ]
          Bertrand Dunogier made changes -
          Environment eZ Content Staging 4.7.1
          Hide
          Bertrand Dunogier added a comment -
          Show
          Bertrand Dunogier added a comment - Merged to ezcontentstaging/master@e1af243c .
          Bertrand Dunogier made changes -
          Fix Version/s 4.7 Maintenance [ 12583 ]
          Fix Version/s 5.0 Maintenance [ 11287 ]
          Fix Version/s 5.1 Maintenance [ 12301 ]
          Fix Version/s 5.2 Maintenance [ 12782 ]
          Fix Version/s 5.3.5 [ 13889 ]
          Bertrand Dunogier made changes -
          Status Development Review done [ 10028 ] Documentation done [ 10011 ]
          Pedro Resende (Inactive) made changes -
          Status Documentation done [ 10011 ] QA [ 10008 ]
          Assignee Bertrand Dunogier [ bertrand.dunogier@ez.no ] Pedro Resende [ pedro.resende@ez.no ]
          Pedro Resende (Inactive) made changes -
          Rank Ranked lower
          Pedro Resende (Inactive) made changes -
          Flagged Impediment [ 10000 ]
          Pedro Resende (Inactive) made changes -
          Attachment after_error.png [ 19015 ]
          Attachment selectable.png [ 19016 ]
          Pedro Resende (Inactive) made changes -
          Comment [ A comment with security level 'Employees' was removed. ]
          Hide
          Pedro Resende (Inactive) added a comment -

          Tested and approved by Q.A.

          Show
          Pedro Resende (Inactive) added a comment - Tested and approved by Q.A.
          Pedro Resende (Inactive) made changes -
          Assignee Pedro Resende [ pedro.resende@ez.no ]
          Status QA [ 10008 ] Closed [ 6 ]
          Resolution Fixed [ 1 ]
          André Rømcke made changes -
          Resolution Fixed [ 1 ]
          Status Closed [ 6 ] Reopened [ 4 ]
          André Rømcke made changes -
          Fix Version/s 5.4.2 [ 13979 ]
          André Rømcke made changes -
          Status Reopened [ 4 ] Closed [ 6 ]
          Resolution Fixed [ 1 ]
          André Rømcke made changes -
          Workflow eZ Engineering Scrumban Workflow [ 65362 ] EZ* Development Workflow [ 85581 ]
          Alex Schuster made changes -
          Workflow EZ* Development Workflow [ 85581 ] EZEE Development Workflow [ 124429 ]
          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

            People

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

              Dates

              • Created:
                Updated:
                Resolved: