litvinovg/vivo
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

NIHVIVO-757 Add information on Google Analytics Tracking Code to upgrade-1.1.txt

Browse source
This commit is contained in:
rjy7 2010-07-08 21:32:44 +00:00
parent fb19508325
commit e8ddbc4dd3
1 changed files with 13 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

15
doc/upgrade-1.1.txt
View file

@ -54,7 +54,8 @@ II. The Upgrade Process
original source directory, the MySQL database, and the uploaded files original source directory, the MySQL database, and the uploaded files
directory (images). directory (images).
2. Download the new distribution file and unpack it into a new source directory. 2. Download the new distribution file and unpack it into a new source
directory.
3. Create deploy.properties, using the same values as in your previous 3. Create deploy.properties, using the same values as in your previous
installation. installation.
@ -66,7 +67,17 @@ II. The Upgrade Process
have changed. It will be necessary to inspect the new source files and have changed. It will be necessary to inspect the new source files and
add any changes to them at that time. add any changes to them at that time.
>>>>>> TBD -- Note on Google Analytics Tracking code to footer.jsp? (lines 68-73 in update-1.0.txt) Note: At a minimum it will be necessary to apply the Google Analytics
Tracking Code to googleAnalytics.ftl in the theme:
[new_source_directory]/themes/[theme_dir]/templates/googleAnalytics.ftl
A sample googleAnalytics.ftl is included in the built-in theme. This file
serves only as an example, and you must replace the tracking code shown
with your institution's own tracking code.
For additional information and a copy your institution's tracking code,
see the Google Analytics wiki page.
https://confluence.cornell.edu/display/ennsrd/Google+Analytics+for+UI
Note: This process assumes any changes made to the application were made in Note: This process assumes any changes made to the application were made in
the source directory and deployed, and were not made directly within the source directory and deployed, and were not made directly within