adrian

Tracy Debugger

Recommended Posts

5 hours ago, Robin S said:

Problem seems to be here:


$paths = array($root);

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

I can't see why it's there either. I have removed here and it's still working fine (although it was working fine for me with it also). Does it fix the problem at your end?

5 hours ago, tpr said:

Thanks - also an error here:


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

 

Do you have anymore details on this error. There isn't actually an is_file() call in that CaptainHookSearch.php file. Maybe if you sent me your open_basedir restrictions it would help me to reproduce.

  • Like 1

Share this post


Link to post
Share on other sites

A more verbose error message:

ErrorException: is_file(): open_basedir restriction in effect. File(classes/CaptainHookSearch.php) is not within the allowed path(s): (/var/www/vhosts/domain.com/:/tmp/) in /var/www/vhosts/domain.com/sub.domain.com/wire/core/FileCompiler.php:312
Stack trace:
#0 [internal function]: Tracy\Bar->Tracy\{closure}(2, 'is_file(): open...', '/var/www/vhosts...', 312, Array)
#1 /var/www/vhosts/domain.com/sub.domain.com/wire/core/FileCompiler.php(312): is_file('classes/Captain...')

So it's the FileCompiler I guess. 

For the open_basedir I have the default setting in Plesk:

{WEBSPACEROOT}{/}{:}{TMP}{/}

 

  • Like 1

Share this post


Link to post
Share on other sites

Thanks @tpr - that helps. Could you please try the latest version. Hopefully I have fixed that and the problem @Robin S was having.

I have also added /site/modules/ so it is also scanned for hookable methods. This means the list of files/hooks will now also include all your installed 3rd party modules.

  • Like 1

Share this post


Link to post
Share on other sites

No errors here, thanks!

I really think there could be a search/filter box in the panels. I know it's hard because panel layouts are different but it could greatly improve productivity (e.g the new CaptainHook panel is about 4 screens high here).

  • Like 2

Share this post


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

No errors here, thanks!

Great - thanks!

1 minute ago, tpr said:

No errors here, thanks!

I really think there could be a search/filter box in the panels. I know it's hard because panel layouts are different but it could greatly improve productivity (e.g the new CaptainHook panel is about 4 screens high here).

I agree and have been contemplating it, but not sure the best approach. Do we need to filter just the filenames, or do we need to filter to the method name? If it's the former, then CTRL/CMD + F is possibly just as easy as a filter. If we also want method names then things will obviously get a bit trickier - do we need to add the name of each method to a data attribute for each file so it can be filtered? Do we want to automatically expand filtered files?

Any thoughts?

Share this post


Link to post
Share on other sites

Imo many panels could be enhanced with a filter, not only CaptainHook. But as I wrote I know it's complicated and the filter should work differently in each panels. Unless I'm mistaken some panels even load data with Ajax, making things even worse. If I knew a cross-panel solution I would have created a PR :) I think ctrl+F will do now :) 

  • Like 2

Share this post


Link to post
Share on other sites

New Captain Hook version just posted!

Changes:

  • I have rewritten the file parser so that it uses token_get_all, rather than a regex. This makes it much faster and it also makes it easier to exclude functions that are commented out. Please let me know if you notice any files/hookable methods that aren't listed.
  • Added a new column which has the className::hookName formatted and ready to copy/paste.
  • Hooks for site modules will be automatically added when a new module is installed.
  • Cached version is now stored in the DB cache table, rather than on the filesystem.
     

Screen Shot 2017-01-25 at 11.15.38 AM.png

  • Like 3

Share this post


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

Hopefully I have fixed that and the problem @Robin S was having.

All fixed, thanks. I'm really liking how easy it is to jump straight to the method in my code editor via the clickable line number. A real timesaver.

  • Like 1

Share this post


Link to post
Share on other sites

@adrian, a while ago @bernhard came up with a cool idea for a "hook recorder":

I'm wondering if you and he think this is something that might be integrated into Tracy Debugger. Now that there is the feature in Tracy (thanks @owzim) for parsing the hookable methods from the wire/site directories, I was thinking that there could be a feature that temporarily appends hooks for all hookable methods to /site/init.php or /site/ready.php. These "auto-hooks" would just do something simple like log/dump the method name as the hook fires.

