Update Application.cfc

[richardherbert]

Added this.suppressRemoteComponentContent = false;

[lmajano]

I had never seen this setting before. @bdw429s do we support this in boxlang? Or does this affect CFML engines?

[richardherbert]

Jon Clausen mentioned it in a Slack reply to an issue I had.

I don't think it exists in Adobe ColdFusion and the only documentation I can find is https://docs.lucee.org/reference/tags/application.html#attribute-suppressremotecomponentcontent

It is used by ContentBox - https://github.com/Ortus-Solutions/ContentBox/blob/3c92c176f64a68353cbb2be7a08c3c51a122537e/Application.cfc#L52

[lmajano]

Can; you explain what this does for you, since I had no idea about it.

[richardherbert]

Yes, sorry, my commit message was a little terse!

For context I asked this question on Slack (https://cfml.slack.com/archives/C06TSRXCJ/p1733759628357719).

For me, after creating a fresh ColdBox application (coldbox create app) and browsing to the example test MainSpec.cfc I was getting a blank screen.

Jon asked "Do you have your server set to disable remote access to components?".

After checking the Lucee Admin I found that Settings > Output > Suppress Content for CFC Remoting was set to true. Changing that to false and then the test response was displayed as expected. Further research revealed that adding this.suppressRemoteComponentContent = false; to the /tests/Application.cfc had the same effect.

Looking at the ContentBox commit history for Application.cfc that has this setting, it appears that you added this setting (Ortus-Solutions/ContentBox@a094d37) back in 2014.