[#WCM-279] 0.3 Release Notes information - jira.jcatalog.com

This is a task for holding "headline" information about all the stuff to mention in release notes.

Site URLs no longer contain ?space= variable
New aliasURI support on Space(s) to support control of the URI needed to access the space, including setting which is the default.
New content type JavaScript
New content type Folder
New improved repository tree UI
Repository UI supports search/filtering
New default space template mechanism with example space
New breadcrumb tag
New menu tag
New countChildren tag
New ifUserCanEdit tag
New ifContentIs tag
New ifContentIsNot tag
Templates inherited from parent nodes
Support for Widgets rendering other nested Widgets
Fixes and improvements to import/export handling
Fixes to ordering of nodes in the repository using drag and drop
New content types for blogs: Blog, Blog Entryand Comment (work in progress)
General status - Wiki and Blog still not functional, not for use. Wiki does not render correctly, has no site visitor editing. Blog requires comment submission, comment moderation and custom admin UI
JNDI Datasource support (jdbc/WeceemDS)
Compatible with postgres (user+role tables renamed)
Configurable search index filesystem path

Note

Applications using the plugin must set "grails.mime.file.extensions = false" in Config.groovy
Applications that want to use the default URI / for a space must remove the default "/" (view:'index') mapping from their UrlMappings
Only Grails 1.2m2 or higher is recommended. Grails 1.1.1 may work, but your mileage may vary, we have seen "Caused by: org.hibernate.AssertionFailure: collection [org.weceem.content.Content.children] was not processed by flush()" errors
If using Grails 1.2m2 or m3, you mist unzip the application, then run grails install-plugin hibernate GRAILS-VER before running the application
Existing sites will not have an aliasURI set. Please edit your Spaces so have an aliasURI matching their name, or blank if they are to be the default uri space eg /
Any uploaded files stored in <weceem>/WeceemFiles/<spaceName> will need to have the folder renamed to match the space's aliasURI. For the space with blank aliasURI, use the folder name _ROOT. For example a space previously called "weceem" that was the being used by weceem 0.2 as the default space, rename <weceem>/WeceemFiles/weceem/ to <weceem>/WeceemFiles/_ROOT/
If you do have to rename any WeceemFiles/<spaceName> folders, you will need to edit any content that links to those files, eg CSS and HTML content that reference images will need the links updated to point to the new folder name

Upgrade considerations

User, Role and User roles table names have changed for compatibility with other database servers eg Postgres, so tables will need to be renamed manually (but to what - naming is DB dependent because of hibernate?) or new code installed and users re-created and passwords change as necessary
The configuration of searchable index path has changed. Users must either set the VM property searchable.index.path to the location of the existing path (${userHome}/.weceem/searchable-index) or allow the application to write to "/var/cache/weceem/searchable-index" which is the new default location.
Make sure that if you specify weceem.config.location VM property that the path begins with "file://"
Recommend full Export of each space and backing up WeceemFiles/ folders before upgrade

Ascending order - Click to sort in descending order

There are no comments yet on this issue.

Weceem