[MULTISITE-20] Add areas to default prototype to insert scripts, such as marketing tags Created: 29/May/14  Updated: 25/Jul/14  Resolved: 29/May/14

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

Type: Task Priority: Neutral
Reporter: Cheng Hu Assignee: Peili Liang
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MULTISITE-25 MultiSite doesn't get TagsManager are... Closed
relation
is related to MGNLTAGS-33 Migrate new areas and its model to STK Closed
is related to MGNLSTK-1388 Add areas to default prototype to ins... Closed
is related to MGNLTAGS-42 Make module EE Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

Add 3 areas to the prototype, in the header, at the beginning of the body, and at the end of the body, in order to be able to insert scripts such as marketing tags. This will be done in STK, see MGNLSTK-1388. Here we need to change the version handler to add the areas.

Originally these areas were inserted by the marketing tags module. However, after discussion during ownership, it was decided to add these areas directly to the STK.

The things to do are:

  • Change the version handler
  • Test the version handler


 Comments   
Comment by Jan Haderka [ 29/May/14 ]

If those areas are added by STK, why is version handler of ETK needed to insert them?

Comment by Cheng Hu [ 29/May/14 ]

Our understanding is that during a fresh install, ETK creates the default prototype by copying it from STK using getExtraInstallTasks(...) in its version handler.

If a person already has multisite installed, and is upgrading it to the current version, then our thought is that the default prototype is a copy of the old STK prototype, and so the additional area introduced in the most recent version of the STK must be added explicitly by the version handler.

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