[
https://issues.apache.org/jira/browse/UNOMI-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18144261#comment-18144261
]
Serge Huber commented on UNOMI-1064:
------------------------------------
Pull request: https://github.com/apache/unomi/pull/962
> Explain the web tracker upgrade in the manual
> ---------------------------------------------
>
> Key: UNOMI-1064
> URL: https://issues.apache.org/jira/browse/UNOMI-1064
> Project: Apache Unomi
> Issue Type: Task
> Components: unomi-tracker
> Affects Versions: unomi-4.0.0
> Reporter: Serge Huber
> Priority: Major
> Fix For: unomi-4.0.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> h3. Summary
> The manual tells a site to set an API key on the web tracker, but it does not
> say what else changes when the site moves from tracker 1.x to 2.0. It also
> does not say that the script served by Unomi is updated with the server,
> while an npm install or a copied file is not. Someone upgrading can miss both
> the required key and the changes they will notice on the page.
> The goal of this ticket is to put that information in the manual, on the
> tracker page and on the pages people read when they upgrade, and to point to
> the tracker project for the full list.
> h3. How to test
> Read the web tracker page and the migration pages. Check that both explain
> the tracker upgrade, and that the migration pages link to the tracker section.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)