adrian

Tracy Debugger

Recommended Posts

4 minutes ago, adrian said:

so you can color by dev.mysite.com vs staging.mysite.com vs mysite.com.

+1 :P And thanks a million, as always...

Edited by szabesz
typo

Share this post


Link to post
Share on other sites

Not completely sure what happened, but i upgraded Tracy on a site running 2.7.3 and it killed the site. I fixed the permissions on all of the Tracy files which were set incorrectly after upgrade, but this didn't prevent the issue.

 

Error: Call to a member function queryString() on null (line 507 of ....wire/core/WireInput.php)
This error message was shown because you are logged in as a Superuser. Error has been logged.

  • Like 1

Share this post


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

Not completely sure what happened, but i upgraded Tracy on a site running 2.7.3 and it killed the site. I fixed the permissions on all of the Tracy files which were set incorrectly after upgrade, but this didn't prevent the issue.

 

Error: Call to a member function queryString() on null (line 507 of ....wire/core/WireInput.php)
This error message was shown because you are logged in as a Superuser. Error has been logged.

Do you have the very latest version of Tracy - that PW 2.x problem was reported already and I fixed in in 4.0.1, unless it is occurring for some other reason as well.

  • Like 1

Share this post


Link to post
Share on other sites
32 minutes ago, Macrura said:

It's running 'version' => '4.0.4',

Thanks. Can you please try replacing lines 227 and 228 of TracyDebugger.module:

        // don't init Tracy for the PW Notifications module polling
        if(strpos($this->wire('input')->queryString(), 'Notifications=update') !== false) return;

with:

        // don't init Tracy for the PW Notifications module polling
        if($this->wire('input')) {
            $queryString = $this->wire('input')->queryString();
        }
        else {
            $info = parse_url($_SERVER['REQUEST_URI']);
            $queryString = $info['query'];            
        }
        if(strpos($queryString, 'Notifications=update') !== false) return;

 

Share this post


Link to post
Share on other sites

OK - thanks @adrian i will need to test this after 5pm (i think the owners are working in the admin so I don't want to crash the site during NY business hrs..)

  • Like 1

Share this post


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

OK - thanks @adrian i will need to test this after 5pm (i think the owners are working in the admin so I don't want to crash the site during NY business hrs..)

No problem - thanks and sorry for the problems in the first place!

Just an FYI why this is happening. It turns out that I had to move lots of logic from ready() into init() to fix some more SessionHandlerDB issues. The problem is that $input seems to be available much earlier in PW 3 than it was in PW 2, hence the reporting of $input as null.

  • Like 1

Share this post


Link to post
Share on other sites

ok thanks for helping out so fast, and hopefully this will help prevent this type of issue for forward versions!

  • Like 1

Share this post


Link to post
Share on other sites

Hi everyone!

Introducing the new Style Admin by Server Type  feature. Hopefully this will reduce the chance of accidentally editing the wrong version of a site when you have more than one open in different tabs.

Firstly, a huge shoutout to @szabesz for the idea for this new feature and for lots of testing and suggestions to improve it. Also @tpr chipped in with some CSS help yet again!

This feature adds a ribbon down the side of the admin to let you know what version of the site you are on, eg. local, dev, staging, etc.

Screen Shot 2017-02-08 at 3.11.24 PM.png

 

Firstly you will need to enable it in the config settings. Then you'll want to set up your various server types and colors. It comes with the following defaults.

Screen Shot 2017-02-08 at 3.13.02 PM.png

 

If you don't like the side ribbon, you can actually style the output exactly how you want.

Screen Shot 2017-02-08 at 3.15.36 PM.png

 

  • Like 2

Share this post


Link to post
Share on other sites

Hi Adrian,

those changes didn't fix the error;

Share this post


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

Hi Adrian,

those changes didn't fix the error;

Let's take this to PM

Share this post


Link to post
Share on other sites

Admin styling: adding "pointer-events: none" could be useful I think.

  • Like 1

Share this post


Link to post
Share on other sites
On 2/9/2017 at 2:33 AM, tpr said:

Admin styling: adding "pointer-events: none" could be useful I think.

Hey @tpr - where do you think this should be applied? Sorry if I am missing the obvious :)

Share this post


Link to post
Share on other sites

To the recently added staging bar. In AOS for example it partly covers the sidebar so items loose hover state when you move the mouse over the bar.

  • Like 1

Share this post


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

To the recently added staging bar. In AOS for example it partly covers the sidebar so items loose hover state when you move the mouse over the bar.

Ok gotcha - I see how it helps now. I had a quick look and couldn't figure out what it achieved, but now I see and agree it's a little nicer. I wish there was a way to not have it partly cover the sidebar, but with those elements being absolutely positioned, I don't see an option. I think what I ended up with is a decent compromise though - it's narrow enough that it doesn't interfere, but is still obvious enough. If anyone has any better ideas I'd be happy to change.

  • Like 2

Share this post


Link to post
Share on other sites

A few updates to the server type indicator ribbon:

  1. It's now possible to display it on the frontend as well. It might seem weird, but on occasion I have been looking at the frontend in the wrong tab (live vs dev) and wondering why my changes aren't doing anything :)
  2. You can now hide the indicator along with the Tracy debug bar when you use the hide icon.
  3. Here is the css to use if you'd prefer to have the indicator along the bottom:
