cflog doesn't write application name to log

Description

see the test case for https://luceeserver.atlassian.net/browse/LDEV-3264

`<cflog application="true" type="Information" text="blah blah">`

Environment

None

Activity

Show:

Pothys - MitrahSoft 9 March 2021 at 13:16

this issue was started regression by the ticket LDEV-3001. Before that, writelog logs an application name only when application=true So I added a fix to log application name in logs even attribute application is not set. I think this causes the regression. Now this works fine with fixed versions. So I mark this as deployed.

Zac Spitzer 8 March 2021 at 16:04

that may be true, but I think this regression was caused by the 5.3.8 logging changes

it did previously work, there was a whole series of builds after those changes which didn’t produce a snapshot, so it isn’t easy to work out what caused this regression

Michael Offner 8 March 2021 at 15:51

this is marked as a regression, but the “PR above does not revert any change made in the past, it changes the default value of an argument to a value it never had.

Pothys - MitrahSoft 8 February 2021 at 08:20

I've checked this ticket and confirmed the application name not rendered in the log with application=true. I added a fix for this ticket

Pull Request: https://github.com/lucee/Lucee/pull/1180

Fixed

Details

Assignee

Reporter

Priority

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

Affects versions

Created 7 February 2021 at 20:46
Updated 4 April 2021 at 14:21
Resolved 9 March 2021 at 13:16