Project

General

Profile

Actions

Feature #78038

closed

debug function with new comfort setting debugInWindow

Added by Peter Enzenberger about 8 years ago. Updated about 6 years ago.

Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
-
Start date:
2016-09-22
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

Some extensions try to make the work with the debug-function a little bit easier.
For example imagine this situation:
In new layouts with bootstrap-features etc you will have a fixed header.
There is no chance to open a plus in the variable-values in
the first black debug-box behind this fixed header.

The debugUtility for some time still knows the debugInPopUpWindow().
But its heavy work to change a normal
debug(...)-call to something like
\TYPO3\CMS\Core\Utility\DebugUtility::debugInPopUpWindow(...)
Thats nothing you will do during development in a php-file ...

Perhaps we could have a switch somewhere
to open debug-output in a window?
Something like the following lines?
(see \typo3\sysext\core\Classes\Utility\DebugUtility.php around line 70)
Just replacing the (buggy) line
  1. echo self::renderDump($var);
  2. echo self::renderDump($var);
    echo self::renderDump($var, sprintf('%s (%s)', $header, $group));
    }
if ($GLOBALS['TYPO3_CONF_VARS']['SYS']['debugInWindow']) {
self::debugInPopUpWindow($var, sprintf('%s (%s)', $header, $group));
} else {

Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Task #78522: Remove backend user option debugInWindowClosedWouter Wolters2016-10-31

Actions
Actions #1

Updated by Christian Kuhn about 6 years ago

  • Status changed from New to Rejected

Hey. Thanks for this suggestion. However, the debugInWindow option has been removed in v8 already. see issue #78522

Actions #2

Updated by Christian Kuhn about 6 years ago

  • Related to Task #78522: Remove backend user option debugInWindow added
Actions

Also available in: Atom PDF