Release Notes for 1.1
Version 1.1.1 of Weceem resolves a number of issues found since the release of 1.0 as well as adding some refinements and Grails 2 compatibility.
Fixes include:
-
Grails 2.0 RC1 compatibility
-
Refactor to avoid static holders for GrailsApplication and Config
-
Major improvements to space deletion code to delete content in the correct order
-
All new preview mechanism that does not rely on transaction rollbacks
-
A number of problems relating to searching and search related tags are resolved
-
A new wcm:render tag has been added for embedding content in your own GSP views
-
Issues with wcm:dataFeed if there are less thant "max" entries
-
Usability improvements, such as automatically switching to the correct space after a create/import
-
Fix for bugs in wcm:resource tag
-
Added short-circuit logic to avoid bug in Commons IO relating to moving a server folder to the same hierarchy level - causing an infinite loop creating nested directories on the folder
-
Fix for missing import in wcm:cache tag
Installation Changes
To install the plugin in a Grails 1.3.x application you can use:
grails install-plugin weceem 1.1.1
For Grails 2 RC1 however you cannot use install-plugin and must edit your plugin dependencies in BuildConfig.groovy to include:
plugins {
compile ":weceem:1.1.1"
}
Domain Model Changes
To make it possible to delete all space content reliably, the domain model has changed such that all content references must be nullable. Your database may not update its schema to match this new NULLABLE constraint. If you experience problems deleting spaces due to referential integrity you will need to update your schema to allow NULL values in all Weceem content reference columns. New databases will be created with nullable references by default.
Note that this also affects custom content types - you must ensure any domain object references are nullable - including references to other weceem content.
New location for source code
