Jump to content

Tracy Debugger


adrian

Recommended Posts

@gmclelland - I think you're issues should be fixed in the latest version (thanks for PM help with this).

@bernhard - I have modified the behavior of the large/small buttons in the Console panel to be fullscreen/halfscreen. Please take a look and let me know if you think that behavior suits your needs. I am ok with adding it to other panels as well if you think it works well, although obviously some panels would look pretty silly fullscreen :)

As for the z-index issues - I think that's maybe an AOS conflict - @tpr was working on that yesterday. Please let me know if they persist with AOS disabled.

Everyone else - while fixing the issue that @gmclelland was having, I make quite a few changes to the the Field List & Values section of the Request Info panel. It should now generally be even lighter and yet also show more depth of details. It also now shows unformatted and formatted values for each field. There is also a new Image Details column - displaying the thumbnails is optional (check config settings - you may want to disable if you have image fields with lots of images).

image.thumb.png.109622e46c5c87e126e0296843176aa8.png

Please let me know if you have any issues with the new version or ideas for improvements.

 

  • Like 3
  • Thanks 1
Link to comment
Share on other sites

That Field Values panel is huge :) I guess it's available for a while but I haven't seen it (probably along with many others) :)

Here is a small tweak that could make such large tables easier to read - sticky table headers:

.tracy-panel th {
  position: sticky;
  top: -13px;
}

sticky-th.thumb.gif.e1db7d6eebd9b5f451270bde23ac25f4.gif

The value -13px is probably a margin issue, and the inverted TH colors are there for better separation.

Of course these sticky headers could be enabled separately for the different panels but I think they won't do any harm when applied globally but maybe I'm wrong.

And Now for Something Completely Different

Rollup panel on double-click on their titles:

doubleclick-toggle.gif.7ae3a62a43c64b1e8b72008efc1eb9bc.gif

This is only quick devtools implementation but if you're interested I can roll down a better one :)

  • Like 5
Link to comment
Share on other sites

19 minutes ago, gmclelland said:

What do you think about the thumbnail linking to the original file?

Sure, I'll add to the next version.

6 minutes ago, tpr said:

Here is a small tweak that could make such large tables easier to read - sticky table headers

Sounds like a good idea - thanks!

6 minutes ago, tpr said:

Rollup panel on double-click on their titles

I think this looks awesome actually. I was kinda looking for something along these lines, but never really figured out the best approach. I went with the ESC to close all panels, but then there was no way to restore. I was going to add a Tab key option to work like tool panels in Adobe products, but you can't really make use of the tab key like that because it's needed for so many other things. I think what you have here looks like a great option for quickly getting a panel out of the way without closing it. Would appreciate some code whenever you get around to it - thanks!

  • Like 1
Link to comment
Share on other sites

Of course several unforseen issues came up but most of them are fixed:

  • closing a rolled-up panel and re-activating it from the debug bar opened it in the rolled-up state. To fix, on closing a rolled-up panel "tracy-mode-rollup" class is removed so it opens up in normal state.
  • setting width-height were tricky here and there but seems to be OK now with all the panels I've tried (Chrome only though).
  • "ProcessWire Logs" panel has a link in h1, I've added pointer-events: none in rolled-up state to prevent accidental click on move
  • resized panels were loaded cropped after page reload (if they were rolled up before reload). I've fixed it with a "beforeunload" event to allow Tracy save positions correctly
  • keeping state after page reload: would be nice to have but I think this would be better handled in the core (Nette Tracy)

Changes:

style.css

Lines at the bottom + added "user-select: none" on line 111 for h1

TracyDebugger.module

Lines 823-867 - I haven't found a better place to add the JS part, I thought there's a js file that the module always loads but apparently there isn't.

tracy-rollup.zip

  • Like 3
Link to comment
Share on other sites

Hey @tpr - thanks for your work on this - I think it's a great addition.

Not sure why, but I had to change max-height for the rolled up version from 39px to 47px, otherwise I got a scrollbar in the header. Does it look OK for you with this change (just committed).

I moved the js into main.js (which is new) as a place to load all general JS (that doesn't need injected PHP vars).

The last version also includes some z-index fixes (introduced recently in the Tracy core), your sticky table header, and I added the fullscreen/halfscreen button to a couple of other panels that I thought could benefit from it. Also added @gmclelland's idea of linking to fullsize version of image. In the PW admin this opens in a modal, but just same page in frontend.

Thanks again!

  • Like 4
Link to comment
Share on other sites

Thanks, works fine here. The 47px vs 39px issue may come from a box-sizing border-box/content-box issue, perhaps my frontend CSS was interfering somehow. If so, .tracy-panels should get box-sizing: border-box in Tracy.

Sticky table headers are working fine too, thanks.

What do you think about making the panel headers a bit smaller? I feel they are a bit too large, a  slightly slower font and less padding wouldn't hurt imho.

  • Like 1
Link to comment
Share on other sites

4 minutes ago, tpr said:

What do you think about making the panel headers a bit smaller? I feel they are a bit too large, a  slightly slower font and less padding wouldn't hurt imho.

+1 :) I am all for slim GUI for development tools...

  • Like 1
Link to comment
Share on other sites

19 hours ago, adrian said:

I have modified the behavior of the large/small buttons in the Console panel to be fullscreen/halfscreen. Please take a look and let me know if you think that behavior suits your needs. I am ok with adding it to other panels as well if you think it works well, although obviously some panels would look pretty silly fullscreen :)

awesome! this helps a lot, thanks :)

  • Like 2
Link to comment
Share on other sites

7 hours ago, tpr said:

What do you think about making the panel headers a bit smaller? I feel they are a bit too large, a  slightly slower font and less padding wouldn't hurt imho.

Sounds good, now what about the border width: 4, 3, 2, or 1?

I am thinking 2 or 3

image.png.7967a1e4819ae6a74498c886282e546c.png

image.png.63604391f7f82ea949b59c823c85d721.png

image.png.14eebb87bf57562df47384d6fa5f156c.png

image.png.5c21c83e0e942f950d2bf9405d1725d3.png

 

 

  • Like 1
Link to comment
Share on other sites

Yepp, the border is a bit thick now. I'm fine with v4 if you think panels doesn't merge too much with the rest of the site.

One thing though: the icon positions need to be adjusted (before the title and the window/close icons too) + the newly added rollup state needs adjustments too.

  • Like 1
Link to comment
Share on other sites

Hey @adrian,

what do you think of adding a check if debugInfo is available for the requested object and if not, set it to "false" automatically?

I'm working on my RockFinder module and wanted to debug my subclass. This was the result:

5ad47946b6454_2018-04-1612_20_18-ModulesProcessWirerockfinder_test.png.e0267c434c3d6fd07fd3e84078647597.png

Switching "debugInfo" to false I get this:

5ad4794a17156_2018-04-1612_19_43-ModulesProcessWirerockfinder_test.png.f8c096810386a145bf0df467a3f2bab1.png

Which is of course much more helpful. Luckily I remembered about that because we were talking about it here, but if someone missed that it could be quite hard to find out what is going on and why the information does not show up...

Also it is quite annoying to always set ['debugInfo' => false] for every quick d($myobject)

  • Like 1
Link to comment
Share on other sites

Hey @bernhard - I think it should already work that way:

image.png.9513aad49d69547b4adb94cd8f792e40.png

So I am wondering if it's due to your class extending a PW class that does implement __debugInfo()

Could you please let me know what you trying to dump in your module so I can reproduce what you are seeing. 

  • Like 1
Link to comment
Share on other sites

Ok, thx. My class is indeed extending Wire... Maybe there is a possibility to check for the number of properties the debugInfo object returns and in case it is 0 it falls back to the original object dump?

Link to comment
Share on other sites

2 minutes ago, bernhard said:

Ok, thx. My class is indeed extending Wire... Maybe there is a possibility to check for the number of properties the debugInfo object returns and in case it is 0 it falls back to the original object dump?

Maybe - I'll see what can be done, but to make it a little easier, can you let me know what variable in RockSqlFinder you are dumping, and where?

  • Like 1
Link to comment
Share on other sites

I'm doing a complete rewrite (again :P ). What I have so far is this:

<?php namespace ProcessWire;
class RockFinderField extends Wire {

  private $name; // name of the final object property
  private $field; // name of the field to query
  private $closure = null; // closure to calc value

  /**
   * constructor
   */
  public function __construct($name, $field) {
    // set the final column name for this field
    if(is_string($name)) $this->name = $name;
    else $this->name = $field;

    // check the field type
    if(is_callable($field) AND !is_string($field)) {
      $this->closure = $field;
    }
    else {
      $this->field = $field;
    }
  }
}

And in the module I do this:

foreach($fields as $key => $value) $this->fields[] = new RockFinderField($key, $value);
bd($this->fields);

 

Link to comment
Share on other sites

@bernhard - I have a temporary solution for you. Replace https://github.com/adrianbj/TracyDebugger/blob/93fe130026244fe727e5553b82183a85b78e2c9f/tracy-master/src/Tracy/Dumper.php#L460

with:

return count((array) $obj->__debugInfo()) ? $obj->__debugInfo() : (array) $obj;

There are other ways this could be achieved, but since this is modifying the Tracy core, I am going to ask them what they think is the best approach.

Let me know if it works as expected for you.

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

@adrian Morning,

