Details
-
Improvement
-
Resolution: Unresolved
-
High
-
5.2-dev
-
Server OS: Red Hat 6.4
PHP: 5.3.3
Database: MySQL 5.1.61
Browser: Firefox 20
Description
This is an improvement regarding the update made on issue EZP-20537
When the sync failed on "content update" it should try to do a create action "content create", this was the implemented UPSERT strategy.
However this might bring some inconsistency and therefore it should throw a visible warning/notice or any other kind of visible info for the user that a update failed and a create was made instead.
Attachments
Issue Links
- relates to
-
EZP-20537 ezcontentstaging: syncing a copy fails if the copy is made from a version > 1
- Closed