adrian

Tracy Debugger

Recommended Posts

Another question: in the panel there is the button "toggle all", but nothing happens if i click on it. ???

Share this post


Link to post
Share on other sites
2 minutes ago, Juergen said:

Another question: in the panel there is the button "toggle all", but nothing happens if i click on it. ???

Another weird one :)

That's obviously all JS - what browser are you using? Any browser console errors reported?

Share this post


Link to post
Share on other sites

I am using the latest Firefox but I have also tested it with IE - same result. Browser console doesnt show any errors.

Share this post


Link to post
Share on other sites
6 minutes ago, Juergen said:

I am using the latest Firefox but I have also tested it with IE - same result. Browser console doesnt show any errors.

Do each of the files toggle correctly when you click on one separately?

I just tested on all my browsers and had no problems. I am wondering if maybe there is some JS on the frontend of your site that is conflicting. If you're not already, can you please test on the backend of the site?

Share this post


Link to post
Share on other sites

Other toggles from other panels work as expeceted. I am running Tracy in Backend at the moment, so no conflict with frontend scripts. Only to mention: My Antivir software from Kaspersky adds a JS-File inside the head section of the page. Maybe this could be a reason.

Share this post


Link to post
Share on other sites
1 minute ago, Juergen said:

Only to mention: My Antivir software from Kaspersky adds a JS-File inside the head section of the page. Maybe this could be a reason.

Maybe you could try disabling that for a test?

If that doesn't help, I might need you to debug that toggleHooks() function in CaptainHookPanel.php to see where it's failing.

Anyone else out there have any problems with the Toggle All button not working?

Share this post


Link to post
Share on other sites
9 minutes ago, Juergen said:

Other toggles from other panels work as expeceted.

Sorry I just noticed this - glad other panel's toggles are working, but it would help to know whether the individual toggles on the Captain Hook panel are working. It contains a list of all the files that have hooks. You should be able to click on each file and see a table of hooks within that file. We need to know that they're there because maybe that is the issue with the Toggle All - maybe there is nothing to show?

Share this post


Link to post
Share on other sites

I have a lot of hooks inside ready.php, which will be loaded with every page load - so there are a lot of :)

Share this post


Link to post
Share on other sites
1 minute ago, Juergen said:

I have a lot of hooks inside ready.php, which will be loaded with every page load - so there are a lot of :)

I wasn't suggesting that there shouldn't be anything to show, but rather maybe there is an issue with them not being populated. Actually maybe it is related to the $paths not defined issue you were having - maybe the Captain Hook cache is not properly populated. That's why I need to know if there is anything under each file, eg in this screenshot I have opened up the Field.php file. By the way, hooks you are calling in ready.php aren't relevant - Captain Hook shows hooks that are available in the core, not hooks that have been triggered - for that, take a look at the "Hooks Triggered" section in the Debug Mode panel - this can be very handy to test if you hook is working.

59f5ee3a1aad9_ScreenShot2017-10-29at8_04_52AM.png.eea19fdf32271e3b1cb933e4eabf5fc6.png

Share this post


Link to post
Share on other sites
Just now, Juergen said:

This is what my Hook panel looks at the moment:

screenshot-www.juergen-kern.at-2017-10-29-16-10-10.png.8f4c3fff54b6ac469a42d393394a7bd2.png

So there is no content at all.

Ok, so please delete the Captain Hook cache from the database caches table. That will trigger it to rescan all your files again. If that doesn't work, we'll need to go back to that $paths issue which I think might still be a problem - I get the feeling that maybe that $iter foreach loop has nothing to loop.

Share this post


Link to post
Share on other sites

Ok I have commented it out

