adrian

Tracy Debugger

Recommended Posts

Hey @bernhard - sorry for the recent silence. I am back in the office this week, but triaging work stuff first. Will try to take a good look at your other suggestions as soon as I can.

Regarding disabling Tracy on certain pages, that is what the "No debug bar in selected templates" setting is for. It seems to work fine here - is it not working for you?

That said, I can also see having a tracy=0 get variable as a useful addition for sure. I'll add that soon. 

Regarding the performance issue - could you narrow down which panel is the cause? I am constantly on the lookout for ways to improve performance, so it would be helpful if I could reproduce to see if something can be improved.

Share this post


Link to post
Share on other sites

Actually thinking about this a little more - maybe the disabler should be turned into a panel with more options:

1) Disable Tracy all pages

2) Disable Tracy this page

And have Once and Sticky buttons to determine how long it's disabled for.

How does this sound compared to the get variable approach?

  • Like 1

Share this post


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

How does this sound compared to the get variable approach?

Of course this sounds better, but I'd also be happy with the get variable. Disable tracy on some templates does not work in my case because I'm developing process modules. So maybe the "disable tracy for selected templates" option could also be moved to this panel and away from the module settings (they are getting more and more complex 🙂 ).

So it totally depends on you and your spare time and if you think you'd also benefit from such a feature. Again: In my case the get var would be sufficient and I guess this would be a lot easier to implement.

Thanks and welcome back 😉

  • Like 2

Share this post


Link to post
Share on other sites

Hey @bernhard - regarding your fd() idea - is there a major difference between it and using l() which already dumps to Tracy log files?

  • Like 1

Share this post


Link to post
Share on other sites

Hi, in a new PW install after install the Tracy module and enable the "Development" mode I get strange responses from the site:

- On the frontend after clicking on a link the site stays processing and after a while gives a 404 page
- On the admin the site stays processing for a while and is slow.

I need to select the "Production" mode for the site to able to work. This is strange, the module never had this behaviour.

The installation is using:

- Processwire 3.0.98
- Tracy Debugger v4.10.22

Right now I do not know if there a module conflict or configuration that is making this behaviour.

Thank you

  • Like 1

Share this post


Link to post
Share on other sites

Hi @vmo - sorry I don't have any idea why you'd be getting a 404. Can you try unchecking all panels via the Panel Selector and see if that helps. Also, do older versions of Tracy work any better?

Is this a local or server install? What OS are you running? Apache or Nginx?

Could you try another install on the same server?

Could you try the Module Disabler panel to disable all other modules to see if there is a conflict?

Share this post


Link to post
Share on other sites

Hi, @adrian - the installation is on a cpanel with Apache. The installation is a basic one with a few fields and templates (with no page) and with no modifications done to the original template files.
I copied the installation with the issue to another sub-domain and did the following actions:

- Disabled all extra site modules
- Removed all the custom templates and fields
- Only enabled the Tracy module in DEVELOPMENT mode (with no errors and 404 pages)
- With the Tracy in DEVELOPMENT mode: I reenabled all the others extra site modules one by one and tested for any errors, delays or 404 pages
- After reenabled all the modules no errors, delays or 404 pages were detected.
- Recreated the custom templates
- Recreated the custom fields

After this actions there wasn't datect any issue, but... after added a repeater field to the "home" template the same issue appeared
and started again to receive 404 pages and delayed page processing on the admin.

I did the following steps to try understand if there was any issue on the repeater field:

On the "home" template:
- Removed the repeater field from the "home" template
- After field was removed, No 404 errors were detected navigating the site
- Added again the repeater field to the "home" template and the same issue started
- Removed the field

On the "basic-page" template:
- Added the field to the "basic-page" template
- After added the repeater field to the "basic-page" template, no 404 errors were detected navigating in the site


Any ideia?
I can make a zip of the installation and send it to you, if it helps.

  • Like 1

Share this post


Link to post
Share on other sites

Hi @vmo - thanks for the hard work narrowing it down to repeaters on the homepage. I have no idea why though at this point. I think the one thing you missed in your debugging was unchecking all the debugbar panels. It would be helpful to know if that helps. If it does, try to narrow it down it a particular panel - most likely the RequestInfo panel. If that doesn't help, then sure send me the zip - I might not have time to look for a little while though.

  • Like 1

Share this post


Link to post
Share on other sites
Posted (edited)

Hi @adrian - After disabled the "RequestInfo panel" on the frontend panels stop receiving the 404 errors

and after disabled the "RequestInfo panel" on the backend panels the admin navigation and save is normal, does not delay.

Any next steps?

Thank you

Edited by vmo
  • Like 2

Share this post


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

Any next steps?

