Loading...

XML

Word

Printable

Details

Type: Story
Resolution: Obsolete
Priority: High
Fix Version/s: None
Affects Version/s: 5.3-dev
Component/s: Platform > API interfaces, Platform > Repository & Services (Public API impl), Platform > SPI interfaces
Labels:
None

Story Points:
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

relates to

EZP-20089 Failures in Public API when setting remote id on Location on create

Closed

EZP-21114 Content Staging: publish event not removed from feed if target server has 'Wait until date' workflow

Closed

EZP-23589 Preview issue when relying on locations for unpublished content

Closed

Activity

People

Assignee:: Unassigned

Reporter:: André Rømcke (Inactive)

Votes:: 0 Vote for this issue

Watchers:: 0 Start watching this issue

Dates

Created:: 06/Feb/14 5:15 PM

Updated:: 13/Feb/18 11:54 PM

Resolved:: 13/Feb/18 11:54 PM

Time Tracking

Estimated:

Remaining:

Logged:

Not Specified