Today we released a patch for ContentBox Modular CMS v3.5.1 to address 1 critical bug fix and managed to squeeze some minor improvements along the way! So either do an automatic patch via the ContentBox admin, or issue a CommandBox `box update contentbox` and you will be patched. Enjoy!

As more people are starting to use CommandBox to start their Adobe ColdFusion and Lucee servers, I've gotten the question of where to find their log files.  The servers that CommandBox starts are full fledged servers with a web admin and all the same log files you'd expect.  However, CommandBox skips the vendor installer and uses the WAR files of each engine for a quick and lightweight deployment that can be deleted later and won't conflict with other servers, no matter how many you have.

This release we're focusing on feedback from ContentBox 3.x customers and the ability to containerize ContentBox. Building on top of the SEO updates in ContentBox 3.1.0, we're continuing to make ContentBox more SEO friendly, Search Engine Friendly and Social Media Friendly. This update has a tremendous amount of updates and bug fixes for your current installations. So let's start investigating all the major areas of improvement:

No doubt you're familiar with one of the buzzwords of the moment: "microservices". Or you are familiar with the word at least, if not in practice. If you've been doing CFML development since the before Adobe bought out Macromedia, possibly even before Macromedia bought out Allaire, you've no doubt slogged through your share of procedural, template-based CFML. Then You know just the app(s!) I'm talking about...