if (!$dir->isDir() /*&& strpos($path, '/.')*/ === false && preg_match($fileNamePattern, $path) && !in_array(basename($path), $excludeFilenames) ) {

but no effect

Share this post


Link to post
Share on other sites

@Juergen - do you have a live somewhere that is showing this problem that you might be able to give me access to?

BTW, commenting out like that will mean result in a weird:

if(!$dir->isDir() === false) 

which isn't what we want. So try removing this in its entirety:

 && strpos($path, '/.') === false

Can you try putting: 

bd($path);

just inside the foreach loop - above the if()

You will need the Dumps Recorder panel for this - the main Dumps panel will miss it because the Captain Hook panel does it's scanning before the regular debug bar panels are loaded.

PS - You will need to clear that cache again - actually I forgot that a simple way to do that is a Modules > Refresh :)

Share this post


Link to post
Share on other sites
11 minutes ago, Juergen said:

I have sent you a PM.

Thanks - I have figured out the issue - it's to do with the path of your site, which starts with: /home/.sites/ which that strpos($path, '/.') === false is catching. I'll get a fix out shortly, although I have to leave in a few minutes, so it might be better if I don't rush and leave it till later today or tomorrow.

Thanks again for access to your site - we could have gone around in circles for hours otherwise :) 

  • Like 1

Share this post


Link to post
Share on other sites
16 minutes ago, Juergen said:

Thanks for your efforts. No need to hassle! ;)

No problem.

I have a solution in place on your site, but I need to test a little more before releasing, so I would appreciate it if you could keep my account active for a while still.

Take a look though - now you'll finally see what the Captain Hook panel is all about :)

  • Like 1

Share this post


Link to post
Share on other sites
7 hours ago, adrian said:

I have always found that clicking Toggle All and then CTRL/CMD+F to use the browser's "Find" functionality

I'll try that, thanks.

6 hours ago, adrian said:

Weird though that it's not causing problems for anyone else

Looking at that chunk of code, it's not about setting items to an uninitialised array with $paths[] = $path (which is okay) but if $iter is empty then $paths does not exist.

  • Like 1

Share this post


Link to post
Share on other sites

A search feature to the panels would be nice, it was suggested a few times before. I think a gui-less one would fit here, I mean start typing and a small lime in the bottom left corner would show the search string only (like google chrome's url display on link hover), esc would exit. The problem is that there are several panel types and closed sections, etc.

Share this post


Link to post
Share on other sites
On 10/28/2017 at 11:55 AM, tpr said:

Thanks and keep bugging us with such updates :)

Ok, you asked for it.

The main Dumps panel is now better at reporting bd() calls from obscure places, like other modules, and within Tracy itself.

These improvements are fairly well tested, but please let me know if you notice anything it's not reporting that it should.

I also added a new "Modules Refresh" option to the PW Info panel. This is not only a useful shortcut on the frontend, but because it returns you to the URL you were on, I actually prefer it to using the "Modules > Refresh" link on the backend as well.

 

18 hours ago, tpr said:

