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

Activity

Show:
Pothys - MitrahSoft
July 18, 2019, 1:51 PM

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

Michael Offner
September 6, 2019, 3:41 PM

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

Zac Spitzer
September 6, 2019, 4:03 PM

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

Zac Spitzer
September 6, 2019, 4:12 PM

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

Assignee

Michael Offner

Reporter

Zac Spitzer

Priority

New

Fix versions

None

Affects versions

Configure