I've been having a hard time with the panels since you introduced the "resize feature". I use AOS with sticky header enabled in Reno. The panels keep moving under Reno's sticky header, making it impossible to move them anywhere, as the head of the panel is "covered" by the admin's header.

There are various occasions when this happens but here is a frequent example: I use bd() and click on the arrow to expand an object with a long list. The panel expands too, moving its head under the sticky header of Reno. BTW: I'm currently running AOS 1.9.0 and Tracy 4.10.18, so these are the latest.

Before you introduced the "resize feature" I had never had such issues. Is there anything that can be done? Maybe @tpr can do something? :)

See image:

Spoiler

tray-panel-under-sticky-header.thumb.png.502cc28a93633850550d6182a2387ea2.png

 

Link to comment
Share on other sites

Hey @szabesz - I can reproduce, but it's fine with the default and Uikit themes with sticky headers so I think it's something that @tpr might need to fix. I know he made some recent changes on this front so maybe those changes need to be applied to the reno sticky header as well?

  • Like 1
Link to comment
Share on other sites

I haven't found a way to make all the z-indexes work nicely together. I could add #tracy-debug { z-index: 100000; } or so when sticky headers are enabled in AOS but that would make menu dropdowns and such overlapped by Tracy panels.

Link to comment
Share on other sites

1 minute ago, tpr said:

I haven't found a way to make all the z-indexes work nicely together. I could add #tracy-debug { z-index: 100000; } or so when sticky headers are enabled in AOS but that would make menu dropdowns and such overlapped by Tracy panels.

But sticky headers are working fine with Tracy panels in the default and UiKit themes. Is there something different about the reno sticky header that you can't change to be like the other two?

Link to comment
Share on other sites

There are lot more elements in Reno, including the sidebar and many header elements. Setting #wrap { z-index: 0 } also solves the panel issue but still the panels are above menus.

