In the case of HomePortals, this release includes a brand new plugin called "CMS". This plugin is basically an entire "live authoring" interface that can be plugged in and activated into any HomePortals-based application by just calling the plugin. The idea is to provide a simple way for creating/updating content and managing page layout, while at the same time abstracting the user from all the complexities of the internal configuration and structure. I'll explain more and show some screenshots on a follow up post.

In ColdBricks, there is now an improved interface for configuring and enabling/disabling site plugins. The site plugins screen (inside the site configation module) now displays all built-in plugins available in your HomePortals installation, along with information about what each does and a quick way for enabling and disabling them. Of course there is always the option to add your own plugins either by providing the full plugin path, or by placing them inside the /homePortals/plugins directory.

For more detail on what changed, here are the changelogs for each version:

ColdBricks 1.1.1095
- Fixed bug: plugins screen in site config module was saving plugins path as file path instead of dot-notation path, which was working in Railo but not in ColdFusion
- Fixed errors caused by an update on how HomePortals stores plugins internally
- Improved screen to enable/disable site plugins by using automatic detection of available built-in plugins (these are the plugins contained within the /homePortals/plugins directory)
- The 'edit config files' screen in the config modules now has the main homeportals config file selected by default
HomePortals 3.1.544
- Fixed bug in which Label and URL defined as resource properties were being ignored when displaying an image from the resource library
- Added built-in custom section name 'HTMLHEAD' for injecting content directly into the  area of the rendered document.
- Added CMS plugin as a linked external
- refactored to top-level plugins branch
- Added removal of surrounding whitespace for text elements when parsing a page in XML format
- modified internal storage of plugin declarations in config to preserve order in which they are declared since that also determines the order in which they are loaded. Plugins are now stored as an array instead of a struct. This affected the returnType of the getPlugins() method in the configBean object.
- Applied Trim() to text values when parsing from a config XML
- Fixed inconsistent behavior when serializing top-level keys that contained simple values to XML format. Now they behave like the complex values in the sense that if they are not defined on the bean (or if they have an empty value), then they are not included on the resulting XML.
- When calling initEnv() only flush cache registry if we are initializing plugins. This will fix the issue of removing caches registered during a plugin initialization
- When throwing an error for an unknown cache request, show the name of the requested cache on the error message

Enjoy!