I guess it's a matter of figuring out what part of that panel is causing the problem. It will most likely be the "Field List & Values" section. So you could try disabling that section only in the module config settings. If everything is still fine with the panel enabled, but that section disabled, then we need to figure out what bit of code in that section is causing the problem. Here's the code for that section: https://github.com/adrianbj/TracyDebugger/blob/2689b8ccc57bd5776a21cf6413a400c68d71a555/panels/RequestInfoPanel.php#L450-L473

In particular I would recommend looking through the getFieldArray() method that it calls. 

If you feel up to investigating the cause, that would be greatly appreciated. Otherwise, I will need to get some more details about that repeater field, because I have many sites with lots of repeater fields and haven't noticed a problem, so would need to be able to reproduce to debug.

Thanks for your help so far.

Share this post


Link to post
Share on other sites

Hi @adrian - thank you for the hints to research the issue.

I just disabled the "Fields Object" on the Request Info Panel > Panel sections and the issue of the 404 does not appear.

I will take time to debug it but right now I need to put everything working for tomorrow and I will give feedback asap.

Thank you, all the best

  • Like 1

Share this post


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

I just disabled the "Fields Object" on the Request Info Panel > Panel sections and the issue of the 404 does not appear.

Good to know - I haven't enabled that section in my RequestInfo panel in forever - I guess that's why I am not seeing the issue with repeater fields.

Thanks for narrowing it down.

Share this post


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

Good to know - I haven't enabled that section in my RequestInfo panel in forever - I guess that's why I am not seeing the issue with repeater fields.

 Thanks for narrowing it down.

Thanks, that is really good to know, I will keep it disabled. Done for now. Will try to debug it asap.

All the best

  • Like 2

Share this post


Link to post
Share on other sites

Hi @adrian,

I'm still experiencing the issue below in the latest Tracy:

I can fix it with the CSS I mentioned earlier...

...but it would be handy to have that as an option built into the module so no custom CSS is needed. Thanks!

  • Like 2

Share this post


Link to post
Share on other sites

Hey @Robin S - I have been experiencing this again too. I though it was solved in some Tracy core updates, but apparently not 🙂

I tend to agree with you that there really isn't a need to move the bar, so I think a fixed option is probably a good idea, so I have added it in the latest version - the option is called: "Fixed Position". You might need a hard reload after changing this to see the effects.

This version also includes some more MySQL info in the Diagnostics panel. It's all about the current number of connections etc:

image.thumb.png.73e43c446e09d878b28df609cc772060.png

 

  • Like 4

Share this post


Link to post
Share on other sites

Hi! I always used Tracy Debugger. Now on a fresh installation, based on the Multilanguage version, i installed the Tracy Debugger module, but it doesn't show on the frontend! Idea? All the options seems right...

Share this post


Link to post
Share on other sites

HI @pandaman - I really don't have any idea why it wouldn't be showing up. I use it on Multilanguage installs regularly. Does it show on the backend, or not at all?

Are you on a local dev setup? If not, make sure that Force Superuser into Development mode is checked, or force the Output Mode to Development.

Are there any JS errors in the browser dev console?

 

Share this post


Link to post
Share on other sites

Hi @adrian

A feature request for your consideration: please could you apply the lovely code editor to the custom PHP textarea in the module settings? Would make editing custom PHP much easier.

Many thanks for your consideration!
Steve

  • Like 2

Share this post


Link to post
Share on other sites
On 7/29/2018 at 2:23 PM, netcarver said:

Hi @adrian

A feature request for your consideration: please could you apply the lovely code editor to the custom PHP textarea in the module settings? Would make editing custom PHP much easier.

Many thanks for your consideration!
Steve

Hi Steve,

Thanks for the suggestion. I have added it to the just released version. Please let me know if you have any issues with it.

PS - I am curious what you are using this panel for - I haven't had much feedback on it thus far.

  • Like 2

Share this post


Link to post
Share on other sites

@adrian Thank you. I was putting together a version-gathering script to collect the data to paste, as Markdown, into GitHub issues - then guess what I found elsewhere in TD 🤔

  • Like 1

Share this post


Link to post
Share on other sites

@adrian Thanks for the update - just tried it - but the value of the field no longer seems to save. Whatever I enter into the custom PHP code editor is lost on submit of the module settings.

  • Like 1

Share this post


Link to post
Share on other sites

Glad you found the "Version's List" functionality - pretty handy isn't it 🙂 Let me know if you think of any other info that should be added to it.

Sorry about the code saving bug - hope you didn't lose too much! It is fixed in the latest commit.

  • Like 1

Share this post


Link to post
Share on other sites

@adrian Thanks, that's fixed it, and nothing lost.

While you have this feature in your working memory, another request: could you have the config scroll to the custom PHP field if it were changed on the last save? That would allow a smoother flow of iterations using the field, and shouldn't interfere with anyone else's use of the config area. That would be the icing on the cake, but I'm totally happy with the cake the way it is at the moment 🙂

---

With regard to the Version List functionality, if anything, I think a "lite" version for initial reporting of just the PW, PHP, Webserver & MySQL versions as a markdown table would be useful. One thing that's struck me reading through the issues is that clarity matters. I really like the comprehensive data you've made available with the existing feature - but I completely missed the data, tucked away at the bottom of a couple of issues. It was only when I found the feature in Tracy that I had a lightbulb moment and realised that's where those three lines in the issue reports came from. (I like to follow the KISBIS rule where possible: Keep It Simple, Because I'm Stupid)

  • Like 2

Share this post


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

While you have this feature in your working memory, another request: could you have the config scroll to the custom PHP field if it were changed on the last save? That would allow a smoother flow of iterations using the field, and shouldn't interfere with anyone else's use of the config area.

Check out the latest version - I think it works pretty nicely!

 

1 hour ago, netcarver said:

With regard to the Version List functionality, if anything, I think a "lite" version for initial reporting of just the PW, PHP, Webserver & MySQL versions as a markdown table would be useful.

Happy to implement, but not sure the best interface - are you thinking about maybe splitting the the button into two: 

1) Copy Simple for Github

2) Copy Detailed for Github


Or do you have other ideas?

  • Like 1

Share this post


Link to post
Share on other sites

@adrian Fantastic! Thank-you, that works great.

Regarding the "Lite" reporting button idea; I'd gather a few more opinions on this before doing anything.

