Jump to content
adrian

Tracy Debugger

Recommended Posts

Just now, matjazp said:

Just wanted to upgrade her, but I got compile error: "Cannot declare class TracyDebugger, because the name is already in use", File: ...\modules\TracyDebugger\TracyDebugger.module.php:24  

I was worried that might happen. @bernhard added .php to the TracyDebugger.module file so that intellisense in vscode could work its magic. I thought I might starting adding the php extension to all my modules files because .module really is a silly extension in my mind. 

You'll be able to solve the issue my deleting the .module version. Same goes for ProcessTracyAdminer.module.

I am curious what method you used to upgrade. I would have thought that the PW Upgrades module would handle this and a git update approach should also work. Updating via modules > add new should also work. Did you just unzip and copy?

Share this post


Link to post
Share on other sites
2 minutes ago, matjazp said:

I used PW upgrades module...

Edit: Adminer 4.7.0 (released 2018-11-24)

Weird - I just tested upgrading Tracy with the PW Upgrades module and it deleted the old .module versions automatically. I have no idea why it wouldn't have worked the same for you.

Thanks for the Adminer update note.

Share this post


Link to post
Share on other sites
45 minutes ago, adrian said:

Well it took several hours of discussions with @bernhard and lots of back and forwards on the best way to do things, but we've finally committed the "WebHooks" panel he posted about above.

Awesome work @bernhard and @adrian. Hopefully one day I'll get to test all these wonderful stuff being added. That might be a while, given that it's only today that I discovered the Tracy console can be opened in a new window! 😁

  • Like 2

Share this post


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

I discovered the Tracy console can be opened in a new window!

Interesting because I actually purposely made this not obvious by hiding the icon that triggers the new window mode. Are you using SHIFT+Click to trigger this or is the icon not hidden for you?

The reason I "disabled" this functionality is that it was a bit painful to get layout to work properly in this mode. And actually, the Console panel is completely broken for me at the moment in this mode at the moment. Are you running a much older version?

Share this post


Link to post
Share on other sites
37 minutes ago, adrian said:

Are you using SHIFT+Click to trigger this or is the icon not hidden for you?

I'm using the icon; it's not hidden for me.

37 minutes ago, adrian said:

Are you running a much older version?

On this machine I'm running 4.8.24

38 minutes ago, adrian said:

Interesting because I actually purposely made this not obvious by hiding the icon that triggers the new window mode.

The new window came handy today. I needed to see different windows at the same time and docked, the console was in the way, plus I just couldn't make it bigger. I've done it before, but can't remember how :-).

  • Like 1

Share this post


Link to post
Share on other sites
58 minutes ago, kongondo said:

On this machine I'm running 4.8.24

That's ancient (10 months old) - you are missing out on so much 🙂 but that explains why the icon is not hidden.

58 minutes ago, kongondo said:

I just couldn't make it bigger. I've done it before, but can't remember how :-).

There are lots of new options for making the Console panel larger - you can maximize the panel, but you can also fullscreen mode the editor/results panes.

You can also "rollup" any Tracy panels by double-clicking on their title bar - nice to get it out of the way quickly.

I'll see about restoring the "window" option, but no promises - it's been painful!

 

Share this post


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

Edit: Adminer 4.7.0 (released 2018-11-24)

New version of Tracy includes 4.7.0

  • Like 3

Share this post


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

Weird - I just tested upgrading Tracy with the PW Upgrades module and it deleted the old .module versions automatically. I have no idea why it wouldn't have worked the same for you.

I experienced the same issue using the PW Upgrades module. I think it is Windows-specific and relates to a bug introduced by Ryan trying to resolve this issue: https://github.com/processwire/processwire-issues/issues/704
In recent dev versions PW is not able to delete files on Windows. See also: 

 

  • Like 3

Share this post


Link to post
Share on other sites
52 minutes ago, adrian said:

That's ancient (10 months old) - you are missing out on so much 🙂 but that explains why the icon is not hidden.

In fact I misspoke in my previous post. I've been using the new version but on a different local site. On the site I'm currently on, I have the older Tracy :-). 

52 minutes ago, adrian said:

There are lots of new options for making the Console panel larger

Yeah; now I seem to remember this. It was of course on the other site where I had the new Tracy. I even played around with Adminer, I recall. 

52 minutes ago, adrian said:

You can also "rollup" any Tracy panels by double-clicking on their title bar - nice to get it out of the way quickly.

Good to know, thanks.

  • Like 1

Share this post


Link to post
Share on other sites
5 minutes ago, kongondo said:
55 minutes ago, adrian said:

 

In fact I misspoke in my previous post. I've been using the new version but on a different local site

Does this mean you are seeing the "open in window" icon on the new version? It should look like this:

image.png.3fedeb8ea66afdad58a54df8e97b6baa.png

Just the Maximize/Restore icon and the close icon.

The open in window icon should be hid by this rule:

https://github.com/adrianbj/TracyDebugger/blob/077b5c26aea42de451dcd94d97ae186d3bbf8529/styles.css#L830-L833

Share this post


Link to post
Share on other sites
7 minutes ago, adrian said:

Does this mean you are seeing the "open in window" icon on the new version? It should look like this:

No. It means I'm using different versions of Tracy on different sites (multisite) on the same machine 😃.

 

Edit: Maybe this old version is why Tracy is not appearing in modal windows or that has always been the case?

Edited by kongondo
  • Like 1

Share this post


Link to post
Share on other sites

Adrian please save your time and forget about the open in new window stuff. The new options are much better!

Share this post


Link to post
Share on other sites

A couple of updates to the new RequestLogger panel.

