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