adrian

Tracy Debugger

Recommended Posts

15 hours ago, Robin S said:

I wouldn't mind an option that keeps the debug bar locked in the bottom right because personally I never move it from there.

This CSS seems to be working well for me so far...

#tracy-debug-bar { position:fixed !important; left:auto !important; top:auto !important; right:0 !important; bottom:0 !important; }

 

  • Like 2

Share this post


Link to post
Share on other sites

@Robin S - I'll see what comes of those discussions over on the tracy github account, but if they don't implement an option to fix position, I will add one to the config settings that uses your css - thanks!

  • Like 2

Share this post


Link to post
Share on other sites

Hi @adrian,

Until Ryan adds core support for loading Tracy early, what do you think about adding some Tracy option to make it easier for users to load Tracy early if they don't mind making changes to the core index.php for that purpose? Something like Tracy checks if $config->earlyTracy is true and if so doesn't load files that will have been loaded in the modified index.php. So the user only has to modify core file(s) and not Tracy files.

On a related note, I'm trying to follow the suggestions you made here to load Tracy early but I can't get it working.

I have these extra lines in index.php...

require_once $config->paths->siteModules.'TracyDebugger/tracy-master/src/tracy.php';
require_once $config->paths->siteModules.'TracyDebugger/includes/TD.php';
require_once $config->paths->siteModules.'TracyDebugger/includes/ShortcutMethods.php';

...and have commented out their equivalents in TracyDebugger.module, but I get this error:

Fatal error: Class 'TracyDebugger' not found in D:\_Websites\_www\1testing\site\modules\TracyDebugger\includes\TD.php on line 6

 

Could you explain again any tricks you know for how to load Tracy early? Thanks.

 

Share this post


Link to post
Share on other sites

Hi @Robin S - sorry for the slow response on this. Honestly I didn't really get very far attempting to load Tracy early. I thought it was ok initially, but as that thread showed, there were lots of issues I didn't initially see. I think it needs some significant investigation. I just don't have the time for that at the moment, but if you find a solution, I am very happy to implement any conditionals in Tracy to make it possible.

 

Share this post


Link to post
Share on other sites
3 minutes ago, adrian said:

Honestly I didn't really get very far attempting to load Tracy early.

I just thought you might have some trick, because in this post you seemed to be able to use Tracy to dump inside Page::resetTrackChanges but when I tried bd() was undefined inside that method.

Share this post


Link to post
Share on other sites
3 hours ago, Robin S said:

I just thought you might have some trick, because in this post you seemed to be able to use Tracy to dump inside Page::resetTrackChanges but when I tried bd() was undefined inside that method.

@Robin S - I'll have to get back to you on that when I get a minute to look into it.

Totally OT, I just wanted to mention this issue to you guys because it cost me some time today.

Now that Tracy by default uses __debugInfo() for d() an bd() calls, I was getting empty responses for d($input->get), post, cookies etc. I have posted an issue for Ryan: 
https://github.com/processwire/processwire-issues/issues/575 - please feel free to +1 it!

but in the meantime, you will need to set debugInfo to false or turn of __debugInfo() completely in the config settings.

image.png.294531aab11ee98d0df561915f236ff2.png

 

  • Like 1

Share this post


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

I was getting empty responses for d($input->get)

I discovered the empty $input dump as soon as __debugInfo() was made the default dump in Tracy. Sorry, I should have raised it at the time but was in the middle of something so just changed back to the full dump setting and then forgot about it.

Maybe it's just because I'm more used the full dump, but I still prefer that option. I like having more info in the dump rather than less and don't mind wading through it to find what I'm looking for.

  • Like 2

Share this post


Link to post
Share on other sites
7 minutes ago, Robin S said:

Maybe it's just because I'm more used the full dump, but I still prefer that option. I like having more info in the dump rather than less and don't mind wading through it to find what I'm looking for.

Yeah, I am not actually sure which I prefer at the moment - I think it depends on the complexity and also how well Ryan implemented __debugInfo() for the object type in question.

Share this post


Link to post
Share on other sites

Welcome to the club, Adrian 😉 +1 for making the large dump default. I also think it's better to turn it off if you need but see everything by default so that misleading situations like yours and mine some days ago are less likely to happen

  • Like 1

Share this post


Link to post
Share on other sites
5 hours ago, bernhard said:

Welcome in the club, Adrian 😉 +1 for making the large dump default.

