Here's an oldie but goodie, I've got a ModelGlue app running on Lucee 5.3.8.206. I cannot get dumps, or really any output to show in components to save my life. It's slowing down development a lot. Things I've tried: 1. Setting output="true" at component and function levels. 2. Turning debug on in ModelGlue 3. Using

this.bufferOutput = true

in the application.cfc. 4. Using output="browser" in the dump call 5. Hacking the dump.cfc My guess is that MG is suppressing any output in components somewhere, but nothing is jumping out at me.

I know zero about ModelGlue but in a similar situation where the dump was mixed in with existing output what we have done is add <cfcontent reset=true> prior to <cfdump var="#cfcatch#" abort=true> Hope that helps somewhat...

I'll try that.

The trick of dumping the content and then flushing (which the cfcontent reset should do) and aborting should always work, but barring that, you can write to the system output, or a log… and best is having stuff under test (where you can use the requestdump stuff if needed)

It should work, but it doesn't. I've spent too many hours trying to make it work, so I'm back to dumping HTML to a file to review.

It rings a vague bell, due to how the MVC works in MG, but I'm a big fan of tests (for code) so did more tests than dumps as it were, and don't remember the workarounds needed to dump

Unfortunately, client won't pay for tests. I know, I know. But it is what it is.

Yeah, that is an especially tough call when you are spending more time in total working around not having tests than you would in total with tests! Even then, for some clients it is more the principal, than the time or money… tho when that's the case it's usually more middle-management (that knows code and says "why add test?"), than the bosses (who don't know code).