Issues
2 of 2
CFSilent is not default bufferoutput=true and missing abort triger documentation
Fixed
Description
Environment
None
Details
Assignee
Pothys - MitrahSoftPothys - MitrahSoftReporter
GuardianGuardianPriority
CriticalLabels
Fix versions
New Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Sprint
NoneAffects versions
Details
Details
Assignee
Pothys - MitrahSoft
Pothys - MitrahSoftReporter
Guardian
GuardianPriority
Labels
Fix versions
New Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Sprint
None
Affects versions
Created 5 March 2020 at 08:27
Updated 21 July 2022 at 13:50
Resolved 20 July 2022 at 14:00
Activity
Show:
Zac Spitzer21 July 2022 at 13:50
Pothys - MitrahSoft21 July 2022 at 12:37
I added a testcase to cfsilent tag
Pull Request:
Pothys - MitrahSoft20 July 2022 at 13:59
I've checked this ticket with the Lucee latest build 6.0.0.202-SNAPSHOT. Now cfsilent bufferoutput attribute takes true as the default value.
Zac Spitzer17 July 2022 at 16:31
Zac Spitzer19 May 2021 at 10:38
I think the problem is when the tag is released, buffer output is set to null, but initially it’s set to true, so it works as advertised the first time, but subsequently it defaults to false
The documentation claims the CFSilent bufferoutput option is defaulting to true, but it isn't.
Also when bufferoutput=true, output written to the body is outputed also when abort is present, that is normal (ACF like), but not specified in docs.