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 OLSA
      Hello for all,
      ConfigurationForm fieldtype module is one my experiment from 2016.
      Main target to build this module was to store multiple setup and configuration values in just 1 field and avoid to use 1 db table to store just single "number of items on page", or another db table to store "layout type" etc. Thanks to JSON formatted storage this module can help you to reduce number of PW native fields in project, save DB space, and reduce number of queries at front-end.
      Install and setup:
      Download (at the bottom ), unzip and install like any other PW module (site/modules/...). Create some filed using this type of field (ConfigurationForm Fieldtype) Go to field setup Input tab and drag some subfields to container area (demo). Set "Name" and other params for subfields Save and place field to templates ("Action tab") How to use it:
      In my case, I use it to store setup and configurations values, but also for contact details, small content blocks... (eg. "widgets").
      Basic usage example:
      ConfigForm fieldtype "setup" has subfields:
      "limit", type select, option values: 5, 10, 15, 20
      "sort", type select, option values: "-date", "date",  "-sort", "sort"
      // get page children (items) $limit = isset($page->setup->limit) ? $page->setup->limit : 10; $sort = isset($page->setup->sort) ? $page->setup->sort : '-sort'; $items = $page->children("limit=$limit, sort=$sort");  
      Screenshots:


       
      Notes:
      Provide option to search inside subfields Provide multilanguage inputs for text and textarea field types Provide option for different field layout per-template basis Do not place/use field type "Button" or "File input" because it won't works. Please read README file for more details and examples Module use JSON format to store values. Text and textarea field types are multilanguage compatible, but please note that main target for this module was to store setup values and small content blocks and save DB space. Search part inside JSON is still a relatively new in MySQL (>=5.77) and that's on you how and for what to use this module.
      Thanks:
      Initial point for this fieldtype was jQuery plugin FormBuiled and thanks to Kevin Chappel for this plugin.
      In field type "link" I use javascript part from @marcostoll module and thanks to him for that part.
      Download:
      FieldtypeConfigForm.zip
      Edit: 14. August 2018. please delete/uninstall previously downloaded zip
      Regards.
         
    • By bernhard
      @Sergio asked about the pdf creation process in the showcase thread about my 360° feedback/survey tool and so I went ahead and set my little pdf helper module to public.
      Description from PW Weekly:
       
      Modules Directory: https://modules.processwire.com/modules/rock-pdf/
      Download & Docs: https://gitlab.com/baumrock/RockPdf
       
      You can combine it easily with RockReplacer: 
      See also a little showcase of the RockPdf module in this thread:
       
    • By bernhard
      WHY?
      This module was built to fill the gap between simple $pages->find() operations and complex SQL queries.
      The problem with $pages->find() is that it loads all pages into memory and that can be a problem when querying multiple thousands of pages. Even $pages->findMany() loads all pages into memory and therefore is a lot slower than regular SQL.
      The problem with SQL on the other hand is, that the queries are quite complex to build. All fields are separate tables, some repeatable fields use multiple rows for their content that belong to only one single page, you always need to check for the page status (which is not necessary on regular find() operations and therefore nobody is used to that).
      In short: It is far too much work to efficiently and easily get an array of data based on PW pages and fields and I need that a lot for my RockGrid module to build all kinds of tabular data.

      Basic Usage

       
      Docs & Download
      https://modules.processwire.com/modules/rock-finder/
      https://gitlab.com/baumrock/RockFinder/tree/master
       
      Changelog
      180810, v1.0.5, basic support for options fields 180528, v1.0.4, add custom select statement option 180516, change sql query method, bump version to 1.0.0 180515, multilang bugfix 180513, beta release <180513, preview/discussion took place here: https://processwire.com/talk/topic/18983-rocksqlfinder-highly-efficient-and-flexible-sql-finder-module/
    • By Thomas Diroll
      Hi guys I'm relatively new to PW and just finished developing a page for a client. I was able to include all necessary functionality using the core fieldtypes but now I it seems that I need to extend them with a custom one. What I need is a simple button, that copies the absolute url (frontend not PW-backend) of the page which is currently edited to the clipboard. As this feature is only needed inside a specific template, I tend to use a custom fieldtype which provides this feature. I've been looking inside the core modules code (eg. FieldtypeCheckbox.module) but I don't really get the structure of it and how its rendered to the admin page. I also didn't find a lot of tutorials covering custom fieldtypes.
      Maybe some of you could give me some tips on how to write a basic custom fieldtype that renders a button which copies the value of
      page->httpUrl() to the clipboard using JS. Thanks!
    • 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
      180730 support subdir installations 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: