Once you have installed the plugin into your application there are some Grails configurations you may need to change to make the CMS work in your application. These options are required for Weceem to operate correctly inside your app.
There are however several other optional configuration options that let you customize how it behaves and looks.
By default, Grails applications have content negotiation enabled based on file extensions in the URI, and this file extension is then removed from the URI. If you want your CMS to function correctly with content URIs like "common.css" and "jquery.js" then you need to turn this off. To do so, change your application's Config.groovy like this:
grails.mime.file.extensions = false
If you want to replicate the behaviour of the binary Weceem Application WAR that can serve content from the "/" URI of your application, you must make sure the default URL Grails mapping for "/" in your application is removed. You will also probably benefit from removing the generic "$controller/$action?/$id?" mapping which can cause confusion.
You can namespace all Weceem controllers using configuration options to prefix all URIs that Weceem uses.
See the configuration options page for more details.
You must tell Weceem what default content spaces are available to users or your code. There are two default spaces provided by the plugin but usually your application will want to specify alternative defaults so that it "boots" with your own content in it.
See the configuration options page for more details.