Of course this would be terrible for site performance - it's something you would only enable briefly during development to work out which hookable methods are firing as PW completes some task.

What do you think?

  • Like 1

Share this post


Link to post
Share on other sites

Another update!

There is now a "Toggle All" button which may come in handy if you want to search for a method (CTRL/CMD + F) to see the classes it exists in.

Tip: search for "___save", rather than "save" so it doesn't find it twice on each row.

Screen Shot 2017-01-25 at 6.06.46 PM.png


Another update, unrelated to Captain Hook - now each panel in the Selector Panel has an info iconlinked to the relevant section in the "Introducing Tracy Debugger" blog post so you can get quick information about what each panel does.

 

 

Screen Shot 2017-01-25 at 8.10.52 PM.png

  • Like 3

Share this post


Link to post
Share on other sites
4 hours ago, Robin S said:

@adrian, a while ago @bernhard came up with a cool idea for a "hook recorder":

Sounds like a good idea to me. @bernhard actually mentioned here as well many pages back, but I never got around to it.

@bernhard - do you have the latest version of the code available somewhere?

  • Like 1

Share this post


Link to post
Share on other sites

And now for something completely different - Tracy Debugger ProcessWirified! :)

td-pw-design.gif

It's still in "alpha" (meaning spent only 15 minutes on it) but feels much better. Note the semi-transparent borders (no drop shadow), full-height header buttons and the PW colors (borrowed from the Reno theme).

  • Like 7

Share this post


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

And now for something completely different - Tracy Debugger ProcessWirified! :)

That is looking really nice - I agree, the default styles from the Tracy core are ugly as :) - really looking forward to your final version - thanks! BTW - nice seeing that you are making good use of the console Snippets :)

While you're in the mode for tackling this stuff, if you feel like it, it would be incredible if you'd be willing to take a look at this: https://github.com/nette/tracy/pull/241

As it mentions, that PR is a work in progress, but it looks like it's going to do more harm than good in my opinion. From my initial experiments, it's going to make it very difficult to get the ACE editor styles into the Console panel. In particular, have a read of my comment here: https://github.com/nette/tracy/pull/241#issuecomment-273268211 - most importantly, note that I always hack the Tracy core's /tracy-master/src/Tracy/assets/Bar/bar.css to change line #23 from #tracy-debug * { to #tracy-debug-bar * {

Perhaps we should talk about this more via PM if you are interested in helping to get everything working with that new approach that is in the works.

PS - no pressure - I am sure you have lots of other things to do. I have been putting it off for the moment myself :)

  • Like 1

Share this post


Link to post
Share on other sites

My changes are only minor ones so I can easily re-add them even if Tracy devs change most styling. I can send the CSS if you need in the meantime.

Those snippets are mainly for testing but the Console panel itself oftencomes in very handy :) 

Share this post


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

I can send the CSS if you need in the meantime.

Just send through whenever you are happy with things - definitely looks like a great improvement - much appreciated!

Share this post


Link to post
Share on other sites
On 26.1.2017 at 3:24 AM, adrian said:

@bernhard - do you have the latest version of the code available somewhere?

hi adrian,

nice that you take up my idea. i may have the code somewhere but i don't think it would be helpful. i did a manual search&replace in the wire folder that writes all calls to a file. i think you'll have a much better approach in some minutes :)

looking forward to your solution.

what i mentioned when playing with it was, that it gets quite messy very quickly. there are lots of hookable methods and on every pagesave or edit there are lots of recorded hooks. it would be necessary to build some UI around that. or additional informations, like a dump of the event object or the like. I'm not sure what the best solution would be for this.

do you understand what i'm talking about? :)

  • Like 1

Share this post


Link to post
Share on other sites

Hi all!

Major overhaul / refactor just committed.

To quote Github: Showing 54 changed files with 1,705 additions and 1,295 deletions. Yes, I haven't slept much lately :)

I have tried to test everything very thoroughly, but with so many changes, there might be new bugs introduced. Please let me know if you find any issues.

You'll also noticed that I have bumped the version number to 4.0.0 and am using a string now so that I can start being more semantic with the version numbers.

Here's a rough highlight of the changes.

  • New skin - a huge thanks to @tpr for all his efforts on this, not to mention lots of other feedback / bug reports while developing this new version!
  • Captain Hook Improvements - it now shows dynamically added hooks, like Page::viewable in both the core and your site module. Also some general cleanup.
  • More SessionHandlerDB fixes - there were still some outstanding issues with some of the lesser used panels. Hopefully we're closer to this being a non-issue.
  • Improved CSS loading - in particular when opening panels in a popup window.
  • General code updates - various things, including updating wire() and $this calls to $this->wire() where appropriate.
  • Lots of bug fixes - mostly issues with the lesser used panels that had gone unnoticed, but still it's amazing what you find when you do a major refactor. 
  • Better code documentation - not my strong point in the past - hopefully this is now on the way to being much better.
  • File / folder restructuring - not really of concern to you guys, but will make life a little easier for me going forward with future enhancements.

Captain Hook panel showing new dynamic hookable methods and @tpr's fantastic new skin!

Screen Shot 2017-02-03 at 12.57.07 PM.png

  • Like 9

Share this post


Link to post
Share on other sites

I have just added a "Config" section to the Debug Mode panel. This returns a nicely formatted table of all the properties of $config - this includes those set in /wire/config.php and /site/config.php, as well as many other derived system settings. 

To make this visible you will either need to add 'config' to the $config->debugTools array in /site/config.php, or uncheck "Respect the PW $config->debugTools config option" in the Tracy config settings.

It shows way too many things to list here, but I think it makes a nice additional resource, so please be sure to check it out. Of course all arrays are expandable.

Screen Shot 2017-02-06 at 5.18.23 PM.png

  • Like 5

Share this post


Link to post
Share on other sites

Just been playing around with a quick visual indicator to let you know if you are on the local or live version of a site. It's done by IP address using the same code that Tracy uses for its DETECT module to switch between DEV and PRODUCTION. 

Not sure how useful this is, but I do know that I sometimes have the local and live versions of a site open in separate browser tabs and occasionally I'll accidentally edit content in the wrong one. I am usually very careful, but we all make mistakes and just thought this might help as an additional visual indicator (without having to look at the address bar). Of course it could be taken further with customizable colors and customizable ways of defining what is dev vs staging vs production if they are all on live servers.

Any thoughts on whether you guys would make use of this?

Local

Screen Shot 2017-02-06 at 6.03.42 PM.png

Live

Screen Shot 2017-02-06 at 6.04.09 PM.png

 

 

  • Like 2

Share this post


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

occasionally I'll accidentally edit content in the wrong one.

Me too! See:

While I like this indicator, it is way too subtle, not to mention that often I have Tracy turned off for the backend.

Edited by szabesz
typo

Share this post


Link to post
Share on other sites
12 hours ago, szabesz said:

While I like this indicator, it is way too subtle, not to mention that often I have Tracy turned off for the backend.

I was wondering about both of these. I actually always have Tracy on in the backend (especially now that we have the "Reference page being edited" option), but I understand that not everyone will. I could pretty easily color the masthead in the backend, eg:

Screen Shot 2017-02-07 at 10.09.44 AM.png

It can start looking pretty ugly but I guess since it's only for superusers (and other authorized Tracy users) it doesn't really matter ?

 

  • Like 1

Share this post


Link to post
Share on other sites

This is sooo art direction. Please make it optional :)

  • Like 2

Share this post


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

doesn't really matter

As long as one can define the color, it doesn't matter ;)

 

  • Like 1

Share this post


Link to post
Share on other sites
4 minutes ago, tpr said:

This is sooo art direction. Please make it optional :)

Of course :) 

3 minutes ago, szabesz said:

As long as one can define the color, it doesn't matter ;)

Absolutely :)

Now the question is whether it should just be local vs live (detected by IP address), or whether it also needs to include subdomain detection so you can color by dev.mysite.com vs staging.mysite.com vs mysite.com. Any thoughts?

 

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!