Details
-
Bug
-
Resolution: Fixed
-
High
-
4.7.0, 5.4.1
Description
Steps to reproduce:
Prepare the environment:
- Prepare two 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 on contentstagingsource.ini.append.php:
TransportClass=eZRestApiEmbeddedClientStagingTransport471
Reproduce the issue:
1. Source & Target: go to Setup/States and create a new state group with 2 object states, as follows:
Identifier: state_for_test
Name: For test
Object states in group:
Identifier: true
Name: True
Identifier: false
Name: False
2. Source: create a test content (used an article), and set "state_for_test" state group to "false". Publish;
3. Source: sync article to target instance;
4. Target: check that the content object has been synced and check the state: it has been lost during the sync, as it is set to "true".