adrian

Tracy Debugger

Recommended Posts

szabesz    1,390
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
Macrura    2,150

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
adrian    7,674
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
adrian    7,674
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
Macrura    2,150

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
adrian    7,674
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
Macrura    2,150

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
adrian    7,674

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
adrian    7,674
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
tpr    2,229

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

  • Like 1

Share this post


Link to post
Share on other sites
adrian    7,674
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
tpr    2,229

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
adrian    7,674
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
adrian    7,674

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
adrian    7,674

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
szabesz    1,390
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
Macrura    2,150

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
adrian    7,674
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
Macrura    2,150

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
netcarver    1,883

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 Marc
      I am trying to make a simple wiredata module that lets me select a page I want all visitors to be redirected to. I have this working in ready.php but then I decided on putting it in a module and I can't get it to work. Here's the relevant bits:
      public function ready() { $this->addHookBefore('Page::render', $this, 'redirectUsers'); } public function redirectUsers(HookEvent $e) { $page = $e->object; // The page we want to redirect to. $redirect = $e->pages->get($this->redirectPage); if ($page->id == $redirect->id) return; // Prevent infinite loop. if (!$e->user->isLoggedin()) { $e->session->redirect($redirect, false); // 'false' indicates 302 temp redirect. } } I left some checks out for simplification. Whenever I'm not on the page that I want to redirect to, an infinite redirect loop starts. Could anybody explain why that is?
    • By alxndre
      I just happened upon something that I think is curious, and I'm wondering if this is default behavior. So help me because I know nothing.
      While writing a module, i logged something in wire('log') inside the module's init() function. I was surprised to see that the text was being logged multiple times continuously. So I tried to open a small random module and logged something in its init() function as well, and the same thing happened - the text being logged many times.
      My question is, is this supposed to happen? I just want to understand what's going on. My concern is that if I do something huge in the init function, it will get called repeatedly, as with the log, and cause performance issue. Please note that these are both autoload modules. I was expecting them to log at least once when I refresh, but not continuously like what happened.
      Please let me know. Thanks.
    • By abdus
      I'm developing a multi value fieldtype and there's this method called getLoadQueryAutojoin().
      // FieldtypeMulti.php /** * Return the query used for Autojoining this field (if different from getLoadQuery) or NULL if autojoin not allowed. * * @param Field $field * @param DatabaseQuerySelect $query * @return DatabaseQuerySelect|NULL * */ public function getLoadQueryAutojoin(Field $field, DatabaseQuerySelect $query) { if($this->get('useOrderByCols')) { // autojoin is not used if sorting or pagination is active $orderByCols = $field->get('orderByCols'); if(count($orderByCols) > 0) return null; } $table = $this->database->escapeTable($field->table); $schema = $this->trimDatabaseSchema($this->getDatabaseSchema($field)); $fieldName = $this->database->escapeCol($field->name); $separator = self::multiValueSeparator; foreach($schema as $key => $unused) { $query->select("GROUP_CONCAT($table.$key SEPARATOR '$separator') AS `{$fieldName}__$key`"); // QA } return $query; } Why would someone need to autojoin a field, or not need a autojoin? Any benefits/drawbacks? I havent used the feature it at all in my 3+ years PW experience.
      I'm not sure whether I need to implement it but I am leaning towards returning null and disable it altogether.
    • By antoiba86
      I am a bit confused, because I don't know how to solve this problem.
      When I install the module Languages Support - Page Names, my web falls apart.
      I have all the necessary modules installed as Language support for example.
      This is the error I get in the admin panel.
      Warning: Invalid argument supplied for foreach() in /hosting/www/antoibaprogramming.com/public/wire/modules/LanguageSupport/LanguageSupportPageNames.module on line 107 Warning: Invalid argument supplied for foreach() in /hosting/www/antoibaprogramming.com/public/wire/modules/LanguageSupport/LanguageSupportPageNames.module on line 198 Warning: Invalid argument supplied for foreach() in /hosting/www/antoibaprogramming.com/public/wire/modules/LanguageSupport/LanguageSupportPageNames.module on line 1011 Warning: Invalid argument supplied for foreach() in /hosting/www/antoibaprogramming.com/public/wire/modules/LanguageSupport/LanguageSupportPageNames.module on line 1011 Warning: Invalid argument supplied for foreach() in /hosting/www/antoibaprogramming.com/public/wire/modules/LanguageSupport/LanguageSupportPageNames.module on line 1041
      And this in the front-end.
      Warning: Invalid argument supplied for foreach() in /hosting/www/antoibaprogramming.com/public/wire/modules/LanguageSupport/LanguageSupportPageNames.module on line 107
      Fatal error: Call to a member function get() on null in /hosting/www/antoibaprogramming.com/public/wire/modules/LanguageSupport/LanguageSupportPageNames.module on line 605 Fatal error: Call to a member function get() on null in /hosting/www/antoibaprogramming.com/public/wire/modules/LanguageSupport/LanguageSupportPageNames.module on line 605
    • By kongondo
      The Module Blog for ProcessWire replicates and extends the popular Blog Profile.
      Blog is now in version 2.
      Please read the README in the Github link below in its entirety before using this module 
      Blog Documentation is here (Work in Progress!)
      See this post for new features in version 2 or the readme in GitHub.
      To upgrade from version 1, see these instructions.
      ##################################################
      Most of the text below refers to Blog version 1 (left here for posterity). 
       
      Blog version 1 consists of two modules:
      ProcessBlog: Manage Blog in the backend/Admin.
      MarkupBlog: Display Blog in the frontend.
      Being a module, Blog can be installed in both fresh and existing sites. Note, however, that presently, ProcessBlog is not compatible with existing installs of the Blog Profile. This is because of various structural and naming differences in respect of Fields, Templates, Template Files and Pages. If there is demand for such compatibility, I will code a separate version for managing Blog Profile installs.
      In order to use the 'Recent Tweets Widget', you will need to separately install and setup the module 'MarkupTwitterFeed'.
      Please read the README in the Github link below in its entirety before using this module (especially the bit about the Pages, etc. created by the module). 
      I'll appreciate Beta testers, thanks! Stable release works fine.
      Download
      Modules Directory: http://modules.processwire.com/modules/process-blog/
      Github: https://github.com/kongondo/Blog
      You can also install from right within your ProcessWire install.
      Screenshots (Blog version 1)

      Video Demos
      ProcessBlog
      MarkupBlog
      Credits
      Ryan Cramer
      The Alpha Testers and 'Critics' 
      License
      GPL2