You can now define which types of request methods are logged: GET, POST, PUT, DELETE, PATCH. By default, all are checked, but I think in most cases unchecking GET is probably helpful as it will prevent page views from being logged.

image.png.acef35a02d410f2d818bab775bdfe240.png

You can now use this panel on non-ProcessWire pages, so if you use a php script like payment_confirmation.php in the root of your site, so long as it bootstraps PW (include ./index.php), it will let you log and retrieve request data. The only catch is that you need to trigger the logging manually by adding:

$page->logRequests();

to the script file. 

Visit the page and enable logging (as with any normal PW page) and you're good to go.

The only weird thing at the moment with this is that the logged url will be /http404/ but otherwise it works as expected.

Let me know if you make use of this approach and if you find any issues.

BTW, I still need to add docs for the Request Logger, API Explorer, and Adminer panels to https://adrianbj.github.io/TracyDebugger/ - I've been slack on this. Anyone out there like doing documentation and would like to help 🙂

  • Like 2

Share this post


Link to post
Share on other sites
2 hours ago, adrian said:

BTW, I still need to add docs for the Request Logger, API Explorer, and Adminer panels to https://adrianbj.github.io/TracyDebugger/ - I've been slack on this. Anyone out there like doing documentation and would like to help 🙂

I could maybe do that for RequestLogger over christmas...

  • Like 2

Share this post


Link to post
Share on other sites

Hello to all,

I've just tried updating the module and got an error. I then deleted it completely to start all over again (on my local site), and as soon as it is downloaded, even if I choose to leave it uninstalled, I still have the same fatal error (I must delete the TracyDebugger folder in my modules completely to be able to access my site). Here's the error :

	require_once(): Failed opening required '/home/celfred/PlanetAlert/site/modules/TracyDebugger/panels/TemplateEditorPanel.php' (include_path='.:/usr/share/php')
	

And I'm sorry to say I have no idea what to do... So if one of you could give me a hint, that would be great. I was using TracyDebugger more and more (for minor debugging, I guess you can tell from my question) but I would like to use it more 🙂 

Share this post


Link to post
Share on other sites

@celfred - does that file actually exist?

How are you upgrading / installing Tracy ? It's always safest through Setup > Modules > New or the PW Upgrades module.

Also, if it's uninstalled and you're getting that error, then you probably need to do a Modules > Refresh

Share this post


Link to post
Share on other sites

@adrian : Well, I am upgrading through Setup > Modules > New and I type the className. Everything downloads and then I click 'Install now'.

I've checked the path and no, the file doesn't exist.

I've tried the Modules > Refresh and re-installed Tracydebugger : same problem. Here's the line mentionned that triggers the issue :

	File: .../modules/TracyDebugger/TracyDebugger.module.php:1341
	

Thanks for your quick reply.

Edit : I've checked on Github in panels folder, and there is no TemplateEditorPanel.php file... I really don't get it...

Share this post


Link to post
Share on other sites
58 minutes ago, celfred said:

@adrian : Well, I am upgrading through Setup > Modules > New and I type the className. Everything downloads and then I click 'Install now'.

I've checked the path and no, the file doesn't exist.

I've tried the Modules > Refresh and re-installed Tracydebugger : same problem. Here's the line mentionned that triggers the issue :


	File: .../modules/TracyDebugger/TracyDebugger.module.php:1341
	

Thanks for your quick reply.

Edit : I've checked on Github in panels folder, and there is no TemplateEditorPanel.php file... I really don't get it...

Oh now I see what's going on - the Template Editor panel hasn't existed in forever 🙂 Your module settings must be configured to try to load it still. An uninstall/reinstall should remove those settings though. Maybe you had used the Panel Selector and "Sticky" selected the template editor? Could you please delete the "tracyPanelsSticky" cookie from your browser and let me know if that works.

Share this post


Link to post
Share on other sites

@celfred - I just committed a new version that won't error even if there are old settings with panels that no longer exist, so please try updating and let me know how you go.

Share this post


Link to post
Share on other sites

@adrian I was indeed about to tell you I'm updating from... 3.6.9 ! I managed to get back the old version from my remote site).

So far, I've tried what you said :

  • Starting with a 'regular' update trhough the module page, clicking on update. It detects the 4?15.4 version. It downloads and then still triggers the same error.
  • Then, I went to check the cookies. I couldn't find the TracyPanelSticky you mentionned, but trying to erase all Tracy cookies (and eventually deleting all my localhost cookies), and also deleting the TracyDebugger folder in my modules folder, and deleting the TracyDebugger folder in my assets/cache/Filecompiler/site/modules... still the same result 😞 In short, I have deleted all traces I could find of TracyDebugger and tried re-installing 4.15.4 but the error persists.

You were perfectly right about the 'sticky panel' : I remember I had the var-dump panel sticky before updating.

Thanks a lot for your help.

Share this post


Link to post
Share on other sites

@celfred - sorry, looks like I forgot to commit that new 4.15.5 version - please try updating now - this new version should prevent the error.

  • Thanks 1

Share this post


Link to post
Share on other sites

I updated PW from 3.0.111 to 3.0.121 today.

I've got a compile error when I wanted to update Tracy as well:

File: .../modules/TracyDebugger/TracyDebugger.module.php:24
class TracyDebugger extends \ProcessWire\WireData implements \ProcessWire\Module, \ProcessWire\ConfigurableModule {

https://dev.foo.com/backstage/module/download/
PHP 7.2.12
Apache/2.4
Tracy 2.5-dev


tracy-error-exception.png.57db11b8bec6e4550f99abe95a2c662a.png

Edited by dragan
added screenshot

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