Well another two weeks go by and work keeps piling up. However, there where several steps forwards with ColdBox this past two weeks. I have been toying with the new website concept and have spent most of my time back in Fireworks and Art Director's Toolkit. Ahh the world of design, how hard are thee!! Anyways, there are several things to report and how progress continues. Also, Compatibility Guide for 2.1.0I have started a Compatibility Guide for ColdBox version 2.1.0. You will find here as work progresses, all the things you need to watch out for when moving to the next release. You will find only compatibility issues in this guide, so updating will be super easy. Guide Updates The majority of the Trac guides and content have been revised and updated. There are still some left that contain old information, but most of them have been revised and will continue to be. Unit Testing I have started to create an entire unit test suite for the entire framework and its capabilities and let me tell you, I should have done this a loooong time ago. It has just solidified the entire code base and you will be able to do test runs on bleeding edge downloads. Tracer in Logger Plugin now persists values http://ortus.svnrepository.com/coldbox/trac.cgi/ticket/245#comment:1 The tracer method in the logger plugin was not persisting the values across requests, so tracing to the debugging panel was kind of on display only. Now, it persists across any number of requests until it gets rendered in the debugging panel. A great tool now!! Session & client storage plugins updated Syntax and code enhancement updates. Custom Bug Report - Users can define the bug report to email out. http://ortus.svnrepository.com/coldbox/trac.cgi/ticket/186#comment:6 You can now declare a template that will serve as your bug report right in your configuration file. It uses the same syntax and style as your custom error template. So now, you have control of what you send in bug reports. Hurray!! New services: handlerservice and pluginservice Due to the new architectures coming and event caching, two new services have been created and the pluginservice is already rocking!! Miscellaneous Multiple syntax and code enhancements have also taken place in several locations, old code has been removed, etc. The look and feel of the debugger panel has been updated and the cache panel also. Anyways, this concludes the report and see you in two weeks for another report.
Blog
Recent Entries
Coming Soon: Version 4 Docker CommandBox Images with Enhanced Performance
CommandBox Docker images were the first CFML docker images and have nearly 2 million pulls, since their inception, to date. It's been a source of pride at Ortus that these images have been the most popular and reliable way to run CFML in containers and we are so very pleased to announce the next evolution, which will be the v4 images which run entirely on the BoxLang CLI and represent a significant overhaul of the image architecture.
These images are now available to test by appending -snapshot to your existing version tags and wil be released as stable, once CommandBox v6 emerges from release candidate status and is published as stable.
Free observability with BxMCP: give your AI agents eyes inside a live BoxLang runtime
Ortus Solutions today announces that bx-mcp, the Model Context Protocol (MCP) server for BoxLang, is now free for everyone. Install it, point any MCP capable client at it, and your AI coding assistant, IDE agent or automation pipeline can inspect and operate a live BoxLang runtime: JVM, caches, datasources, slow requests, schedulers, logs and more. No BoxLang+ subscription required.
Inherited a CFML Application With Few Tests? Here’s Where to Start!
You need to change an application that has been running for years.
It might be a ColdFusion customer portal, a Lucee application supporting internal operations, or a CFML system your team is preparing to modernize. People depend on it, but some of its behavior lives in old tickets, scattered documentation, and the memory of whoever has supported it longest.
Now a release is approaching. You know more testing would help. The difficult part is deciding where to begin without putting every other priority on hold.
Start with one important workflow and build evidence around what it needs to do.
Add Your Comment