Hey Bernhard - not sure on this yet - I think for the average new Tracy user using __debugInfo() is a more useful experience - a full PW object can be quite overwhelming for the uninitiated. Of course once you're comfortable with them they're fine, but they also often require the use of bdb() or bd($page, [8]) type calls to get to all the info you need and a new user may not know about those options yet and just think that those [...] mean that the info isn't available.

For those reasons I am tempted to leave as is for the moment.

Note that Ryan just implemented __debugInfo() for WireInput: https://github.com/processwire/processwire/commit/105ba2b8ebbdf4e65f2300bf79b233850107c4d6 so that issue is solved at least.

 

  • Like 1

Share this post


Link to post
Share on other sites
1 hour ago, adrian said:

I think for the average new Tracy user using __debugInfo() is a more useful experience

Sure, I'm with you here. But I think it's much more critical to get an empty dump than to get a bloated one where you need to look for the correct information and maybe turn on the "cleanup feature". But I can live with both versions, of course ;)

Edit: @adrian could it maybe show a notice on empty debugInfo objects to turn "debugInfo cleanup" OFF to be sure it is really empty?

  • Like 1

Share this post


Link to post
Share on other sites

Hey @bernhard - I get your issue with empty vs bloated for sure. When I get some time I'll look into the possibility of a check for an empty object, although I do think that maybe that's something the PW wire __debugInfo method might be the best way to handle this.

Just an FYI - Ryan just added a detailed PageFiles __debugInfo() method, so now we get this in the Request Info panel, which is pretty nice!

image.thumb.png.73198ea175ff27af8a8a26fc3e34d120.png

  • Like 3

Share this post


Link to post
Share on other sites

Hi @adrian, what do you think of adding a Facebook Sharing Debugger panel to the module? It requires login and there's no GET way to force "Scrape again" (as I know) but still it would make easier to check the opengraph data on a page. For me a simple link would suffice (unlike the Validator panel).

  • Like 2

Share this post


Link to post
Share on other sites
5 hours ago, tpr said:

For me a simple link would suffice

If you just want a link to that page with the site's URL passed, have you tried the Custom PHP panel?

That said, I am curious about a more complete integration and a dedicated panel - I'll add it to my list for when I have a spare 5 minutes - it's busy here ATM :)

Share this post


Link to post
Share on other sites

No, I haven't tried this time but recently I've added buttons to it. Just wanted to mention this because this feature could be useful also to others (or am I the only one blessed with such a client? :))

  • Like 2

Share this post


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

am I the only one blessed with such a client?

Not at all - lots of need to do FB debugging these days. It's on my list, but don't hold your breath - I am panic stations till the end of the week, then away for 2 weeks - maybe sometime late May or early June!

Share this post


Link to post
Share on other sites

Sure, it's fine to me having this somewhere low on your todo list :)

Share this post


Link to post
Share on other sites

hey adrian, hope you are enjoying your vacation!

what do you think of adding a section in the request info panel that shows the code needed for creating this field via api (for example in process module)?

$form->add([
  'type' => 'page',
  'label' => __('Mail auswählen'),
  'derefAsPage' => 1, // single or null
  'inputfield' => 'InputfieldAsmSelect',
  'template_id' => 73, // mail
  'value' => 23669,
]);

The request info panel has all the necessary informations:

2018-05-14--18-13-08.png.1382a9f99221aa4e2f8447bba9b6df15.png

If we had a section "Field code" we could just create fields in the Backend and then copy/paste them in our modules 🙂

  • Like 2

Share this post


Link to post
Share on other sites
16 hours ago, bernhard said:

adding a section in the request info panel

It should be optional/temporary so that there is no extra markup generated when it is not needed. Tracy already outputs a lot... Anyway, I like the idea 🙂

Share this post


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

It should be optional/temporary so that there is no extra markup generated when it is not needed. Tracy already outputs a lot... Anyway, I like the idea 🙂

You can already disable the request panel... And you can disable tracy completely. Don't think there is a need to overcomplicate things where we already have solutions 🙂

Share this post


Link to post
Share on other sites

Ok, I've created a PR that does at least the first part of what I requested: https://github.com/adrianbj/TracyDebugger/pull/22

2018-05-15--12-05-11.png.92775982a2846fb1ac4e38fd3580bcfb.png

