adrian

Tracy Debugger

Recommended Posts

@celfred - any chance this site is on a live server somewhere and you could give me access to figure out what is going on. 

PS Are you running the latest version of Tracy?

Share this post


Link to post
Share on other sites

@adrian Thanks for your reply. My site is at http://planetalert.tuxfamily.org . I have just installed TracyDenugger there. It doesn't appear but from what I've read in the settings, that's normal, everything is stored in log files. Ok, but how do I give you access to useful things (admin access?). Sorry if you feel like I'm messing things up and being a nuisance...

Actually, I've just tested 1 thing : forcing the DEV mode so I can see Tracy's bar. I saw the 'Processwire Debug Panel' and clicked on the 'Pages loaded' link, and it went to my 404 page like I said... I turned the setting back to DETECT. Feel free to tell me if you want me to do some things or to private message you some logs or whatever...

Edit : PM sent. Thank you so much.

Share this post


Link to post
Share on other sites

@celfred - I would need superuser access to the site to be able to test the issue of the pages loaded going to the 404 and also the issue of it appearing in the backend when not checked. Don't worry, you can trust me :) Obviously PM the login details.

Share this post


Link to post
Share on other sites

Thanks @adrian that's exactly what I was asking for.  I like the configuration as well.

I upgraded Tracy on two local sites, one site works correctly on the frontend and backend.  The other site doesn't show the toggle on the frontend, it works fine on the backend.  I'm not sure why yet.  I have tried uninstall/reinstalling the module.  I tried clearing the browser caches.  I tried refreshing the PW modules.  All I see on the frontend is the old Tracy debug bar.

Do you have any ideas what is causing this?

  • Like 1

Share this post


Link to post
Share on other sites
10 minutes ago, gmclelland said:

Thanks @adrian that's exactly what I was asking for.  I like the configuration as well.

I upgraded Tracy on two local sites, one site works correctly on the frontend and backend.  The other site doesn't show the toggle on the frontend, it works fine on the backend.  I'm not sure why yet.  I have tried uninstall/reinstalling the module.  I tried clearing the browser caches.  I tried refreshing the PW modules.  All I see on the frontend is the old Tracy debug bar.

Do you have any ideas what is causing this?

Are there any JS errors in the console for the frontend of the site where it isn't working? I am replacing the old close button with the hide button via JS so maybe there would be some clues there? Can you point me to the site?

 

Share this post


Link to post
Share on other sites

No js errors in the console.  Tried in different browsers as well.  I see the old 'X' button, I just don't see the new toggle button.  Sorry, the site is local.  I'll keep looking into it.

Home 2017-01-18 09-39-03.jpg

 

  • Like 1

Share this post


Link to post
Share on other sites

The site that is having a problem is using the Twig template engine using https://github.com/wanze/TemplateEngineFactory and https://github.com/wanze/TemplateEngineTwig.

I wonder if it is because the TracyDebugger module is using a hook to add the javascript?  I'm not very familiar with hooks, but maybe the hook doesn't run after Twig has compiled the markup?

  • Like 1

Share this post


Link to post
Share on other sites

Just as a follow-up in case people wonder, here's a copy of the message I sent to @adrian
 

Quote

 

I'm still struggling !!!

Here's what I have so far : In my head.inc, I had those lines (I can't remember why I needed them, really...)


$whitelist = array('127.0.0.1', 'localhost');
if(!in_array($_SERVER['REMOTE_ADDR'], $whitelist)){
   // Remote server
   echo "<base href='/index.html'>";
 } else {
   // Localhost
   echo "<base href='/PlanetAlert/index.html'>";
 }

 I commented them out on localhost and Tracy works as expected ! Thanks for your help !

Now I'll check later if I can comment these lines out on live site ;) And I'm gonna dig this Teams page but that will be for my other post on 'Optimisation' :)

Thanks again !

 

 

  • Like 1

Share this post


Link to post
Share on other sites

Ok, on line 294 of TracyDebugger.module, I changed it to

$this->addHookAfter('Page::render', $this, 'addCustomStuff', array('priority'=>'100.7'));

After I did this, I started seeing the toggle link on the frontend.

The templateEngineFactory module (Page::render() TemplateEngineFactory::hookRender()) had a priority of 100.5.  TracyDebugger had a priority of 100.4, so it ran too early.

What do you think is the best way to fix this?

 

  • Like 1

Share this post


Link to post
Share on other sites

@gmclelland - thanks for helping to track that down!

I think that 100.5 priority in TemplateEngineFactory is being set automatically. I am honestly not sure the best way to approach fixing this. The most guaranteed would probably be if I manually set it to say 1000, to make sure it is after any other hooks that might also manually set the priority to a high value. I guess I'll do that for now. There are actually a few Page::render hooks used in Tracy, so I will take care of those as well because I feel like TemplateEngineFactory will be breaking those as well.

Thanks again!

Share this post


Link to post
Share on other sites

@gmclelland and everyone.

Latest version takes care of the hook priority issue and adds a new feature to the new hide/show toggle button.

Now if you have it hidden and it detects an error it will force it to display. Once you fix the error, it will go back to being hidden again. I think this is a nice compromise for those who don't like having the debug bar visible all the time, but don't want to miss any reported notices/warnings.

Please let me know if you notice any problems with this change.

  • Like 3

Share this post


Link to post
Share on other sites

@adrian - Thanks for adding that new feature.  I just tested the new version and noticed a few of issues.

1. I don't think the "Hide debug bar by default" setting is working for me anymore.  I swear it was working before.  Now, the debug bar always shows expanded when enabled on the frontend or backend.

