Actions
Bug #73193
closedvar_dump output not visible in backend modules
Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2016-02-09
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
7
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:
Description
I'm using var_dump()
during development of backend modules.
Unfortunately, the module-docheader
div is positioned fixed
and overlays the debug output, making the first lines of it invisible - see the attached screenshot; the first two dumped strings are not visible.
Please make it possible to use var_dump()
during backend development.
Files
Updated by Andreas Kienast almost 9 years ago
- Status changed from New to Needs Feedback
Why don't you use \TYPO3\CMS\Extbase\Utility\DebuggerUtility::var_dump()
instead?
Updated by Christian Weiske almost 9 years ago
because writing var_dump()
is so much shorter than writing \TYPO3\CMS\Extbase\Utility\DebuggerUtility::var_dump()
.
Updated by Andreas Kienast almost 9 years ago
- Status changed from Needs Feedback to Rejected
This is IMO no good reason to change the behavior of the TYPO3 core. A decent IDE autocompletes already at "DebuggerUt".
Actions