body::before {
    content: "[type]";
    background: [color];
    position: fixed;
    left: 0;
    bottom: 0;
    color: #ffffff;
    width: 100%;
    padding: 0;
    text-align: left;
    text-indent: 5px;
    font-weight: 600;
    text-transform: uppercase;
    z-index: 29999;
    font-size: 15px;
    height: 22px;
    line-height: 22px;
    pointer-events: none;
}

which looks like this rather than the default sidebar. It is of course also fixed so it always visible when you scroll.

Screen Shot 2017-02-13 at 7.41.53 PM.png

  • Like 3

Share this post


Link to post
Share on other sites

Another minor (but hopefully useful addition) - you can now use keyboard shortcuts to move between items in the console panel history stack.

Back: CTRL+CMD+↑
Forward: CTRL+CMD+↓

The up and down arrows are to mimic unix based terminal history shortcuts. Unfortunately I had to add the CTRL+CMD in there as well because it's hard to find a combination that isn't already used for something else, either by the browser or ACE editor.

Anyway, hope you will find it useful for speedy switching back and forward between snippets of code you have recently run.

  • Like 2

Share this post


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

Back: CTRL+CMD+↑
Forward: CTRL+CMD+↓

Thank you! I've been missing it :)

  • Like 1

Share this post


Link to post
Share on other sites

just popping by to say that Tracy made it possible for me to convert an old site where i was using direct output, to a delayed output model, which i needed to be able to handle the new requirements of the site; in particular, the template path feature was crucial – i was able to simply duplicate each template one at a time, rename to -dev, and work on the conversion until it was ready... Also the new styling looks great!

  • Like 3

Share this post


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

in particular, the template path feature was crucial

Thanks for the feedback @Macrura - I have often wondered how much use the template path (and template editor) panels were getting. Glad to hear that it helped you out :)

Share this post


Link to post
Share on other sites

yeah, when i first started the conversion, i was basically scratching my head about how hard/complex it would be to change from direct to delayed; At some point along the way i remembered the tracy template path, and after that it just went really fast.. now that site's code has been completely refactored and it's so much cleaner!

  • Like 1

Share this post


Link to post
Share on other sites

Hi @adrian

Perhaps slightly off topic but...

I'd like to report that I had a recent differential backup that was growing rather fast, and it turned out to be tracy files in the session directory of the site. I've since excluded the offending session directory from the backup (shouldn't have been there in the first place) but it might be worth noting that the total size of all the tracy sessions files had grown into the 10s of GB. I wonder if there is any practical way Tracy could be made to cull its old session files?

Best wishes,
Steve

  • 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 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
      180817, v1.0.6, support for joining multiple finders 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 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 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: