Puzzler for y’all: I’m trying to reproduce an erro...
# lucee
f
Puzzler for y’all: I’m trying to reproduce an error which has this in the output
<td valign="top" bgcolor="#ff9900" style="border : 1px solid #000000;empty-cells:show;
which I am finding is lucee’s
HTMLDumpWriter
. You would expect to see this in the result of a
cfdump
right?, but you’ll see that lucee cfdump output doesn’t have inline style attributes, it has a style tag and uses classes like
luceeH1
which appears to come from the Dump.cfc custom tag bundled with lucee: https://github.com/lucee/Lucee/blob/6.0/core/src/main/java/resource/library/tag/Dump.cfc#L616
So my question is, in what circumstances does the HTMLDumpWriter get used? here’s how I know the markup came from it: https://github.com/lucee/Lucee/blob/6.0/core/src/main/java/lucee/runtime/dump/HTMLDumpWriter.java#L123-L124
It looks like the Dump function in lucee defined here: https://github.com/lucee/Lucee/blob/6.0/core/src/main/java/lucee/runtime/functions/other/Dump.java would use HTMLDumpWriter, but it doesn’t it uses Dump.cfc
I tried all the format options of cfdump as well, all appear to use dump.cfc
a
Could it be a call to cfdump as a function where the result is assigned back to a variable ?
e
Yes, what @alexpixl8 said. Or perhaps wrapped inside a cfsavecontent?
a
There is a concept of cfdump templates
so if the html dump template is being used that will use that,
now for how you invoke that
format= html ?
f
yeah, I tried the dump function and with format=html (and all format options), but it still outputs using Dump.cfc’s markup, with the luceeH1 classes, etc: https://trycf.com/gist/9db4f296923694820017164972afe25b/lucee5?theme=monokai
Also tried to call to cfdump as a function where the result is assigned back to a variable, if I try
y = dump(var=x, format="html");
then
y
is not defined because dump is void, I don’t see an argument that writes the result back to a var. I did try cfsavecontent as shown in the trycf gist above, still no dice.
all good ideas, thanks for the input
Figured this out… it was caused by a timeout in a cfquery. This bug causes the stack trace to be output, it ignores what you have as the Lucee Error Handler in Lucee Admin, more details in my comment here: https://luceeserver.atlassian.net/browse/LDEV-4311 really odd one, but hopefully the info I added allows the lucee team to reproduce it now
image.png