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

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

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 gebeer
      I am happy to present my new fieldtype FieldtypeImageFromPage. It is made up of 2 modules:
      Fieldtype Image Reference From Another Page is a Fieldtype that stores a reference to a single image from another page. The image can be selected with the associated Inputfield.
      Inputfield Select Image From Page is an Inputfield to select a single image from images on a predefined page and it's children.
      And there also is a helper module that takes care of cleanup tasks.
      This module evolved out of a discussion about my other Module FieldtypeImagePicker.  It caters for use cases where a set of images is being reused multiple times across a site. With this fieldtype these images can be administered through a chosen page. All images uploaded to that page will be available in the inputfield.
      When to use ?
      Let editors choose an image from a set of images that is being used site-wide. Ideal for images that are being re-used across the site.
      Suited for images that are used on multiple pages throughout the site (e.g. icons).
      Other than the native ProcessWire images field, the images here are not stored per page. Only references to images on another page are stored. This has several advantages:
      one central place to organize images when images change, you only have to update them in one place. All references will be updated, too. (Provided the name of the image that has changed stays the same) Features
      Images can be manipulated like native ProcessWire images (resizing, cropping etc.) Image names are fully searchable through the API Accidental image deletion is prevented. When you want to delete an image from one of the pages that hold your site-wide images, the module searches all pages that use that image. If any page contains a reference to the image you are trying to delete, deletion will be prevented. You will get an error message to help you edit those pages and remove references there before you can finally delete the image. How to install and setup
      Download and install this module like any other modules in ProcessWire Create a page in the page tree that will hold your images. This page's template must have an images field Upload some images to the page you created in step 2 Create a new field. As type choose 'Image Reference From Another Page'. Save the field. In 'Details' Tab of the field choose the page you created in step 2 Click Save button Choose the images field name for the field that holds your images (on page template from step 2) Click Save button again Choose whether you want to include child pages of page from step 2 to supply images Add the field to any template You are now ready to use the field View of the inputfield on the page edit screen:

      View of the field settings

      The module can be installed from this github repo. Some more info in the README there, too.
      In my tests it was fairly stable. After receiving your valued feedback, I will eventually add it to the modules directory.
      My ideas for further improvement:
      - add ajax loading of thumbnails
      Happy to hear your feedback!
       
    • By gebeer
      Although the PW backend is really intuitive, ever so often my clients need some assistance. Be it they are not so tech savvy or they are not working in the backend often.
      For those cases it is nice to make some help videos available to editors. This is what this module does.
      ProcessHelpVideos Module
      A Process module to display help videos for the ProcessWire CMS. It can be used to make help videos (screencasts) available to content editors.
      This module adds a 'Help Videos" section to the ProcessWire backend. The help videos are accessible through an automatically created page in the Admin page tree. You can add your help videos as pages in the page tree. The module adds a hidden page to the page tree that acts as parent page for the help video pages. All necessary fields and templates will be installed automatically. If there are already a CKEditor field and/or a file field for mp4 files installed in the system, the module will use those. Otherwise it will create the necessary fields. Also the necessary templates for the parent help videos page and it's children are created on module install. The module installs a permission process-helpvideos. Every user role that should have access to the help video section, needs this permission. I use the help video approach on quite a few production sites. It is stable so far and well received by site owners/editors. Up until now I installed required fields, templates and pages manually and then added the module. Now I added all this logic to the install method of the module and it should be ready to share.
      The module and further description on how to use it is available on github: https://github.com/gebeer/ProcessHelpVideos
      If you like to give it a try, I am happy to receive your comments/suggestions here.
    • By Robin S
      A module created in response to the topic here:
      Page List Select Multiple Quickly
      Modifies PageListSelectMultiple to allow you to select multiple pages without the tree closing every time you select a page.
      The screencast says it all:

       
      https://github.com/Toutouwai/PageListSelectMultipleQuickly
      https://modules.processwire.com/modules/page-list-select-multiple-quickly/
    • By gebeer
      Hello all,
      sharing my new module FieldtypeImagePicker. It provides a configurable input field for choosing any type of image from a predefined folder.
      The need for it came up because a client had a custom SVG icon set and I wanted the editors to be able to choose an icon in the page editor.
      It can also be used to offer a choice of images that are used site-wide without having to upload them to individual pages.
      There are no image manipulation methods like with the native PW image field.
      Module and full description can be found on github https://github.com/gebeer/FieldtypeImagePicker
      Kudos to @Martijn Geerts. I used his module FieldTypeSelectFile as a base to build upon.
      Here's how the input field looks like in the page editor:

      Hope it can be of use to someone.
      If you like to give it a try, I'm happy to hear your comments or suggestions for improvement. Eventually this will go in the module directory soon, too.
    • 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://github.com/BernhardBaumrock/RockPDF
       
      You can combine it easily with RockReplacer: 
      See also a little showcase of the RockPdf module in this thread:
       
×
×
  • Create New...