Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

admin.getLoggedDebugData doesn't include mapped paths

Description

when using archives via a mapping, admin.getLoggedDebugData() doesn't include any mapping information, so the debugging erroneously displays the paths from the archive as being under the root folder

this also affects normal mappings

 

Environment

None

Attachments

1
  • 06 Sept 2019, 04:03 pm

Activity

Show:

Zac Spitzer 6 September 2019 at 16:12

other normal mapped folders also get recorded as ../ so you loose all context unless you can guess which mapping it came from.

this is then compounded by the rather buggy group by filepath logic in the modern template, so unrelated files may be grouped together, potentially obscuring performance problems

Zac Spitzer 6 September 2019 at 16:03

no, they are related, it makes the debug logs confusing as these files are simply not in the root folder/mapping.

Michael Offner 6 September 2019 at 15:41

so far i did not dig into this ticket, agrees on statement?

Pothys - MitrahSoft 18 July 2019 at 13:51

I've checked this ticket and admin.getLoggedDebugData is unrelated to mapping. Because this will use for debugging-logs. So, it does not include any of the information for mapping-archive

Details

Assignee

Reporter

Priority

Labels

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 6 July 2019 at 13:39
Updated 20 December 2019 at 18:19

Flag notifications