Details
-
Story
-
Resolution: Obsolete
-
High
-
None
-
5.3-dev
-
None
-
2
Description
Given I want to use workflows my content is not necessarily published straight away, and in case of approval workflows my editor might change the locations of my draft before publishing it.
Technical implications:
- API / SPI changes
- Some already modeled here: https://github.com/docb22/ezpublish-kernel/compare/master...backend_6.0
- including removal of loadParentLocationsForDraftContent()
- API changes might be needed in addition, like loadLocations() might need VersionInfo support/change or additional loadLocationsByVersionInfo() is needed
For reference here is old version of legacy schema (note: at least eznode_assignment.remote_id has become varchar in between):
http://doc.ez.no/schemadoc/tables/ezcontentobject_tree.html
http://doc.ez.no/schemadoc/tables/eznode_assignment.html
Attachments
Issue Links
- clones
-
EZP-22260 As legacy User I want node assignment remote id to be kept on publish
- Closed