The Ortus BlogBox

"Ortus: A rise, beginning, coming into being, born, the origin!"


ColdBox 4.3.0 Released

Luis Majano
Oct 19, 2016


We are pleased to announce the general availability of ColdBox 4.3.0, WireBox 4.3.0, CacheBox 4.3.0 and LogBox 4.3.0. This is a minor release with some great improvements and lots of bug fixes. So let's look at the major things in this release.

CacheBox, ColdBox MVC, ColdFusion, CommandBox, News, Releases, WireBox 0

CommandBox 3.3.0 Released - server enhancements and bug fixes.

Brad Wood
Oct 09, 2016


We are pleased to announce a minor release of our CommandBox CLI, server, and package manager tool today. Version 3.3.0 of CommandBox is our second minor release since we added support for starting Adobe ColdFusion engines, Railo, and Lucee 5 web servers.  This release has 46 tickets that focus on cleaning up more rough edges around the server implementation, adding features, and of course, fixing bugs.  A big thanks to Denny Valiant and his work on Runwar, which is the library that makes CommandBox's severs work.

Download it

You can download the latest binary from our CommandBox product home page:

CommandBox Download

We've also updated our CommandBox documentation book to cover all these new features which can be found here:

CommandBox GitBook Documentation

Remember, you can send pull requests via Github for any typos or missing content you find in our GitBooks!  

The Command API Docs also show the latest commands and usage too:

CommandBox Command API Documentation

What's New?

Let's take a quick peek at the major new features in CommandBox 3.3

Server Enhancements

The embedded CommandBox server have seen a number of nice enhancements to make it easier for you to use CommandBox for super easy local development.

Fusion Reactor Module

The more people begin to use CommandBox for local development, the more interested they became in being able to run FusionReactor on their dev servers to help trouble shoot their code.  That's why we created a CommandBox FusionReactor module.  It's not part of the core, but can be installed in a single command and will attach FusionReactor's server monitor to every server you start.  You'll need to have a FusionReactor license or sign up for a trial to use it.

install commandbox-fusionreactor
fr register "your FR license key"
server start
fr open

Web Aliases

CommandBox allows you to create web aliases for the web server that are similar to virtual directories. The alias path is relative to the web root, but can point to any folder on the hard drive. Aliases can be used for static or CFM files.  To configure aliases for your server, create an object under web called alises. The keys are the web-accessible virtual paths and the corresponding values are the relative or absolute path to the folder the alias points to.

Here's what your server.json might look like.

  "web" : {
    "aliases" : {
      "/foo" : "../bar",
      "/js" : "C:\static\shared\javascript"

Here's how to create aliases from the server set command:

server set web.aliases./foo = bar

Custom Error Pages

You can customize the error page that CommandBox servers return. You can have a setting for each status code including a default error page to be used if no other setting applies.
Create an errorPages object inside the web object in your server.json where each key is the status code integer or the word default and the value is a relative (to the web root) path to be loaded for that status code.
This is what you server.json might look like:

  "web" : {
    "errorPages" : {
      "404" : "/path/to/404.html",
      "500" : "/path/to/500.html",
      "default" : "/path/to/default.html"

You can set error pages via the server set command like this:

server set web.aliases.404=/missing.htm

Custom tray menu items

You can customize these tray menus and add your own option for your convenience.  To add a menu contribution to an individual server, add the following to your server.json:

      "url":"http://${Setting: not found}:${Setting: runwar.port not found}/foobar.cfm",

Tray menu makeover

We've updated to a new library that creates the tray icon for your running servers and the menu that appears when you right click.  In addition to better support for some Linux distros, we've added some nice new icons to the menus.

Pre/Post package scripts

Before any package script is run, CommandBox will look for another package script with the same name, but prefixed with pre. After any package script is run, CommandBox will look for another package script with the same name, but prefixed with Post. So if you have a package that contains 3 package scripts: foo, preFoo, and postFoo, they will run in this order.

  1. preFoo
  2. foo
  3. postFoo

This works for built-in package script names as well as as doc package scripts. It also works on any level. In the example above, if you created a 4th package script called prePreFoo, it would run prior to preFoo.

Better ForgeBox Login management

If you use more than one ForgeBox login, perhaps a personal one and a company one, it can be a pain to keep logging in.  It's also hard to remember the last user you logged in with.  We've introduced two new commands to help with this.  Run this to tell you who you are logged in as:

forgebox whoami

Run this to switch between users that you've previously logged in with:

forgebox use myUser

onRelease interceptor/package script

We've added a new "onRelease" interceptor and package script to help with the workflow of publishing packages.  Here's a run down of the three key points when bumping a package version.

  • preVersion - Announced before the new version is set using the bump command
  • postVersion - Announced after the new version using the bump command but before the Git repo is tagged.
  • onRelease - Announced after a new version is set using the bump command and after the Git repo is tagged.

Here is a typical package script work flow for working with a package that's hosted on GitHub and published to ForgeBox:

  "preVersion":"testbox run",
  "postVersion":"package set location='gituser/repov#`package version`'",
  "postPublish":"!git push --follow-tags"

Then when you want to publish a new version of your package, commit your changes to Git and run the following commands:

bump --minor

Those two commands, in combination with your package scripts, would accomplish the following:

  1. Run the package's test suite (a failure will abort the process)
  2. Increase the minor version of the page
  3. Tag the Git repo
  4. Change the package's location property in box.json to point to the new tag
  5. Commit the tag and new box.json
  6. Publish the package to ForgeBox
  7. Push the new box.json and Git tag

onInstall interceptor/package script

Announced while a package is being installed, after the package endpoint and installation directory has been resolved but before the actual installation occurs. This allows you to override things like the installation directory based on package type. Any values updated in the interceptData struct will override what the install command uses.

CLI Engine Update

The Lucee version that the CLI runs on has been updated to be which is also now the default engine to be used when you use the "server start" command and don't specify a cfengine.  If you still want to start a web server on Lucee, then simply to this:

start cfengine=lucee@4.5.2+018

Release Notes

There are tons of little bug fixes in this version that you can view in our release notes.  


  • [COMMANDBOX-187] - error when updating forgebox when slugname changes
  • [COMMANDBOX-422] - Empty command CFCs with no functions throw an error starting box
  • [COMMANDBOX-423] - Error "key [FUNCTIONS] doesn't exist" thrown when trying to start command box
  • [COMMANDBOX-426] - server name completion errors on server open command
  • [COMMANDBOX-434] - Document the resolvePath() differing behaviour on OSX vs Windows
  • [COMMANDBOX-435] - artifacts clean fails on OSX when there's .DS_Store files
  • [COMMANDBOX-437] - appSkeleton in the coldbox create app wizard needs to comply to IDs instead of local disk
  • [COMMANDBOX-449] - "server open" always opens localhost
  • [COMMANDBOX-451] - The trayicon in server.json does not work with relative paths
  • [COMMANDBOX-464] - update command doesn't respect original install path
  • [COMMANDBOX-465] - custom url rewrite location doesn't respect starting server by name in different location
  • [COMMANDBOX-466] - coldbox create crud doesn't work on Windows

New Feature

  • [COMMANDBOX-316] - Add Fusion Reactor support for server
  • [COMMANDBOX-399] - Starting server in web root with WEB-INF treats CWD as war
  • [COMMANDBOX-416] - Add "open" flag to touch/new command.
  • [COMMANDBOX-430] - forgebox whoami command to show what user your API key is set to
  • [COMMANDBOX-431] - Update the storage of the APIkey in the commandbox settings to include multiple keys
  • [COMMANDBOX-432] - Have a forgebox use {username} command to switch the current api key
  • [COMMANDBOX-445] - Allow aliases (virtual directory) in web server
  • [COMMANDBOX-458] - Provide custom 40x and 50x error pages for servers


CommandBox, News, Releases 0

New Adobe and Lucee CF Engines available for CommandBox

Brad Wood
Sep 29, 2016


We've updated to have updated CF Engines for Adobe ColdFusion as well as Lucee Server to include some recent security fixes from each as well as some new yet-to-be-released Lucee features.

Here are the new Adobe ColdFusion versions:

  • ColdFusion 11 Update 21 (10.0.21+300068)
  • ColdFusion 11 Update 10 (11.0.10+300066)

Here are the new Lucee Server versions

  • Lucee 4.5 Stable (4.5.3+020)
  • Lucee 5.0 Stable (5.0.0+254)
  • Lucee 5.0 Snapshot (5.0.1-snapshot+067)
  • Lucee 5.1 Beta 2 (5.1.0-beta.2+031)
ColdFusion, CommandBox, News 0

Ortus Developer Week 2016 - Hey you developer, What do you want to learn?

Jorge Reyes
Aug 24, 2016


Ortus Developer Week
November 14-18, 2016

5 days, 20 Live Sessions

A FREE Training Extravaganza


ODW version 5.0

Ortus Developer Week is taking place for the 5th year in a row! A FREE Training week dedicated to all of you developers that are eager to learn more and update your skills. Register and join 300+ developers taking part of this great event.



What do you wish to learn?

The FREE training is meant for you. So we invite you to suggest the topics you would like to learn more of! Rules are simple:
  • Suggest as many topics as you like.
  • Topics must be about web development technologies, ideas and processes.
  • ColdFusion CFML is the server-side language of choice
  • We'll choose topics based on relevance and popularity, and of course, speakers availability.
We encourage you not to miss this opportunity to propose your own schedule



Be a Speaker!

There are only a few things more gratifying than to contribute to the learning of others. Join the Ortus Team in this great opportunity and register as a speaker. 100% Satisfaction Guaranteed.



Ortus Joins Patreon, Help Sponsor Open Source

Luis Majano
Aug 22, 2016


We are excited to announce we have joined !

Sponsor Us

At Ortus Solutions we are known for building open source projects for the ColdFusion (CFML) community such as ColdBox, CommandBox, ContentBox Modular CMS, ForgeBox and many more. All of those products are licensed under the Apache 2 license and are completely FREE to use and extend.


However, the amount of effort needed to maintain and develop new features for all projects is not sustainable without proper financial backing. This is where you can come in and help support Ortus Open Source Software by pledging on Patreon. We have listed a bunch of options for you to sponsor Ortus Open Source Projects with lots of rewards like getting awesome recognition and some great discounts, swag and t-shirts. By pledging as little as $10 a month, you can contribute to this great cause and allow Ortus Open Source to have faster and ongoing development cycles. Pledge more and you can even be part of our product roadmap planning sessions.


If you run a business and are using Ortus Open Source software in a revenue generating product or service, it makes sense to sponsor Ortus Open Source Software development: it ensures the project that your product/services use stays healthy and actively maintained. If you are an individual user and have enjoyed the productivity of our Open Source Software tools, consider donating as a sign of appreciation :).

Sponsor Us

CacheBox, CFCouchbase, ColdBox MVC, ColdFusion, CommandBox, Community, ContentBox CMS, Elixir, ForgeBox, LogBox, News, Relax, WireBox 0

CBCMS2016 - Building your Own Admin Modules - Part 4 - Extending ContentBox 3

Gavin Pickin
Aug 11, 2016


Ready for part 4? Yes, part 4. We continue our small walkthrough of building your own Admin Module in ContentBox 3. The last few blog posts we learned the minimum requirements for a new module, to be controlled from inside of ContentBox. Then we learned how to add a handler and a view, and how to access the module from the front end entry point, and through the ContentBox admin entrypoint. In the last blog post in this mini series, we looked at adding a Submenu for your module, to an existing top level Menu item inside of the ContentBox admin. This blog post is going to show you how to add your very own top level Menu item, give it an icon, set permissions, and then add Submenu items to access your module.

ContentBox CMS, Modules, RoadShow, Walkthroughs 0

CBCMS2016 - Building your Own Admin Modules - Part 3 - Extending ContentBox 3

Gavin Pickin
Aug 09, 2016


In previous posts, we learned how to create a module inside of ContentBox, and then we added a handler and view so we could view the module behind the security of the login, but having an admin module, without menu items, is fairly silly ( usually ). In this blog post, we'll learn how you can add Submenu items to existing menus, like the Modules Main Menu.

ContentBox CMS, Modules, RoadShow, Walkthroughs 0

CBCMS2016 - ContentBox ColdFusion CMS Roadshow 2016 - Links to Recordings, Posts and Closing Remarks

Jorge Reyes
Aug 09, 2016


We definitely had fun sharing the latest features of our new ContentBox 3.0 modular CMS. We hope you boys and girls enjoyed it and are falling even more in love with our Open Source CMS and how it can get your projects done and out the door in not time.

For those of you who want to revisit the content from the Roadshow we have included the link to the webinars, recordings, blog posts and our dedicated ContentBox 3 Roadshow event page. Thanks to all roadshow attendees, presenters, bloggers, ContentBox CMS Open Source Project contributors, and our beloved sponsor Ortus Solutions. Although the roadshow is over, ContentBox 3 has so many great features, we'll be still be releasing blog posts, so keep checking the Ortus Blog for regular content.


Open Source Project

2,602 Commits | 25 Releases | 20 Contributors

You can be part of it!

You can very easily start contributing to ContentBox CMS. Visit our open source project in GitHub and go through our easy-to-follow guidelines. You'll be contributing in no-time. Let's make great software together!


Our event page can be found here:

Webinars Recordings

Blog Posts

Upcoming Events

CFSummit Training
Las Vegas | October 8-9


CFCAMP Training
Munich | October 17-19


Ortus Developer Week
FREE-Online Training | November 14-18


ColdBox MVC, ColdFusion, Community 0

Content Box Theme Development: Creating a CI Pipeline

Jon Clausen
Aug 05, 2016


An incredibly powerful feature of ContentBox 3 is the increasing availability of open source themes to jump start your custom development.   For those wishing to contribute back to the community, creating your own theme is as simple as cloning one of our boilerplate themes, creating a new GitHub repo for your customizations, and publishing your theme on Forgebox.  

ContentBox CMS, TestBox, Tutorials 0

ContentBox 3.0.0 is Released - The wait is over

Gavin Pickin
Aug 02, 2016


We are happy to announce, ContentBox 3.0 FINAL is now available to the public. After a lot of hard work, we are finally ready to cut the release. With 100+ issues included in this release, this major release is nothing short of massive. With ColdBox 4 updates, Theme updates, Enterprise updates, Security Updates, JSON Support and Exports, Native Markdown Support, Autosave and much more, this major release has something for everyone. ContentBox 3.1.0 is already in development as well and can be installed via CommandBox using the contentbox@be Identifier.

Alongside the release we have many other announcements around the CMS. So get ready!

ContentBox CMS, Releases 0
1 2 3 4 5 6 ... 105 >>