1.3-M2 to 1.3-M3 upgrade

Changes

• Various improvements to the skinning: the skinning now happens in two steps: first a page-specific stylesheet or template, and then a layout.xsl defining the general layout. The layout.xsl has a well-defined input. The common stylesheets have been dropped, instead a new fallback mechanism has been added: if a file does not exist in a skin, it is taken from its parent skin. This avoids the need to copy all XSLs and other resources into each skin. Combined, all these changes make skins easier to create and maintain. See the updated skinning documentation.
• A new, powerful Publisher request model. At first sight for many users this is a behind-the-scenes refactoring, but it opens the way to more customised publishing possibilities. See also the new Wiki extension possibilities and samples mentioned below.
• Teletype text support in the wysiwyg editor.
• Some fragment identifier support.
• Query language: added a versionId identifier, and new conditions IsLinked() and IsNotLinked() to find documents that are or are not linked by any other document.
• Link extraction is now also performed for navigation trees.
• The document info window now shows the document type of the document.
• The global (non-site-specific) skin can now be configured in a siteconf.xml file below the sites directory (previously: was hardcoded in the sitemap.xmap)
• Changes to skinconf.xml files are automatically detected (previously required touching siteconf.xml)
• Cross-site extensions: Wiki extensions which are available in all sites (previously, only site-specific extensions were possible)
• New possibilities in Wiki extensions due to new Publisher request model and some publishing refactorings. See the documentation and some new samples, including:
• RSS feeds
• aggregated publishing of all documents in a navigation tree
• A new ACL permission: "read live", which allows read access but only to the data of the live version of a document (and non-versioned properties). This permission doesn't allow access to retired documents either.
• Better management of HTTP connections in the repository client.

Compatibility

Important: please check the compatibility notes for this release to see if there is anyting that applies to your usage of Daisy.

Upgrading

Before starting

Shutdown Daisy (the Repository Server, the Daisy Wiki, and the OpenJMS server)

Make backups! More specifically:

• make a copy of the daisy data directory
• do a dump of the database:
  mysqldump daisyrepository -uuser -ppassword > daisyrepo.sql

Update database schema

There have been changes to the database schema.

To do the appropriate changes to the MySQL database, an upgrade script is available.

To execute the upgrade script, perform the following steps in a command prompt or shell:

cd <DAISY_HOME>/misc
mysql -Ddaisyrepository -udaisy -p<password>
[then on the mysql prompt]
\. daisy-1_3_M2-to-1_3_M3.sql 

Copy over the old configuration

• Copy <OLD_DAISY_HOME>/openjms/config/openjms.xml to <NEW_DAISY_HOME>/openjms/config/openjms.xml
• Copy <OLD_DAISY_HOME>/daisywiki/webapp/daisy/sites/* to <NEW_DAISY_HOME>/daisywiki/webapp/daisy/sites
• In <NEW_DAISY_HOME>/daisywiki/webapp/WEB-INF/cocoon.xconf, adjust the following passwords with the values you can find in <OLD_DAISY_HOME>/daisywiki/webapp/WEB-INF/cocoon.xconf:
  • Adjust the password for openjms user (if not left to default): <credentials password="openjms" username="admin"/>
  • Adjust the password for "internal' user: <cacheUser login="internal" password="defaultpwd"/>
  • Adjust the password for the "registrar" user: <registrarUser login="registrar" password="defaultpwd"/>
• If you created any document type-specific stylesheets, you can copy them over also (see also the compatibilty notes!)
• If you developed a custom skin, then you'll have to update it to work with the new version (see also the compatibility notes).

Edit <DAISY_HOME>/openjms/bin/setenv.(sh|bat), uncomment the line defining the CLASSPATH and put the MySQL driver in the CLASSPATH, which can be found at (substitute DAISY_HOME by its actual location):

DAISY_HOME/lib/mysql/jars/mysql-connector-java-3.0.15-ga-bin.jar

Start the servers

Start OpenJMS, the Daisy Repository Server, and the Daisy Wiki.

If necessary, first update the DAISY_HOME and OPENJMS_HOME variables to point to the location of the new Daisy version.

Note about static resources and caching

Since static resources are cached for about 5 hours by your browser, you might need to do a full reload (shift + reload button on the browsers' toolbar). Also when opening the editor for the first time do a shift + reload.

If these instructions or unclear to you, or if you find an error in them, please share them with us on the Daisy mailing list or by leaving a comment.