Blog

Luis Majano

July 01, 2016

Spread the word


Share your thoughts

The new ContentBox 3 CMS editors have the capability to output dynamic settings and even tap in to the ColdBox MVC request context and private context collections. This will allow you to easily output from any of these sources using an easy to use markup.

Settings

Any setting stored in ContentBox can be output using the following markup: ${ setting_name }. This is a great way to create site-wide static settings that can be outputed in any editor.

ColdBox Request Collection

Since ContentBox CMS is built on a solid MVC foundation via ColdBox, you can easily tap into the request structures that power a request. The request collection or usually referred to as rc is available in any editor using the following markup: ${ rc:key_name }. This will allow you to have access to incoming URL and FORM parameters or internal application variables.

ColdBox Private Request Collection

The private request collection or usually referred to as prc is available in any editor using the following markup: ${ prc:key_name }. This will allow you to have access to private dynamic variables that can be set by the ColdBox application eco-system.


You now have more choices for integration with the ColdBox application eco-system. Have fun!

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