Link to comment
Share on other sites

  • adrian pinned and locked this topic
  • adrian unpinned and pinned this topic
Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Robin S
      This module lets you add some custom menu items to the main admin menu, and you can set the dropdown links dynamically in a hook if needed.
      Sidenote: the module config uses some repeatable/sortable rows for the child link settings, similar to the ProFields Table interface. The data gets saved as JSON in a hidden textarea field. Might be interesting to other module developers?
      Custom Admin Menus
      Adds up to three custom menu items with optional dropdowns to the main admin menu.
      The menu items can link to admin pages, front-end pages, or pages on external websites.
      The links can be set to open in a new browser tab, and child links in the dropdown can be given an icon.
      Requires ProcessWire v3.0.178 or newer.
      Screenshots
      Example of menu items

      Module config for the menus

      Link list shown when parent menu item is not given a URL

      Advanced
      Setting child menu items dynamically
      If needed you can set the child menu items dynamically using a hook.
      Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); if($menu_number === 1) { $colours = $event->wire()->pages->findRaw('template=colour', ['title', 'url', 'page_icon']); $children = []; foreach($colours as $colour) { // Each child item should be an array with the following keys $children[] = [ 'icon' => $colour['page_icon'], 'label' => $colour['title'], 'url' => $colour['url'], 'newtab' => false, ]; } $event->return = $children; } }); Create multiple levels of flyout menus
      It's also possible to create multiple levels of flyout submenus using a hook.

      For each level a submenu can be defined in a "children" item. Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); if($menu_number === 1) { $children = [ [ 'icon' => 'adjust', 'label' => 'One', 'url' => '/one/', 'newtab' => false, ], [ 'icon' => 'anchor', 'label' => 'Two', 'url' => '/two/', 'newtab' => false, 'children' => [ [ 'icon' => 'child', 'label' => 'Red', 'url' => '/red/', 'newtab' => false, ], [ 'icon' => 'bullhorn', 'label' => 'Green', 'url' => '/green/', 'newtab' => false, 'children' => [ [ 'icon' => 'wifi', 'label' => 'Small', 'url' => '/small/', 'newtab' => true, ], [ 'icon' => 'codepen', 'label' => 'Medium', 'url' => '/medium/', 'newtab' => false, ], [ 'icon' => 'cogs', 'label' => 'Large', 'url' => '/large/', 'newtab' => false, ], ] ], [ 'icon' => 'futbol-o', 'label' => 'Blue', 'url' => '/blue/', 'newtab' => true, ], ] ], [ 'icon' => 'hand-o-left', 'label' => 'Three', 'url' => '/three/', 'newtab' => false, ], ]; $event->return = $children; } }); Showing/hiding menus according to user role
      You can determine which menu items can be seen by a role by checking the user's role in the hook.
      For example, if a user has or lacks a role you could include different child menu items in the hook return value. Or if you want to conditionally hide a custom menu altogether you can set the return value to false. Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); $user = $event->wire()->user; // For custom menu number 1... if($menu_number === 1) { // ...if user does not have some particular role... if(!$user->hasRole('foo')) { // ...do not show the menu $event->return = false; } } });  
      https://github.com/Toutouwai/CustomAdminMenus
      https://processwire.com/modules/custom-admin-menus/
    • By tcnet
      This module for ProcessWire sends a notification email for each failed login attempt. Similar modules exists already in the module directory of ProcessWire. However, this module is designed to notify, even if specified user doesn't exist.
      Settings
      The settings for this module are located in the menu Modules=>Configure=>LoginFailNotifier.
      Notification email
      Specifies the email address to which the notification emails should be sent.
        Email subject
      Specifies the subject line for the notification email.
        Post variables
      Specifies the $_POST variables to be included in the notification email. Each variable must be separated by a comma. For example: login_name,login_pass
        Server variables
      Specifies the $_SERVER variables to be included in the notification email. Each variable must be separated by a comma. For example: REMOTE_ADDR,HTTP_USER_AGENT
      Link to ProcessWire module directory:
      https://processwire.com/modules/login-fail-notifier/
      Link to github.com:
      https://github.com/techcnet/LoginFailNotifier
    • By Fokke
      ProcessWire 3.x markup module for rendering meta tags in HTML document head section. Note that this module is not a full-blown SEO solution, but rather a simple tool for rendering meta tags based on module configuration. Adding custom meta tags is also supported.
      Built-in meta tags
      The following meta tags are supported out-of-the-box:
      Document title consisting of page title and site name Character set Canonical Viewport Description Keywords Hreflang tags Open Graph og:title og:site_name og:type og:url og:description og:image og:image:width og:image:height Twitter meta tags twitter:card twitter:site twitter:creator twitter:title twitter:description twitter:image Facebook meta tags fb:app_id The full documentation with configurable options can be found here: https://github.com/Fokke-/MarkupMetadata
       
      Requirements:
      ProcessWire>=3.0.0 PHP >=7.1 Installation using Composer
      composer require fokke/markup-metadata Manual installation
      Download latest version from https://github.com/Fokke-/MarkupMetadata/archive/master.zip Extract module files to site/modules/MarkupMetadata directory.
    • By m.sieber
      ITRK-Service for ProcessWire
      Module for the automated transfer of imprint, data protection declaration and terms and conditions from IT-Recht Kanzlei to your ProcessWire installation
      What is ITRK Service for ProcessWire?
      ITRK-Service for ProcessWire is a free module for ProcessWire CMS. It provides an interface to the update service of IT-Recht Kanzlei, via which the legal texts of your online presence are automatically updated. In this way, the texts remain legally secure and warning-proof in the long term. Imprint, data protection declaration, revocation and general terms and conditions are currently supported.
      You can find our documentation (in german language) here: https://www.pupit.de/itrk-service-for-processwire/dokumentation/

      Download: https://www.pupit.de/itrk-service-for-processwire/
      Github: https://github.com/pupit-de/pwItrkServiceConnector
    • By LuisM
      Symprowire is a PHP MVC Framework based and built on Symfony using ProcessWire 3.x as DBAL and Service-Provider
      It acts as a Drop-In Replacement Module to handle the Request/Response outside the ProcessWire Admin. Even tough Symfony or any other mature MVC Framework could be intimidating at first, Symprowire tries to abstract Configuration and Symfony Internals away as much as possible to give you a quick start and lift the heavy work for you.
      The main Goal is to give an easy path to follow an MVC Approach during development with ProcessWire and open up the available eco-system.
      You can find the GitHub Repo and more Information here: https://github.com/Luis85/symprowire
      Documentation
      The Symprowire Wiki https://github.com/Luis85/symprowire/wiki How to create a simple Blog with Symprowire https://github.com/Luis85/symprowire/wiki/Symprowire-Blog-Tutorial Last Update
      16.07.2021 // RC 1 v0.6.0 centralized ProcessWire access trough out the Application by wrapping to a Service https://github.com/Luis85/symprowire/releases/tag/v0.6.0-rc-1 Requirements
      PHP ^7.4 Fresh ProcessWire ^3.0.181 with a Blank Profile Composer 2 (v1 should work, not recommended) The usual Symfony Requirements Features
      Twig Dependency Injection Monolog for Symprowire Support for .env YAML Configuration Symfony Console and Console Commands Symfony Webprofiler Full ProcessWire access inside your Controller and Services Webpack Encore support Caveats
      Symfony is no small Framework and will come with a price in terms of Memory Usage and added Overhead. To give you a taste I installed Tracy Debugger alongside to compare ProcessWire profiling with the included Symfony Webprofiler

      So in a fresh install Symprowire would atleast add another 2MB of Memory usage and around 40ms in response time, should be less in production due to the added overhead of the Webprofiler in dev env
       
×
×
  • Create New...