@szabesz adrian was crazy enough to implement exactly what you requested, so that's is already possible 😉

2018-05-15--11-30-16.png.4b9c71d2c9d2c685b285eb77acf7419d.png

@adrian

Regarding my PR: Not sure why, but I have an options field that does not show any information about the selectable options in the request info panel. Also I'm not sure how to work with multilanguage fields, as the inputfield seems to be always single language.

  • Like 1

Share this post


Link to post
Share on other sites

hey @adrian 

just had to update thousands of pages via tracy and that's a bit of a problem using the tracy console because if the task takes a long time you have no idea what is going on behind the scenes... that's my workaround that i'm using:

 

ini_set('max_execution_time', 60*10);
file_put_contents('debug.txt', '');
$sel = 'template=feedback';
d($pages->count($sel));
foreach($pages->find($sel) as $i=>$p) {
    file_put_contents('debug.txt', "$i: {$p->id},  {$p->path}\n", FILE_APPEND);
    $p->save();
}

Then I do this to follow:

tail -f site/assets/cache/TracyDebugger/debug.txt

Of course that is totally fine to use, but it would be even nicer to have something like this:

$sel = 'template=feedback';
d($pages->count($sel));
foreach($pages->find($sel) as $i=>$p) {
    fd("$i: {$p->id},  {$p->path}\n", 60*10);
    $p->save();
}

fd() being filedump() setting the max_execution_time, flushing the file on each new console request and appending the dump to it while execution is in progress (just like in my verbose example above);

What do you think of that idea? I know there are other tools around and I'm thinking of implementing such a feature for my RockGrid batcher, but tracy console is always available and by far the quickest option.

Or is there maybe a similar option? fl() dumps only when finished, so if there is an error (max execution time or max memory or the like) you are lost... if the dump is in a file you can lookup how far you got and continue from that stage.

edit: fd() could also be handy when dumping huge amount of data or html code or the like, because then you could leave that file open in your IDE and anayse it quickly with syntax highlighting etc.

filedump.gif.373ccee2cfb2c6074c0a74aadbd37f7b.gif

VSCode automatically updates the file while it is populated. For larger dumps tail -f would be better of course.

Another example of doing a cleanup, population of random values and creating cache:

filedump2.thumb.gif.ae932ebbf4eab0405578aa172b0f0517.gif

Share this post


Link to post
Share on other sites

Hey adrian, me again 😉

I wonder how hard it would be to have the option of enabling/disabling tracy for special pages. I have some performance issues (not severe) here while developing something with my RockGrid module, so disabling Tracy makes working a lot more comfortable. On another page (a custom process module showing charts) I need tracy, so what I do is using the enable/disable button in the debug bar. This always needs a reload and is tedious if you need it more often.

Could there be an option "disable tracy on this special page"?

It seems there's already a config setting for tracy but that had no effect when I tried it. Maybe I did something wrong?

Edit: Tracy is already disabled on modals (when &modal=1 is in the url), so maybe we could just introduce a get variable ?tracy=off 🙂

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 Robin S
      Another little admin helper module...
      Template Field Widths
      Adds a "Field widths" field to Edit Template that allows you to quickly set the widths of inputfields in the template.

      Why?
      When setting up a new template or trying out different field layouts I find it a bit slow and tedious to have to open each field individually in a modal just to set the width. This module speeds up the process.
      Installation
      Install the Template Field Widths module.
      Config options
      You can set the default presentation of the "Field widths" field to collapsed or open. You can choose Name or Label as the primary identifier shown for the field. The unchosen alternative will become the title attribute shown on hover. You can choose to show the original field width next to the template context field width.  
      https://github.com/Toutouwai/TemplateFieldWidths
      https://modules.processwire.com/modules/template-field-widths/
    • By horst
      Croppable Image 3
      for PW 3.0.20+
      Module Version 1.1.16
      Sponsored by http://dreikon.de/, many thanks Timo & Niko!
      You can get it in the modules directory!
      Please refer to the readme on github for instructions.
       
      -------------------------------------------------------------------------
       
      Updating from prior versions:
       
      Updating from Croppable Image 3 with versions prior to 1.1.7, please do this as a one time step:
      In the PW Admin, go to side -> modules -> new, use "install via ClassName" and use CroppableImage3 for the Module Class Name. This will update your existing CroppableImage3 module sub directory, even if it is called a new install. After that, the module will be recogniced by the PW updater module, what makes it a lot easier on further updates.
      -------------------------------------------------------------------------
       
      For updating from the legacy Thumbnail / CropImage to CroppableImage3 read on here.
       
      -------------------------------------------------------------------------
       
    • By MoritzLost
      UPDATE: I have published a stable version of this module!
      Discussion thread:
      Github: https://github.com/MoritzLost/TextformatterPageTitleLinks
      ---
      Hello there,
      I'm working on a tiny textformatter module that searches the text for titles of other pages on your site and creates hyperlinks to them. I'm not sure if something like this exists already, but I haven't found anything in the module directory, so I wrote my own solution 🙂
      It's not properly tested yet and is still missing some functionality I would like to implement, so at the moment it should be considered in BETA. Features include limiting the pages that will get searched by template, and adding a custom CSS class to the generated hyperlinks. As I'm writing this I noticed that it will probably include unpublished and hidden pages at the moment, so yeah ... it's still in development alright 😅
      You can download the module from Github:
      https://github.com/MoritzLost/TextformatterPageTitleLinks
      There's some more information in the readme as well.
      Anyway, let me know what you think! I'm happy about any feedback, possible improvements or ideas on how to improve the module. Cheers.
    • By blad
      Hi guys!
      I just uploaded a module to explore files based on elFinder. By default it will show the "Files" folder.
      Screenshots:

      Video:
       
      To do:
       More options To fix:
       The function of rotating or scaling an image fails  Image editors V 1.01 (view issue)
      Fixed the bug working with the Multi-Language support ( translation of folders ). Fixed the name of elfinder.en  Github:
      https://github.com/LuisSantiago/ProcessElFinder/
      I hope you like it.
    • By BitPoet
      I'm really in love with FormBuilder, but the one thing missing to match all my end users' expectations were repeatable field groups. Think repeaters, in ProcessWire terms. Our primary application of PW is our corporate intranet, so "lines" of fields are quite common in the forms I build. We have all kinds of request forms where the information for a varying number of colleagues needs to be entered (from meal order to flight booking request) and where it is simply impractical to send a form for each, and I don't want to clutter my forms with multiple instances of fields that may only get used ten percent of the time.
      That's why I started to build FormBuilderMultiplier (link to GitHub).
      What it does:
      Adds an option to make a regular Fieldgroup repeatable Lets you limit the number of instances of a Fieldgroup on the form Adds an "Add row" button the form that adds another instance of the Fieldgroup's fields Adds a counter suffix at the end of every affected field's label Stores the entered values just like regular fields Makes the entered values available in preview and email notifications Supports most text based fields, textareas and selects (really, I haven't had enough time to test all the available choices yet) What it doesn't do (yet):
      Support saving to ProcessWire pages (i.e. real Repeaters) I haven't tested all the validation stuff, Date/Time inputs etc. yet, but since I'm utterly swamped with other stuff at work, I didn't want to wait until I have it polished. Any feedback is welcome. There might also be some issues with different output frameworks that I haven't encountered yet. The forms I work with mostly use UIKit.
      Status:
      Still alpha, so test well before using it in the field.
      Known issues:
      When rows are added, the form's iframe needs to be resized, which isn't completely clean yet.
      How it works:
      The Fieldgroup settings are added through regular hooks, as is the logic that adds the necessary field copies for processing the form and displaying previews.
      "Multiplied" field instances are suffixed with _NUM, where NUM is an incremental integer starting from 1. So if you have add two fields named "surname" and "givenname" to a fieldgroup and check the "multiply" checkbox, the form will initially have "surname_1" and "givenname_1" field (I'm still considering changing that to make the risk to shoot oneself into the foot by having a regular "surname_1" field somewhere else in the form less likely).
      When a "row" is added, the first row is cloned through JS and the counter in the fields' IDs, names and "for" attributes as well as the counter in the label are incremented before appending the copies to the Fieldset container in the form.
      To keep backend and frontend in sync, a hidden field named [name of the fieldset]__multiplier_rows is added to the form. Both the backend and the frontend script use this to store and retrieve the number of "rows".
      ToDo:
      Naturally, add the option to store the data in real repeaters when saving to pages. Do a lot of testing (and likely fixing). Make a few things (like the "Add row" button label etc.) configurable in field(set) context. Add a smooth API to retrieve the multiplied values as WireArrays. The mandatory moving screenshot: