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 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: