FORGEBOX v5.1.0 Released

Cloud, CommandBox, ForgeBox, Lucee, Lucee Extensions, Modules, Releases

Luis Majano June 01, 2020

Spread the word

Luis Majano

June 01, 2020

Spread the word

Share your thoughts

Modernize all things!

FORGEBOX v5.1.0 released!

See Plans

Today we are pleased to announce a minor release for our FORGEBOX suite of products to version 5.1.0. It has tons of updates and nice features for all plans. Enjoy!

Release Notes

Bugs

[FORGEBOX-180] - Last updated date is incorrect in versions listing
[FORGEBOX-290] - When a collaborator publishes a new version to a package, the package disappears
[FORGEBOX-364] - Hamburger not working on mobile anymore
[FORGEBOX-413] - Forgebox Project Badges: should set "Cache-Control: no-cache", otherwise Github caches agressively
[FORGEBOX-476] - Versions tab doesn't always open when loading page with many versions
[FORGEBOX-520] - Assign user subscription to community plan when registering a new user
[FORGEBOX-524] - Make sure on all ajax calls on the collaborators, that you show error messages
[FORGEBOX-427] - Handle non-successful API calls from the collab screen.

New Features

[FORGEBOX-215] - UI update for registration page
[FORGEBOX-354] - Create the ForgeBox support/contact page
[FORGEBOX-500] - Implement plan custom fields UI
[FORGEBOX-517] - Account for a user having a paid plan that was comped
[FORGEBOX-521] - Overhaul dependencies tab
[FORGEBOX-522] - New Versions Vue Component
[FORGEBOX-526] - Add a forgebox plan mini report on admin dashboard
[FORGEBOX-523] - Secure the collaborations tab in edit mode for forgebox plans

Improvements

[FORGEBOX-525] - Revise that all formats should be markdown by default when in edit mode for a package
[FORGEBOX-408] - Improve collaborator package UI
[FORGEBOX-410] - Send notification to user when an admin removes you as a collaborator
[FORGEBOX-411] - Send notification to admins/owners when collaborator leaves the collaboration
[FORGEBOX-428] - If package is unpublished make sure you can't add collaborators
[FORGEBOX-442] - Include username in account activation E-mail
[FORGEBOX-477] - Add pagination to versions tab
[FORGEBOX-478] - Add ability to filter out unstable builds on version tab
[FORGEBOX-489] - Add rel="noopener" to forgebox external urls
[FORGEBOX-518] - Allow users to link to specific headers in a package description
[FORGEBOX-527] - Add Environment name in the subject emails when not in production mode

Introducing the BoxLang Spring Boot Starter: Dynamic JVM Templating for Spring

Spring Boot developers know the pain of evaluating view technologies. Thymeleaf is great — until you need more expressiveness. FreeMarker is powerful — until the syntax fights you. What if you could write templates in a dynamic JVM language that gives you the full power of the platform, feels natural, and requires zero setup to integrate?

Meet the BoxLang Spring Boot Starter.

Why Swiss Banks Are Modernizing CFML Platforms Without Rewrites

The growing need to evolve legacy financial platforms safely

Many Swiss banks and financial institutions still operate important systems built on ColdFusion and CFML platforms.

These systems manage a wide range of functions, including:

internal banking workflows
reporting systems
client portals
data integration platforms
compliance and risk management tools

In many cases, thes...

Reactive vs Proactive ColdFusion Support: Why Waiting for an Outage Is the Most Expensive Strategy

Many ColdFusion environments operate in a reactive mode without realizing it.

Everything seems fine… until something breaks.

A server crashes.

Performance drops suddenly.

An integration stops working.

A security audit reveals missing patches.

At that point the response is urgent:

“Can someone help us fix this now?”

Emergency support is sometimes unavoidable. But when reactive intervention becomes the norm, it usually means something deep...

Blog