For example, another alternative is to just keep the existing button but make the basics a non-collapsed table with all the additional details in the collapsed sections following it. That would make the basics stand out pretty well in the issue reports.

 

  • Like 2

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 BitPoet
      MediaLibrary
      Update: MediaLibrary can now be found in the official module list.
      Out of necessity, I've started to implement a simple media library module.
      The basic mechanism is that it adds a MediaLibrary template with file and image fields. Pages of this type can be added anywhere in the page tree.
      The link and image pickers in CKEditor are extended to allow quick selection of library pages from dropdowns. In the link picker this happens in the MediaLibrary tab, where you can also see a preview of the selected image. In the image picker, simply select a library from the dropdown at the top, everything else is handled by standard functionality.
      I've put the code onto github. This module is compatible with ProcessWire 3.
      Steps to usage:
      Download the module's zip from github (switch to the pw3 branche beforehand if you want to test on PW 3.x) and unpack it into site/modules Click "Modules" -> "Refresh" in the admin Click "Install" for MediaLibrary For testing, create a page with the MediaLibrary template under home (give it an expressive title like 'Global Media') and add some images and files Edit a differnt page with a CKEditor field and add a link and an image to see the MediaLibrary features in action (see the screencap for details) Optionally, go into the module settings for MediaLibrary Note: this module is far from being as elaborate as Kongondo's Media Manager (and doesn't plan to be). If you need a feature-rich solution for integrated media management, give it a look.
      Feel free to change the settings for MediaFiles and MediaImages fields, just keep the type as multiple.
      There are some not-so-pretty hacks for creating and inserting the correct markup, which could probably be changed to use standard input fields, though I'm a bit at a loss right now how to get it to work. I've also still got to take a look at error handling before I can call it fit for production. All feedback and pointers are appreciated (that's also why I post this in the development section).

      Edit 09.03.2016 / version 0.0.4: there's now also a "Media" admin page with a shortcut to quickly add a new library.

      Edit 01.05.2016:
      Version 0.0.8:
      - The module now supports nested media libraries (all descendants of eligible media libraries are also selectable in link/image picker).
      - There's a MediaLibrary::getPageMediaLibraries method you can hook after to modify the array of available libraries.
      - You can switch between (default) select dropdowns or radio boxes in the module configuration of MediaLIbrary to choose libraries.
      Edit 10.10.2018:
      Version 0.1.3:
      - Dropped compatibility for ProcessWire legacy versions by adding namespaces
      - Allow deletion of libraries from the Media overview admin page
      - Added an option to hide media libraries from the page tree (optionally also for superusers)
    • By Robin S
      This module corrects a few things that I find awkward about the "Add New Template" workflow in the PW admin. I opened a wishlist topic a while back because it would good to resolve some of these things in the core, but this module is a stopgap for now.
      Originally I was going to share these as a few standalone hooks, but decided to bundle them together in a configurable module instead.
      Add Template Enhancements
      A module for ProcessWire CMS/CMF. Adds some efficiency enhancements when adding or cloning templates via admin.

      Features
      Derive label from name when new template added: if you like to give each of your templates a label then this feature can save some time. The label can be added automatically when templates are added in admin, in admin/API, or not at all. There are options for underscore/hyphen replacement and capitalisation of the label. Edit template after add: when adding only a single template, the template is automatically opened for editing after it is added. Copy field contexts when cloning: this copies the field contexts (a.k.a. overrides such as column width, label and description) from the source template to the new template when using the "Duplicate/clone this template?" feature on the Advanced tab. Copy field contexts when duplicating fields: this copies the field contexts if you select the "Duplicate fields used by another template" option when adding a new template. Usage
      Install the Add Template Enhancements module.
      Configure the module settings according to what suits you.
       
      https://github.com/Toutouwai/AddTemplateEnhancements
      https://modules.processwire.com/modules/add-template-enhancements/
    • By Mike Rockett
      As I mentioned in this issue, I've create a new textformatter for ParsedownExtraPlugin, which adds some oomph to your markdown.
      Repo: Parsedown Extra Plugin
      Unlike the built-in textformatter for Parsedown and Parsedown Extra, this should be used when you want to use Extra with additional configuration/customisation.
      Some examples:
      ### Test {.heading} - A [external link](https://google.com/){.google} with `google` as a class that opens in a new tab if the config property is set. - [Another link](/page){target=_blank} that opens in a new tab even though it isn't external. ```html .html <p>Test</p> ``` There's some config options available to you, such as setting attributes on all/external images and links, setting table and table-cell alignment classes, adjusting footnote classes and IDs, adding <code> attributes to their parent <pre> elements, and changing the <code> class if your syntax highlighter does not use language-*.
      I was thinking about adding the ability to make links open in a new tab by appending a plus to the link syntax, but only external links should be opening in a new tab anyway. Further, this would add extra, unnecessary processing time.
      Please let me know if you bump into any problems. ☺️
    • By Mike Rockett
      TextformatterTypographer (0.4.0 Beta)
      A ProcessWire wrapper for the awesome PHP Typography class, originally authored by KINGdesk LLC and enhanced by Peter Putzer in wp-Typography. Like Smartypants, it supercharges text fields with enhanced typography and typesetting, such as smart quotations, hyphenation in 59 languages, ellipses, copyright-, trade-, and service-marks, math symbols, and more.
      Learn more on my blog
      It's based on the PHP-Typography library found over at wp-Typography, which is more frequently updated and feature rich that its original by KINGdesk LLC.
      The module itself is fully configurable. I haven't done extensive testing, but there is nothing complex about this, and so I only envisage a typographical bug here and there, if any.
      Please do test it out and let me know what you think.
      Also note that I have indicated support for PW 2.8, but I haven't tested there as yet. This was built on PW 3.0.42/62.
    • By Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.50
      Jumplinks is an enhanced version of the original ProcessRedirects by Antti Peisa.
      The Process module manages your permanent and temporary redirects (we'll call these "jumplinks" from now on, unless in reference to redirects from another module), useful for when you're migrating over to ProcessWire from another system/platform. Each jumplink supports wildcards, shortening the time needed to create them.
      Unlike similar modules for other platforms, wildcards in Jumplinks are much easier to work with, as Regular Expressions are not fully exposed. Instead, parameters wrapped in curly braces are used - these are described in the documentation.
      Under Development: 2.0, to be powered by FastRoute
      As of version 1.5.0, Jumplinks requires at least ProcessWire 2.6.1 to run.
      View on GitLab
      Download via the Modules Directory
      Read the docs
      Features
      The most prominent features include:
      Basic jumplinks (from one fixed route to another) Parameter-based wildcards with "Smart" equivalents Mapping Collections (for converting ID-based routes to their named-equivalents without the need to create multiple jumplinks) Destination Selectors (for finding and redirecting to pages containing legacy location information) Timed Activation (activate and/or deactivate jumplinks at specific times) 404-Monitor (for creating jumplinks based on 404 hits) Additionally, the following features may come in handy:
      Stale jumplink management Legacy domain support for slow migrations An importer (from CSV or ProcessRedirects) Feedback & Feature Requests
      I’d love to know what you think of this module. Please provide some feedback on the module as a whole, or even regarding smaller things that make it whole. Also, please feel free to submit feature requests and their use-cases.
      Note: Features requested so far have been added to the to-do list, and will be added to 2.0, and not the current dev/master branches.
      Open Source

      Jumplinks is an open-source project, and is free to use. In fact, Jumplinks will always be open-source, and will always remain free to use. Forever. If you would like to support the development of Jumplinks, please consider making a small donation via PayPal.
      Enjoy!