Try an embedded document approach for INTEGRATED-219

Description

Background

  • The solution in the PR used a form to restore the draft. We don't like this approach

  • During a brainstorm session one other solution came up: store the draft as an embedded content object

Requirements

  • Make a test setup with embedded storage of the content document and prove it can be used for the draft.

  • In previous tests the retrieval of the document was a problem. Make sure it is not.

Technical tasks

None

Deployment actions

None

Activity

Show:
Jeroen van Leeuwen
December 22, 2016, 10:15 AM

zou jij nog kunnen kijken of deze issue goedgekeurd kan worden?

API
December 22, 2016, 11:53 AM

.Schatting van 12.5 uur is geaccepteerd door Integrated Marijn (in opdracht ingevoerd door Marijn Otte).

Jan Sanne Mulder
January 3, 2017, 1:45 PM

Changes based on 0.6:
https://bitbucket.org/eactive/integrated-content-bundle/branches/compare/INTEGRATED-951%0D0.6#diff

It kind of work but probably not in the way we want. When you embed a new document in the draft collection then it is also created on the content collection. Didnt really try what happend when you try to edit a document but that probably also gives problems. Deleting the document from the draft collection gave problems with other code. As uncommenting line https://bitbucket.org/eactive/integrated-content-bundle/branches/compare/INTEGRATED-951%0DINTEGRATED-219#LController/ContentController.phpT448 will result in foreign key errors in the workflow bundle.

Jan Sanne Mulder
January 3, 2017, 1:49 PM

I setup a test and made some conclusions so I am not sure what to do with the issue now.

Assignee

Unassigned

External issue ID

None

Client

None

Min. hours

None

Dev hour estimate

None

Sprint

None

Fix versions

Configure