Blog

ColdBox: ColdFusion MX 6.X issues and support

Luis Majano October 15, 2008

Spread the word

Luis Majano

October 15, 2008

Spread the word


Share your thoughts

Support for ColdFusion 6.X will be on the next revision 1.0.3 plus other great features that you can check out here. 6.X has some issues that were shown into light by Aaron Conran. You can download the zip in this post that contains a new settings.cfc, XMLParser.cfc, and Application.cfm. Just replace them in your system folder and also use the Application.cfm as a template for your applications, including the samples gallery. Another drawback is that the Dashboard is only supported on CFMX 7.0 and above. If you can make it work for cfmx 6.X, then let me know. Issues with 6.X click on them to view them.

Add Your Comment

Recent Entries

Your Development Team Is at Capacity. Here’s How to Keep Critical Work Moving!

Your Development Team Is at Capacity. Here’s How to Keep Critical Work Moving!

The problem is not that your team lacks priorities.It is that maintenance, delivery, and long-term improvement are competing for the same people.

For companies running business-critical CFML, ColdFusion, or BoxLang applications, that pressure can be especially difficult to solve. Experienced developers are not always easy to hire quickly, application knowledge may be concentrated in one or two people, and a generalist may need significant context before taking ownership of the work. A permanent hire can also require a significant investment in recruiting, compensation, onboarding, and long-term capacity even when the immediate need is a specific project, urgent maintenance, or a period of transition.

Maria Jose Herrera
Maria Jose Herrera
September 18, 2026
Copy of BoxLang AI 3.4 Blog Series Part 5 : Reasoning Without the Guesswork

Copy of BoxLang AI 3.4 Blog Series Part 5 : Reasoning Without the Guesswork

Reasoning-capable models have been usable in BoxLang AI for a while. params passes straight through to the provider body, so params: { thinking: { type: "enabled", budget_tokens: 10000 } } for Claude, or params: { reasoning_effort: "high" } for OpenAI, already reached the API. What never worked was reading the reasoning back. It was parsed out on arrival and silently dropped. In 3.4.0, that's fixed, and it's fixed the same way for every provider.

Luis Majano
Luis Majano
September 15, 2026