Jump to content
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

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Robin S
      A community member raised a question and I thought a new sanitizer method for the purpose would be useful, hence...
      Sanitizer Transliterate
      Adds a transliterate method to $sanitizer that performs character replacements as defined in the module config. The default character replacements are based on the defaults from InputfieldPageName, but with uppercase characters included too.
      Usage
      Install the Sanitizer Transliterate module.
      Customise the character replacements in the module config as needed.
      Use the sanitizer on strings like so:
      $transliterated_string = $sanitizer->transliterate($string);
       
      https://github.com/Toutouwai/SanitizerTransliterate
      https://modules.processwire.com/modules/sanitizer-transliterate/
       
    • By dimitrios
      Hello,
      this module can publish content of a Processwire page on a Facebook page, triggered by saving the Processwire page.
      To set it up, configure the module with a Facebook app ID, secret and a Page ID. Following is additional configuration on Facebook for developers:
      Minimum Required Facebook App configuration:
      on Settings -> Basics, provide the App Domains, provide the Site URL, on Settings -> Advanced, set the API version to 2.10, add Product: Facebook Login, on Facebook Login -> Settings, set Client OAuth Login: Yes, set Web OAuth Login: Yes, set Enforce HTTPS: Yes, add "http://www.example.com/processwire/page/" to field Valid OAuth Redirect URIs. This module is configurable as follows:
      Templates: posts can take place only for pages with the defined templates. On/Off switch: specify a checkbox field that will not allow the post if checked. Specify a message and/or an image for the post.
      Usage
      edit the desired PW page and save; it will post right after the initial Facebook log in and permission granting. After that, an access token is kept.
       
      Download
      PW module directory: http://modules.processwire.com/modules/auto-fb-post/ Github: https://github.com/kastrind/AutoFbPost   Note: Facebook SDK for PHP is utilized.


    • By thomasaull
      I created a little helper module to trigger a CI pipeline when your website has been changed. It's quite simple and works like this: As soon as you save a page the module sets a Boolean via a pages save after hook. Once a day via LazyCron the module checks if the Boolean is set and sends a POST Request to a configurable Webhook URL.
      Some ideas to extend this:
      make request type configurable (GET, POST) make the module trigger at a specified time (probably only possible with a server cronjob) trigger manually Anything else? If there's interest, I might put in some more functionality. Let me know what you're interested in. Until then, maybe it is useful for a couple of people 🙂
      Github Repo: https://github.com/thomasaull/CiTrigger
    • By Robin S
      I created this module a while ago and never got around to publicising it, but it has been outed in the latest PW Weekly so here goes the support thread...
      Unique Image Variations
      Ensures that all ImageSizer options and focus settings affect image variation filenames.

      Background
      When using methods that produce image variations such as Pageimage::size(), ProcessWire includes some of the ImageSizer settings (height, width, cropping location, etc) in the variation filename. This is useful so that if you change these settings in your size() call a new variation is generated and you see this variation on the front-end.
      However, ProcessWire does not include several of the other ImageSizer settings in the variation filename:
      upscaling cropping, when set to false or a blank string interlace sharpening quality hidpi quality focus (whether any saved focus area for an image should affect cropping) focus data (the top/left/zoom data for the focus area) This means that if you change any of these settings, either in $config->imageSizerOptions or in an $options array passed to a method like size(), and you already have variations at the requested size/crop, then ProcessWire will not create new variations and will continue to serve the old variations. In other words you won't see the effect of your changed ImageSizer options on the front-end until you delete the old variations.
      Features
      The Unique Image Variations module ensures that any changes to ImageSizer options and any changes to the focus area made in Page Edit are reflected in the variation filename, so new variations will always be generated and displayed on the front-end.
      Installation
      Install the Unique Image Variations module.
      In the module config, set the ImageSizer options that you want to include in image variation filenames.
      Warnings
      Installing the module (and keeping one or more of the options selected in the module config) will cause all existing image variations to be regenerated the next time they are requested. If you have an existing website with a large number of images you may not want the performance impact of that. The module is perhaps best suited to new sites where image variations have not yet been generated.
      Similarly, if you change the module config settings on an existing site then all image variations will be regenerated the next time they are requested.
      If you think you might want to change an ImageSizer option in the future (I'm thinking here primarily of options such as interlace that are typically set in $config->imageSizerOptions) and would not want that change to cause existing image variations to be regenerated then best to not include that option in the module config after you first install the module.
       
      https://github.com/Toutouwai/UniqueImageVariations
      https://modules.processwire.com/modules/unique-image-variations/
    • By Sebi
      I've created a small module which lets you define a timestamp after which a page should be accessible. In addition you can define a timestamp when the release should end and the page should not be accessable any more.
      ProcessWire-Module: http://modules.processwire.com/modules/page-access-releasetime/
      Github: https://github.com/Sebiworld/PageAccessReleasetime
      Usage
      PageAccessReleasetime can be installed like every other module in ProcessWire. Check the following guide for detailed information: How-To Install or Uninstall Modules
      After that, you will find checkboxes for activating the releasetime-fields at the settings-tab of each page. You don't need to add the fields to your templates manually.
      Check e.g. the checkbox "Activate Releasetime from?" and fill in a date in the future. The page will not be accessable for your users until the given date is reached.
      If you have $config->pagefileSecure = true, the module will protect files of unreleased pages as well.
      How it works
      This module hooks into Page::viewable to prevent users to access unreleased pages:
      public function hookPageViewable($event) { $page = $event->object; $viewable = $event->return; if($viewable){ // If the page would be viewable, additionally check Releasetime and User-Permission $viewable = $this->canUserSee($page); } $event->return = $viewable; } To prevent access to the files of unreleased pages, we hook into Page::isPublic and ProcessPageView::sendFile.
      public function hookPageIsPublic($e) { $page = $e->object; if($e->return && $this->isReleaseTimeSet($page)) { $e->return = false; } } The site/assets/files/ directory of pages, which isPublic() returns false, will get a '-' as prefix. This indicates ProcessWire (with activated $config->pagefileSecure) to check the file's permissions via PHP before delivering it to the client.
      The check wether a not-public file should be accessable happens in ProcessPageView::sendFile. We throw an 404 Exception if the current user must not see the file.
      public function hookProcessPageViewSendFile($e) { $page = $e->arguments[0]; if(!$this->canUserSee($page)) { throw new Wire404Exception('File not found'); } } Additionally we hook into ProcessPageEdit::buildForm to add the PageAccessReleasetime fields to each page and move them to the settings tab.
      Limitations
      In the current version, releasetime-protected pages will appear in wire('pages')->find() queries. If you want to display a list of pages, where pages could be releasetime-protected, you should double-check with $page->viewable() wether the page can be accessed. $page->viewable() returns false, if the page is not released yet.
      If you have an idea how unreleased pages can be filtered out of ProcessWire selector queries, feel free to write an issue, comment or make a pull request!
×
×
  • Create New...