[PAGES-42] Introduce PagesContentConnector and ActionExecutor Created: 09/Nov/15  Updated: 17/Oct/16  Resolved: 03/Aug/16

Status: Closed
Project: Magnolia pages module
Component/s: None
Affects Version/s: 5.4.2
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Espen Jervidalo Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
duplicate
is duplicated by PAGES-80 Adapt pages app to Content-Connector ... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Story Points: 8

 Description   

These changes were introduced w/ PAGES-40 but held back due to API-compatibility.



 Comments   
Comment by Mikaël Geljić [ 28/Jul/16 ]

Do we still need or want to do this? Guess it's much less critical since the default-value problems have been addressed (so that also makes more room for the p13n-driven changes, for what I know). Any opinion on that ejervidalo?

I'll tentatively close it for now; we can still dig it up again if needs be.

Comment by Espen Jervidalo [ 03/Aug/16 ]

I overlooked/forgot about this issue. This was finally committed in the linked ticket PAGES-80. And yes we still want these changes: There are several customers currently re-using the page-editor for editing content other than 'website'-content.
I'll update the status.

UPD: The changes were anyway 'parked' on some branch.

Generated at Mon Feb 12 06:15:02 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.