[MULTISITE-75] Remove uses of the Content API Created: 14/Jul/17  Updated: 31/Aug/17  Resolved: 30/Aug/17

Status: Closed
Project: Magnolia Multisite Module
Component/s: None
Affects Version/s: None
Fix Version/s: 1.3

Type: Task Priority: Neutral
Reporter: Michael Mühlebach Assignee: Oanh Thai Hoang
Resolution: Fixed Votes: 0
Labels: tech-debt
Remaining Estimate: 0d
Time Spent: 1d 4.5h
Original Estimate: 2d

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: Remove Content API
Sprint: Saigon 109, Saigon 110, Saigon 111
Story Points: 5

 Description   

see https://wiki.magnolia-cms.com/pages/viewpage.action?pageId=136852051 for further detail.



 Comments   
Comment by Mikaël Geljić [ 28/Aug/17 ]

Let's evaluate dropping migration from the end-of-life ETK module in 1.3 (either only support upgrades from 1.0, or 1.2 if that makes it even simpler).

Comment by Oanh Thai Hoang [ 28/Aug/17 ]

mgeljic: Tasks related to end-of-line ETK only handle in fresh-install so we don't need to drop migration

Comment by Mikaël Geljić [ 30/Aug/17 ]

Right, because ETK module was "renamed", so it was not possible to upgrade ETK from multisite deltas. Extra-install tasks were the only option, but their job is still to handle about ETK "migration" (so to speak), on the first time you installed multisite.

Anyway, as we've just reviewed in the version-handler, cleaning up this part is not trivial. We will use another ticket for this.

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