A search feature to the panels would be nice, it was suggested a few times before. I think a gui-less one would fit here, I mean start typing and a small lime in the bottom left corner would show the search string only (like google chrome's url display on link hover), esc would exit. The problem is that there are several panel types and closed sections, etc.

I am definitely open to more discussion on this, but at the moment I don't really see a good solution that will work across all panels - information is presented in many different ways in the different panels, so I think we would need to target this to the ones that really need search/filtering.

  • Like 3

Share this post


Link to post
Share on other sites

Hi @adrian,

I've just updated to v4.7.6 – skipping a few versions altogether – and my current interest is in the ProcessWire Info Panel.

I noticed that turning on API variables, Core Classes and Config Data does have an impact on page load time, as expected. Panel selector reports 300ms vs 14ms (frontend with not to much on it).

However, System Info's page load time report doesn't change at all: always about 260ms, no matter what is enabled for the ProcessWire Info Panel. 260ms is less than 300ms, so I wonder how these numbers are related in the first place?

I also have a request regarding this ProcessWire Info Panel. Since "API variables, Core Classes and Config Data" takes a considerable time to load, it would be great if we could keep them turned off by default, and temporarily enable them just like the panels themselves (Once, Sticky) but this would be an overkill, I think, so maybe moving them to their own panel would suffice.

I mean, I normally don't need them but when I want to peek under the hood they are very helpful indeed. I also tested page load time just by watching Chrome's loading animation and it is indeed a lot faster to load the page without them, so there is a good reason to keep them off. However, going to Tracy's settings to turn them on/off is time consuming.

What do you think?

Edited by szabesz
typo

Share this post


Link to post
Share on other sites

Hey @szabesz - I am surprised you are seeing such a dramatic difference in load times for the PW Info panel with those 3 sections enabled.

I just tested on two of my servers and got these results:

Server 1

Those sections enabled: 28ms

Those sections disabled: 22ms

Server 2

Those sections enabled: 6ms

Those sections disabled: 3ms


So for me, there really is no noticeable difference in load times. But we have seen discrepancies like this before. I remember when kongondo had really slow load times with the three objects in this panel, but it didn't affect you at all. Could you maybe determine which one of these three is causing the main slowdown? If it's "Config Data", then I would suggest just disabling that and using the Console panel and doing: d($config) whenever you want that info.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By joshuag
      Hey guys, 
      Thought I would share a quick preview of Designme. A module we (Eduardo @elabx and I) are building for visually laying out your templates/edit screens. 🙂
      This is a really quick, zero polish screen grab. FYI. 
      Video #2 - UPDATE
      This new video shows the following features in Designme:
      Re-arranging fields via Drag & Drop Re-sizing fields via Dragging. Adjusting field settings - with live refresh. Working on "hidden" fields while Designme is active. Creating New fields. Deleting fields. Creating/Deleting Tabs. Dragging fields between tabs. Creating fieldsets. Tagging/Un-tagging fields. Fields without headers expand when hovered (like checkboxes). Live filtering of fields in the sidebar. Ability to adjust (all) Template settings without leaving Designme. Template File Tree Editing Template files source code with ACE Editor. Editing Multiple files with ACE Editor. (New Tabs) Saving files. Techie stuff Fields load their own js/css dependancies. *ready to use on creation (*most fields)  Everything happens via Ajax to ProcessPageEdit (via module + hooks). Designme has a JS api that you can use.  All actions trigger events.  We would love any detailed feedback on what you see so far. If you are interested in testing Designme. Let me know below. 🙂
       
       
      Video #1. 
       
    • By dreerr
      TemplateEnginePug (formally TemplateEngineJade)
       
      This module adds Pug templates to the TemplateEngineFactory. It uses https://github.com/pug-php/pug to render templates.
      doctype html html(lang='en') head meta(http-equiv='content-type', content='text/html; charset=utf-8') title= $page->title link(rel='stylesheet', type='text/css', href=$config->urls->templates . 'styles/main.css') body include header.pug h1= $page->title if $page->editable() p: a(href=$page->editURL) Edit Project on GitHub: github.com/dreerr/TemplateEnginePug
      Project in modules directory: modules.processwire.com/modules/template-engine-pug/
       
      For common problems/features/questions about the Factory, use the TemplateEngineFactory thread.
       
    • By tpr
      ProcessNetteTester
      Run Nette Tester tests within ProcessWire admin.
      (continued from here)

      Features
      AJAX interface for running Nette Tester tests, in bulk or manually display counter, error message and execution time in a table run all tests at once or launch single tests show formatted test error messages and report PHP syntax errors stop on first failed test (optional) hide passed tests (optional) display failed/total instead passed/total (optional) re-run failed tests only (optional) auto scroll (optional) include or exclude tests based on query parameters start/stop all tests with the spacebar reset one test or all tests (ctrl+click) https://modules.processwire.com/modules/process-nette-tester/
      https://github.com/rolandtoth/ProcessNetteTester
    • By bernhard
      Some of you might have followed the development of this module here: https://processwire.com/talk/topic/15524-previewdiscussion-rockdatatables/ . It is the successor of "RockDataTables" and requires RockFinder to get the data for the grid easily and efficiently. It uses the open source part of agGrid for grid rendering.
       
      WHY?
      ProcessWire is awesome for creating all kinds of custom backend applications, but where it is not so awesome in my opinion is when it comes to listing this data. Of course we have the built in page lister and we have ListerPro, but none of that solutions is capable of properly displaying large amounts of data, for example lists of revenues, aggregations, quick and easy sorts by the user, instant filter and those kind of features. RockGrid to the rescue 😉 
       
      Features/Highlights:
      100k+ rows Instant (client side) filter, search, sort (different sort based on data type, eg "lower/greater than" for numbers, "contains" for strings) extendable via plugins (available plugins at the moment: fullscreen, csv export, reload, batch-processing of data, column sum/statistics, row selection) all the agGrid features (cell renderers, cell styling, pagination, column grouping etc) vanilla javascript, backend and frontend support (though not all plugins are working on the frontend yet and I don't plan to support it as long as I don't need it myself)  
      Limitations:
      While there is an option to retrieve data via AJAX the actual processing of the grid (displaying, filtering, sorting) is done on the client side, meaning that you can get into troubles when handling really large datasets of several thousands of rows. agGrid should be one of the most performant grid options in the world (see the official example page with a 100k row example) and does a lot to prevent problems (such as virtual row rendering), but you should always have this limitation in mind as this is a major difference to the available lister options that do not have this limitation.
      Currently it only supports AdminThemeUikit and I don't plan to support any other admin theme.
       
      Download: https://gitlab.com/baumrock/RockGrid
      Installation: https://gitlab.com/baumrock/RockGrid/wikis/Installation
      Quikckstart: https://gitlab.com/baumrock/RockGrid/wikis/quickstart
      Further instructions: https://gitlab.com/baumrock/RockGrid/wikis/quickstart#further-instructions
       
      Module status: alpha, License: MIT
      Note that every installation and uninstallation sends an anonymous google analytics event to my google analytics account. If you don't want that feel free to remove the appropriate lines of code before installation/uninstallation.
       
      Contribute:
      You can contribute to the development of this and other modules or just say thank you by
      testing, reporting issues and making PRs at gitlab liking this post buying me a drink: paypal.me/baumrock/5 liking my facebook page: facebook.com/baumrock hiring me for pw work: baumrock.com  
      Support: Please note that this module might not be as easy and plug&play as many other modules. It needs a good understanding of agGrid (and JavaScript in general) and it likely needs some looks into the code to get all the options. Please understand that I can not provide free support for every request here in the forum. I try to answer all questions that might also help others or that might improve the module but for individual requests I offer paid support for 60€ per hour.
       
      Changelog
      180711 bugfix (naming issue) 180630 alpha realease  
      Use Cases / Examples:
      Colored grid cells, Icons, Links etc. The Grid also has a "batcher" feature built in that helps communicating with the server via AJAX and managing resource intensive tasks in batches:

      Filters, PW panel links and instant reload on panel close:

      You can combine the grid with a chart library like I did with the (outdated) RockDataTables module:

    • By tpr
      Update 2018-07-09: ProcessNetteTester module is available in the Modules Directory and on GitHub.

      This is a short tutorial on how to use Nette Tester with ProcessWire.
      As you will see it's very easy to setup and use and it's perfect for testing your code's functionality. With bootstrapping ProcessWire it's also possible to check the rendered markup of pages using the API, checking page properties, etc. It's also a great tool for module developers for writing better code. 
      While there will be nothing extraordinary here that you couldn't find in Tester's docs this can serve as a good starting point.
      Prerequisites: PHP 5.6+
      01 Download Tester
      Go to https://github.com/nette/tester/releases and download the latest release (currently 2.0.2). Download from the link reading "Source code (zip)". You can use composer also if you wish.
      02 Extract Tester files
      Create a new directory in your site root called "tester". Extract the zip downloaded here, so it should look like this:
      /site /tester/src /tester/tools /tester/appveyor.yml /tester/composer.json /tester/contributing.md /tester/license.md /tester/readme.md /wire ... 03 Create directory for test files
      Add a new directory in "/tester" called "tests". Tester recognizes "*.Test.php" and "*.phpt" files in the tests directory, recursively. 
      04 Create your first test
      In the "tests" directory create a new "MyTest.php" file.
      The first test is a very simple one that bootstraps ProcessWire and checks if the Home page name is "Home". This is not the smartest test but will show you the basics.
      Add this to "/tester/tests/MyTest.php":
      <?php namespace ProcessWire; use \Tester\Assert; use \Tester\DomQuery; use \Tester\TestCase; use \Tester\Environment; require __DIR__ . '/../src/bootstrap.php'; // load Tester require __DIR__ . '/../../index.php'; // bootstrap ProcessWire Environment::setup(); class MyTest extends TestCase {     // first test (step 04)     public function testHomeTitle()     {         $expected = 'Home'; // we expect the page title to be "Home"         $actual = wire('pages')->get(1)->title; // check what's the actual title Assert::equal($expected, $actual); // check whether they are equal     }     // second test will go here (step 06)     // third test will go here (step 07) } // run testing methods (new MyTest())->run(); I've added comment placeholders for the second and third tests that we will insert later.
      05 Run Tester
      Tester can be run either from the command line or from the browser. The command line output is more verbose and colored while in the browser it's plain text only (see later).
      Running from the command line
      Navigate to the "/tester" directory in your console and execute this:
      php src/tester.php -C tests This will start "/tester/src/tester.php" and runs test files from the "/tester/tests" directory. The "-C" switch tells Tester to use the system-wide php ini file, that is required here because when bootstrapping ProcessWire you may run into errors (no php.ini file is used by default). You may load another ini file with the "-c <path>" (check the docs).
      If the title of your Home page is "Home" you should see this:

      If it's for example "Cats and Dogs", you should see this:

      Running from the browser
      First we need to create a new PHP file in ProcessWire's root, let's call it "testrunner.php". This is because ProcessWire doesn't allow to run PHP files from its "site" directory.
      The following code runs two test classes and produces a legible output. IRL you should probably iterate through directories to get test files (eg. with glob()), and of course it's better not allow tests go out to production.
      <?php ini_set('html_errors', false); header('Content-type: text/plain'); echo 'Starting tests.' . PHP_EOL; echo '--------------------------' . PHP_EOL; $file = __DIR__ . '/PATH_TO/FirstTest.php'; echo basename($file) . ' '; require $file; echo '[OK]' . PHP_EOL; $file = __DIR__ . '/PATH_TO/SecondTest.php'; echo basename($file) . ' '; require $file; echo '[OK]' . PHP_EOL; echo '--------------------------' . PHP_EOL; echo 'Tests finished.'; exit; Navigate to "DOMAIN/testrunner.php" in your browser to execute the file. If every test succeeds you should get this:

      If there are failed tests the execution stops and you can read the error message. If there were more tests (eg. ThirdTest), those won't be displayed under the failed test.

      06 DOM test
      This test will check if a page with "basic-page" template has a "h1" element. We will create the page on the fly with ProcessWire's API. To keep things simple we will add the new test as a new method to our MyTest class.
      Add this block to the MyTest class:
      public function testBasicPageHeadline() {     $p = new Page();     $p->template = 'basic-page';     $html = $p->render();     $dom = DomQuery::fromHtml($html);     Assert::true($dom->has('h1')); } This will most likely be true but of course you can check for something more specific, for example "div#main". Note that we have used the DomQuery helper here (check the "use" statement on the top of the file).
      07 Custom function test
      You will probably want to make sure your custom functions/methods will work as they should so let's write a test that demonstrates this.
      I don't want to complicate things so I'll check if the built-in "pageName" sanitizer works as expected. Add this to the myTest class:
      public function testPageNameSanitizer() {     $expected = 'hello-world';     $actual = wire('sanitizer')->pageName('Hello world!', true);     Assert::equal($expected, $actual); } This should also be true. Try to change the expected value if you are eager to see a failure message.
       
      08 Next steps
      You can add more methods to the MyTest class or create new files in the "tests" directory. Check out the range of available Assertions and other features in the docs and see how they could help you writing more fail-safe code.
      Once you make a habit of writing tests you'll see how it can assist making your code more bulletproof and stable. Remember: test early, test often 🙂
      If you find out something useful or cool with Tester make sure to share.