2. Maybe add checkboxes for a "Hide debug bar by default on the frontend" and "Hide debug bar by default on the backend" settings?

3. I don't think the padding got applied to the toggle when the bar is in a collapsed state when viewed on the backend.  I'm using the default admin theme.  You can see this by toggling the bar.  The height of the toggle button doesn't match the height of the debug bar.  It looks fine on the frontend though.

Share this post


Link to post
Share on other sites

Nevermind about  #1. I see that works properly.  I was assuming that it would be collapsed by default on every page load.  The actual behavior is that it remembers if it was opened or closed and stays that way between page loads.

  • Like 1

Share this post


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

1. I don't think the "Hide debug bar by default" setting is working for me anymore.  I swear it was working before.  Now, the debug bar always shows expanded when enabled on the frontend or backend.

Once you have clicked to show it, a cookie is set which overrides the config setting. Or is this because there are errors in the errors panel, which as I mentioned now forces it to display, which I think is a good idea, but can revisit/make configurable if you needs don't like it.
 

2 minutes ago, gmclelland said:

2. Maybe add checkboxes for a "Hide debug bar by default on the frontend" and "Hide debug bar by default on the backend" settings?

I know I already have a lot of settings, but I feel like this might be going a little too far :) especially given how easy it is to toggle.
 

4 minutes ago, gmclelland said:

3. I don't think the padding got applied to the toggle when the bar is in a collapsed state when viewed on the backend.  I'm using the default admin theme.  You can see this by toggling the bar.  The height of the toggle button doesn't match the height of the debug bar.  It looks fine on the frontend though.

It looks the same to me both front and backend. Perhaps you have extra padding on the frontend due to some css cascading down? Could you maybe post some comparison screenshots and/or debug the css to see what might be conflicting.

Thanks.

Share this post


Link to post
Share on other sites

It's a subtle difference that can only be seen when toggling back and forth.

Here is the frontend

frontend.gif

 

Here is the backend

backend.gif

  • Like 1

Share this post


Link to post
Share on other sites
Now if you have it hidden and it detects an error it will force it to display. 

How about extending it to bd() calls too?

Share this post


Link to post
Share on other sites
3 hours ago, tpr said:

Now if you have it hidden and it detects an error it will force it to display. 

How about extending it to bd() calls too?

Not sure about this - I like your thinking, but then where do I stop? Do I extend it even further to display if there is a new PW or Logs panel item? What about a new Mail panel or Page recorder entry?

I think perhaps that manually triggered things shouldn't automatically unhide the bar because you know you've added the call so you will be looking for an entry on the bar. If anything I think maybe the logs panels should maybe trigger display of the bar if they are error related entries.

As always though I am open to feedback if others think this change would be good.

Share this post


Link to post
Share on other sites

To fix the toggle button height and width jumping, I had to add the following to #show-button:

box-sizing: border-box;
line-height: normal;
padding: 4px 15px 2px 6px !important;
width: 16px !important;

So all together it looks like this:

#show-button {
    bottom: 0;
    right: 0;
    z-index: 99999;
    position: fixed;
    width: 16px !important;
    margin: 0 !important;
    padding: 4px 15px 2px 6px !important;
    background: #FFFFFF !important;
    border: 1px solid #DDDDDD !important;
    font-size: 12px !important;
    cursor: pointer;
    box-sizing: border-box;
    line-height: normal;
}

Works in the default and Reno admin themes and my frontend theme.  Hope that helps

Here is the pull request https://github.com/adrianbj/TracyDebugger/pull/9

  • Like 1

Share this post


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

Not sure about this - I like your thinking, but then where do I stop? 

It's up to you :) I'm fine with the expanded bar too, just thought this could save some clicks.

Share this post


Link to post
Share on other sites

New Captain Hook panel just added!

Features:

  1. The hooks are parsed directly from the files in your PW installation, so they will always be up to date.
  2. They are cached, but will be updated whenever you upgrade your PW version.
  3. If you have your Editor Protocol Handler properly configured for Tracy, clicking on the Line Number will open to the method in your code editor.

This panel uses @owzim's Captain Hook generator: https://github.com/owzim/PWCaptainHookCLI

Please let me know if you have any problems or suggestions.

Screen Shot 2017-01-24 at 10.43.45 PM.png

  • Like 8

Share this post


Link to post
Share on other sites

I'm seeing an error in the new Captain Hook panel on Windows - I think it's the path slashes issue.

ErrorException: file_get_contents(D:/Websites/__www/1testing/wire/): failed to open stream: No such file or directory in D:\Websites\__www\1testing\site\assets\cache\FileCompiler\site\modules\TracyDebugger\CaptainHook\classes\CaptainHookSearch.php:44

Dumping $filenamesArray in CaptainHookSearch::getHooks() shows paths like...

"D:/Websites/__www/1testing/wire/"
"D:/Websites/__www/1testing/wire\config.php"
"D:/Websites/__www/1testing/wire\core\admin.php"
"D:/Websites/__www/1testing/wire\core\boot.php"
...

Edit: actually, it might be the first item in the array that's the problem: "D:/Websites/__www/1testing/wire/". Seems like this shouldn't be in there seeing as it's a directory and and not a .php or .module file.

  • Like 1

Share this post


Link to post
Share on other sites

Thanks - also an error here:

ErrorException: is_file(): open_basedir restriction in effect. File(classes/CaptainHookSearch.php)

 

Share this post


Link to post
Share on other sites

Problem seems to be here:

$paths = array($root);

Might be misunderstanding something but don't think the root directory is wanted in that array.

  • Like 1

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!