Blog

ColdBox 5.2.0 Released!

Luis Majano October 18, 2018

Spread the word

Luis Majano

October 18, 2018

Spread the word


Share your thoughts

What's New With 5.2.0

ColdBox 5.2.0 is a minor version update with lots of fixes, improvements and some new features not only to the ColdBox core but to LogBox and WireBox standalone versions alike. Below are the major areas of improvement and the full release notes. To update your installations just issue the commands below with CommandBox:

  • update coldbox - Update ColdBox Platform
  • update logbox - Update standalone LogBox
  • update wirebox - Update standalone WireBox

ColdBox


The major areas of improvement for the ColdBox core where on tons of fixes, however there are some nice new features discussed below.

Bugs

  • [COLDBOX-597] - Function addAsset generate wrong link if asset path contains ".js"
  • [COLDBOX-668] - Make implicit views case sensitive by default for linux systems
  • [COLDBOX-677] - HTML HELPER - Fix a requirement for columnName if column is defined
  • [COLDBOX-696] - Passing headers to `request` breaks RoutingService when in test mode
  • [COLDBOX-724] - Add ENV overload in detectEnvironment() via ENVIRONMENT system setting/property
  • [COLDBOX-726] - setNextEvent does not exist in coldbox.system.web.Controller
  • [COLDBOX-727] - fail fast strong typed to boolean, update to allow custom closures/lambdas
  • [COLDBOX-729] - getRenderData\(\) in base test case was not looking at the right request collection
  • [COLDBOX-732] - Fail fast can't be turned off for original behavior of ColdBox 4
  • [COLDBOX-736] - Module mappings disappear when not unloading ColdBox in base test case
  • [COLDBOX-738] - Clear not working on string builders: Use setLength\(0\) since clear is not a method on StringBuilder
  • [COLDBOX-740] - When using group\(\)operations with a handler and no explicit handler routing call added, route never registered the handler

New Features

  • [COLDBOX-722] - New global directive: autoMapModels which if true, it will map all root models just like modules do.

This will allow root models to behave like modules where all models are registered automatically for you but with no namespace.

  • [COLDBOX-737] - toAction() terminator is missing from the new router DSL

This terminator was missing from the new Routing DSL. This will allow you to build up routes that terminate at an action.

  • [COLDBOX-720] - Register config/Router.cfc as an interceptor

The main application router and ALL module routers are now also interceptors.

Improvements

  • [COLDBOX-730] - Implicitly pass args from renderLayout() into the rendered views
  • [COLDBOX-739] - List modules which have already been processed when a module cannot be activated to help with debugging

LogBox


Bugs

  • [LOGBOX-29] - when using async option on FileAppender, nothing logs, well now it does!

New Features

  • [LOGBOX-31] - Add defaultValue arguments to getProperty() methods on abstract appenders

Improvements

  • [LOGBOX-30] - Leave off text "ExtraInfo: " from console appender if empty string

WireBox


Bugs

  • [WIREBOX-76] - Virtual inheritance not injecting generic getters and setters correctly on target objects
  • [WIREBOX-77] - Virtual inheritance not inheriting init from super class

Improvements

  • [WIREBOX-51] - Add method to binder to override alias of current mapping, by passing the current mapping to the influencer closure
  • [WIREBOX-75] - Don't exclude path in parent mapping destinations
  • [WIREBOX-78] - Simplify error message for missing dependency to be human readable

Add Your Comment

Recent Entries

Building Native CLI Apps with MatchBox & Native Fusion

Building Native CLI Apps with MatchBox & Native Fusion

MatchBox makes BoxLang practical for a classic deployment target: the single-file command-line application.

The MatchBox open beta is available at https://github.com/ortus-boxlang/matchbox.

With the MatchBox native target, you can compile a .bxs script into a standalone executable for macOS, Linux, or Windows. The generated binary includes the MatchBox VM core and your compiled BoxLang bytecode. It does not require a JVM, a separate MatchBox install, or any runtime on the target machine.

Jacob Beers
Jacob Beers
July 14, 2026