From 286388d8accd68b32e68c70cefe77386cb2b2702 Mon Sep 17 00:00:00 2001 From: ejc12 Date: Thu, 10 Feb 2011 14:47:05 +0000 Subject: [PATCH] I removed content on the customizing your theme and pointed to the site admin guide for this. I hope Nick is ok with that. --- doc/upgrade-1.2.html | 137 ++++--------------------------------------- 1 file changed, 13 insertions(+), 124 deletions(-) diff --git a/doc/upgrade-1.2.html b/doc/upgrade-1.2.html index 4ecbdd7c..577e59b5 100644 --- a/doc/upgrade-1.2.html +++ b/doc/upgrade-1.2.html @@ -34,8 +34,8 @@ at VIVOweb.org

- If you need to do a fresh install, please consult VIVO Release 1 v1.2 - Installation Guide + If you need to do a fresh install, please consult the VIVO Release 1 v1.2 + Installation Guide found on vivoweb.org or the install.html file located in the doc directory of the VIVO source code distribution. The installation document also has a list of the required software and versions. @@ -810,134 +810,23 @@ within a theme.

+ If you did not create a custom theme for your site previously, but used + the vivo-basic theme in its original directory, you need not take any + action in order to remain using the vivo-basic theme in 1.2. +

+

If you did make changes to the vivo-basic theme, you will need to reapply those changes. + We recommend you apply these changes to the wilma theme.

+
+ Please note: The vivo-basic theme has been deprecated and is + not recommended for production instances. +
+

For details on the new structure of themes in 1.2 and further information regarding the development of your own custom theme, please review the Site Administrator's Guide. This document will focus on updating an existing pre 1.2 theme.

-

Updating an Existing Theme

-

- If you already have an existing pre 1.2 instance running, follow step A or B below, - whichever is applicable to your site: -

-

- A. If you did not create a custom theme for your site previously, but used - the vivo-basic theme in its original directory, you need not take any - action in order to remain using the vivo-basic theme in 1.2. -

-
- Please note: The vivo-basic theme has been deprecated and is - not recommended for production instances. -
-

- B. If you created your own theme in VIVO 1.1, follow the steps below under sections - "Templates," "Stylesheets," and "Site Icons" to upgrade your theme to VIVO 1.2. -

-

- NC: Everything below up to Section VII still needs some work and is not ready for - prime time. -

-
-
- 1. Templates -
-
-
-
- a. Copy the directory /vivo/themes/vivo-basic/templates - into your theme directory /vivo/themes/[your-theme-name]. -
-
-
-
- b. Follow step i or ii below, whichever is applicable to your theme. -
-
-
    -
  1. - If you did not make any customizations to the templates in your - VIVO 1.1 theme, then you do not need to apply any additional changes - to the new 1.2 theme templates during the upgrade process. -
    2. -
  2. -

    - If you did make customizations to the templates in your VIVO 1.1 - theme, you will need to hand-replicate those modifications in the - new theme templates. -

    -

    - The theme template content that was previously contained in - three JSP files is now contained in five FTL files. The - correspondence between the 1.0 JSPs and the 1.1 FTLs is as - follows: -

    - 
    -                identity.jsp => identity.ftl
-                menu.jsp => menu.ftl and search.ftl
-                footer.jsp => footer.ftl and googleAnalytics.ftl
-
    -

    - googleAnalytics.ftl - is the file to which you add your site's Google Analytics Tracking - Code (see section II). -

    -

    - Consult the FreeMarker Template Author's Guide at http://freemarker.org/docs/dgui.html - and the Reference at http://freemarker.org/docs/ref.html - for complete documentation of the syntax and available built-in constructs. Template - authors need not be concerned with the Programmer's Guide or Java API documentation. -

    -
    3. -
-
-
-
-
- 2. Stylesheets -
-
- VIVO 1.2 includes changes to vivo-basic stylesheets. If you modified - styles in your VIVO 1.1 theme, you will not be able to simply copy the - 1.1 stylesheets into your 1.2 theme, because you will then lose 1.2 - style upgrades that your theme should pick up. Instead, you should - use the vivo-basic 1.2 stylesheets as a starting point, and manually - merge your 1.1 style modifications in as needed. -
-
- 3. Site Icons -
-
- Copy the site icons from your 1.1 theme into the site_icons folder in - your 1.2 theme. -
-
-

VII. Set Up SDB Store in the Background (Optional)

-

- If your VIVO installation is running in RDB mode, and you'd like to convert - to SDB, you can start the conversion process in the background while the RDB - system is running. This will reduce the delay in initial startup after the - application is redeployed with deploy.properties set for SDB. Note that it - is important not to edit any data anywhere in the application while this - background conversion is running. -

-

- To start the SDB conversion, log in as a system - administrator and request /sdbsetup. (For example, if your VIVO is installed - at http://vivo.myuniversity.edu/ you would type - http://vivo.myuniversity.edu/sdbsetup into your browser.) -

-

- Click the button that appears on this page. -

-

- During the course of the SDB setup, which may take several hours on a - large database, subsequent requests to /sdbsetup will display a - message that the operation is still in progress. When a request for this - page shows a message that the SDB setup has completed successfully, shut down - Tomcat, set deploy.properties to SDB mode, redeploy, and restart Tomcat. - VIVO will now be running from the SDB store. -