Details
-
Bug
-
Resolution: Fixed
-
High
-
4.7.0
-
None
-
eZ Publish Enterprise 4.7, eZ Content Staging 4.7.1
-
Castor Core S2
Description
When using eZ Content Staging 4.7.1, if we set TransportClass=eZRestApiEmbeddedClientStagingTransport471, object priority is not synced.
Setting the environment:
- Create 2 new eZ Publish 4.7 installations, and install all available Service Packs;
- Install and activate eZ Content Staging 4.7.1 extension on both on both installations. For convenience, I attached eZ Content Staging 4.7.1 in this issue. Installation steps are here:
- This is only reproducible if, in contentstagingsource.ini, you use:
TransportClass=eZRestApiEmbeddedClientStagingTransport471
...instead of the standard:
TransportClass=eZRestApiEmbeddedClientStagingTransport
Steps to reproduce:
1. Login to admin interface and go to "Content structure" tab;
2. Create a new article, fill in all required fields, and publish e.g.
Home Articles (folder, object Id 59) Article 1 (article, object Id 96)
3. Set the priority of the newly created article to a value of your choice e.g. 10;
4. Go to Setup tab / Content staging, select both events - object publication and priority change - and click on 'Synchronize'.
The article was successfully synchronized on target installation, but the priority has not been updated, it's still 0.
On source installation, the following warning was displayed:
Event synchronisation action results : Object 59 to be synchronised to feed 47ezfc_cs2.com: failure (HTTP error 404 (Not Found)) [Event 39] Object 96 succesfully synchronised to feed 47ezfc_cs2.com [Event 38]
The following error was registerd on the error log:
[ Jul 03 2014 17:15:18 ] [127.0.0.1] eZContentStagingEvent::syncEvents: Failed syncing event 39, transport error code: HTTP error 404 (Not Found)