I think the TracyDebugger module auto detects .dev domains. Can you also make it detect .test domains?

I'm moving my development sites to use .test instead of .dev because of https://ma.ttias.be/chrome-force-dev-domains-https-via-preloaded-hsts/

Hello again)

After upgrading to 1.9.4, debugger has crashes if template contain exit code.

Console tells: ReferenceError: ace is not defined function getTracyTemplatePath() {

And when exit code remved: : NetworkError: A network error occurred.

P.S. Syntax highlighting is great!

Hi Adrian,

After installing the latest version, I'm seeing the following error

PHP Warning: count(): Parameter must be an array or an object that implements Countable in .../site/modules/TracyDebugger/TracyDebugger.module:1123

ErrorException: count(): Parameter must be an array or an object that implements Countable in /Users/glenn/websites/mysite/wwwroot/site/assets/cache/FileCompiler/site/modules/TracyDebugger/panels/ProcesswireInfoPanel.php:198
Stack trace:
#0 /Users/glenn/websites/mysite/wwwroot/site/assets/cache/FileCompiler/site/modules/TracyDebugger/panels/ProcesswireInfoPanel.php(198): Tracy\Bar->Tracy\{closure}(2, 'count(): Parame...', '/Users/glenn/we...', 198, Array)
#1 /Users/glenn/websites/mysite/wwwroot/site/assets/cache/FileCompiler/site/modules/TracyDebugger/tracy-master/src/Tracy/Bar.php(159): ProcesswireInfoPanel->getPanel()
#2 /Users/glenn/websites/mysite/wwwroot/site/assets/cache/FileCompiler/site/modules/TracyDebugger/tracy-master/src/Tracy/Bar.php(108): Tracy\Bar->renderPanels()
#3 /Users/glenn/websites/mysite/wwwroot/site/assets/cache/FileCompiler/site/modules/TracyDebugger/tracy-master/src/Tracy/Debugger.php(272): Tracy\Bar->render()
#4 [internal function]: Tracy\Debugger::shutdownHandler()
#5 {main}

and on another site the same

ErrorException: count(): Parameter must be an array or an object that implements Countable in /Users/glenn/websites/othersite/wwwroot/site/assets/cache/FileCompiler/site/modules/TracyDebugger/panels/ProcesswireInfoPanel.php:198
Stack trace:
#0 /Users/glenn/websites/othersite/wwwroot/site/assets/cache/FileCompiler/site/modules/TracyDebugger/panels/ProcesswireInfoPanel.php(198): Tracy\Bar->Tracy\{closure}(2, 'count(): Parame...', '/Users/glenn/we...', 198, Array)
#1 /Users/glenn/websites/othersite/wwwroot/site/assets/cache/FileCompiler/site/modules/TracyDebugger/tracy-master/src/Tracy/Bar.php(159): ProcesswireInfoPanel->getPanel()
#2 /Users/glenn/websites/othersite/wwwroot/site/assets/cache/FileCompiler/site/modules/TracyDebugger/tracy-master/src/Tracy/Bar.php(108): Tracy\Bar->renderPanels()
#3 /Users/glenn/websites/othersite/wwwroot/site/assets/cache/FileCompiler/site/modules/TracyDebugger/tracy-master/src/Tracy/Debugger.php(272): Tracy\Bar->render()
#4 [internal function]: Tracy\Debugger::shutdownHandler()
#5 {main}

I'm running Apache/2.4.28 (Unix) PHP/7.2.0beta3

When I visit the modules page, I also see the following errors:

1x | PHP Warning: count(): Parameter must be an array or an object that implements Countable in .../Inputfield/InputfieldFile/InputfieldFile.module:637
--
1× | PHP Warning: count(): Parameter must be an array or an object that implements Countable in .../Inputfield/InputfieldFile/InputfieldFile.module:229

After v4.20.17, all new releases making website loading slowest (admin and frontend). v4.20.17 working normal.

Checked versions

• 4.21.0
• 4.21.1
• 4.21.2
• 4.21.3
• 4.21.4

System

• Macos Mojave
• PHP 7.4.5 (with https://github.com/laravel/valet)
• mariadb 15.1

One of the few things that I really missed from AdminOnSteroids - so I built a tracy panel instead :) I mean AOS has many great features but only a few that I really need for my daily work. This is one of them.

Having your module installed and executing something from the command line using wireshell there is no $_SERVER['REQUEST_URI‘] defined which leads to some PHP notices:

PHP Notice:  Undefined index: REQUEST_URI in /../site/assets/cache/FileCompiler/site/modules/TracyDebugger/TracyDebugger.module on line 207

Notice: Undefined index: REQUEST_URI in /../site/assets/cache/FileCompiler/site/modules/TracyDebugger/TracyDebugger.module on line 207
PHP Notice:  Undefined index: REQUEST_URI in /../site/assets/cache/FileCompiler/site/modules/TracyDebugger/TracyDebugger.module on line 211

Notice: Undefined index: REQUEST_URI in /../site/assets/cache/FileCompiler/site/modules/TracyDebugger/TracyDebugger.module on line 211
PHP Notice:  Undefined index: REQUEST_URI in /../site/assets/cache/FileCompiler/site/modules/TracyDebugger/TracyDebugger.module on line 844

Notice: Undefined index: REQUEST_URI in /../site/assets/cache/FileCompiler/site/modules/TracyDebugger/TracyDebugger.module on line 844
PHP Notice:  Undefined index: REQUEST_URI in /../site/assets/cache/FileCompiler/site/modules/TracyDebugger/TracyDebugger.module on line 844

Notice: Undefined index: REQUEST_URI in /../site/assets/cache/FileCompiler/site/modules/TracyDebugger/TracyDebugger.module on line 844

It would be great if you could implement a check before accessing $_SERVER['REQUEST_URI‘].

Hi, Adrian! This popped up during module development. Don't know why Tinycon si undefined. Maybe just checking if Tinycon is defined before doing anything with it would be enough.

Hey @adrianbj

As you already know I'm using the logs panel for showing information about triggered migrations from RockMigrations. The problem with the current implementation of the logs panel is that this messes with the exact execution order of my migration logs because there are always many entries within one second. I've done some research and tried different approaches (like adding the line number to the timestamp and sorting afterwards), but the best option seems to be to simply introduce a setting that enables me to disable the sort on this line: https://github.com/adrianbj/TracyDebugger/blob/c024f995dfa8be5e5238dc87995afd49da1ca642/panels/ProcesswireLogsPanel.php#L84

When disabled, I get a clean log with all my rockmigration logs in place an in correct order:

I'm totally fine with not having a GUI for this setting as I think nobody else will ever need this...

Thx in advance!

Hello, I'm testing PW3 now, and found some buggy behavior with get request to dump panel or logger. For example:

$page->get("FIELD_PAGE_ARRAY_NAME");

With Tracy Debugger 1.8* such requests runs to 500 Server error. But after upgrade to 1.9.0 the request gets a recursion from array item _wire protected => ProcessWire\ProcessWire.

Works well in PW2.7.*

MacOS 10.14.3 PHP 7.2.15 nginx/1.15.8 (via Laravel Valet) Tracy 2.6.1 Tracy Debugger 4.18.6

Error stack

Fatal Error: Uncaught TypeError: explode() expects parameter 2 to be string, boolean given in /Users/rudy/Sites/profile1/public/site/modules/TracyDebugger/tracy-2.6.x/src/Tracy/Bar/assets/loader.phtml:16
Stack trace:
#0 /Users/rudy/Sites/profile1/public/site/modules/TracyDebugger/tracy-2.6.x/src/Tracy/Bar/assets/loader.phtml(16): explode('?', false)
#1 /Users/rudy/Sites/profile1/public/site/modules/TracyDebugger/tracy-2.6.x/src/Tracy/Bar/Bar.php(113): require('/Users/rudy/Sit...')
#2 /Users/rudy/Sites/profile1/public/site/modules/TracyDebugger/tracy-2.6.x/src/Tracy/Debugger/Debugger.php(330): Tracy\Bar->render()
#3 [internal function]: Tracy\Debugger::exceptionHandler(Object(TypeError))
#4 {main}
thrown (line 16 of /Users/rudy/Sites/profile1/public/site/modules/TracyDebugger/tracy-2.6.x/src/Tracy/Bar/assets/loader.phtml) 

This error message was shown because: you are logged in as a Superuser. Administrator has been notified. Error has been logged.

Hey @adrianbj. I've just tried out the 4.23 update, and ran into an issue: the module no longer displays AJAX requests on the live server.

Tracy docs mention that Tracy now uses "temporary files" for storing data, and I'm suspecting that this is the issue: in this case server is load balanced, and most directories are not shared among instances, and PHP / Apache user has very limited write access to files.

Do you know where Tracy stores these files? Is it cache directory specific to ProcessWire, or something else? If I knew where those files are going, and/or could somehow configure their path myself, I might be able to further debug and perhaps bypass the issue.

If that's not possible, Tracy announcement post also mentioned that sessions can still be used. Is there a possibility to add this as an option?

For the time being I'm going to restore TD 4.22.

Hi,

When working on a module, I noticed that even though I disabled the template in the No debug bar in selected frontend templates, some markup was added right before </body>.

This is due to the line 1092. Best would be to check if the template is not in the list of excluded ones and return before any additions are made.

Let me know if you need more infos.

@adrianbj I noticed exceptions getting thrown unexpectedly here and eventually tracked it down to a hook added in TracyDebugger.module.php:

// override default PW core behavior that converts exceptions to string
$this->wire()->addHookAfter('Wire::trackException', function($event) {
	$exception = $event->arguments(0);
	if($this->wire('config')->ajax && ($exception instanceof WireException || $exception instanceof \ProcessWire\WireException)) {
		// intentionally blank
	}
	else {
		throw $exception;
	}
});

PW is only supposed to throw the given Exception (arg0) from the trackException() method if the $severe argument (arg1) is true and $config->allowExceptions === true;. I think the hook above shouldn't throw the exception because it would have been already thrown in the trackException() method if it was supposed to be (since this is an after hook).

The issue is that PW calls the trackException() method sometimes for non-fatal errors ($severe===false) and it is hookable so that anything else can log or report the error for additional debugging info. If the $config->allowExceptions is true, then the exception is considered fatal only if the $severe argument is also true... in which case it throws the exception. But if the $severe argument is false, then PW expects to be able to continue its business and fix whatever caused the exception. So when TD comes in and throws an exception when it shouldn't be, it potentially bypasses code that is meant to resolve a non-fatal exception.

Not sure why Tracy would affect a Select Options field in this way, but I've noticed that I get a warning about deleting options when I am adding options to a new Select Options field that does not yet have any options.

Screencast:

When Tracy is disabled I don't get this notice when adding options.