Jump to content
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

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Robin S
      A community member raised a question and I thought a new sanitizer method for the purpose would be useful, hence...
      Sanitizer Transliterate
      Adds a transliterate method to $sanitizer that performs character replacements as defined in the module config. The default character replacements are based on the defaults from InputfieldPageName, but with uppercase characters included too.
      Usage
      Install the Sanitizer Transliterate module.
      Customise the character replacements in the module config as needed.
      Use the sanitizer on strings like so:
      $transliterated_string = $sanitizer->transliterate($string);
       
      https://github.com/Toutouwai/SanitizerTransliterate
      https://modules.processwire.com/modules/sanitizer-transliterate/
       
    • By dimitrios
      Hello,
      this module can publish content of a Processwire page on a Facebook page, triggered by saving the Processwire page.
      To set it up, configure the module with a Facebook app ID, secret and a Page ID. Following is additional configuration on Facebook for developers:
      Minimum Required Facebook App configuration:
      on Settings -> Basics, provide the App Domains, provide the Site URL, on Settings -> Advanced, set the API version to 2.10, add Product: Facebook Login, on Facebook Login -> Settings, set Client OAuth Login: Yes, set Web OAuth Login: Yes, set Enforce HTTPS: Yes, add "http://www.example.com/processwire/page/" to field Valid OAuth Redirect URIs. This module is configurable as follows:
      Templates: posts can take place only for pages with the defined templates. On/Off switch: specify a checkbox field that will not allow the post if checked. Specify a message and/or an image for the post.
      Usage
      edit the desired PW page and save; it will post right after the initial Facebook log in and permission granting. After that, an access token is kept.
       
      Download
      PW module directory: http://modules.processwire.com/modules/auto-fb-post/ Github: https://github.com/kastrind/AutoFbPost   Note: Facebook SDK for PHP is utilized.


    • By thomasaull
      I created a little helper module to trigger a CI pipeline when your website has been changed. It's quite simple and works like this: As soon as you save a page the module sets a Boolean via a pages save after hook. Once a day via LazyCron the module checks if the Boolean is set and sends a POST Request to a configurable Webhook URL.
      Some ideas to extend this:
      make request type configurable (GET, POST) make the module trigger at a specified time (probably only possible with a server cronjob) trigger manually Anything else? If there's interest, I might put in some more functionality. Let me know what you're interested in. Until then, maybe it is useful for a couple of people 🙂
      Github Repo: https://github.com/thomasaull/CiTrigger
    • By Robin S
      I created this module a while ago and never got around to publicising it, but it has been outed in the latest PW Weekly so here goes the support thread...
      Unique Image Variations
      Ensures that all ImageSizer options and focus settings affect image variation filenames.

      Background
      When using methods that produce image variations such as Pageimage::size(), ProcessWire includes some of the ImageSizer settings (height, width, cropping location, etc) in the variation filename. This is useful so that if you change these settings in your size() call a new variation is generated and you see this variation on the front-end.
      However, ProcessWire does not include several of the other ImageSizer settings in the variation filename:
      upscaling cropping, when set to false or a blank string interlace sharpening quality hidpi quality focus (whether any saved focus area for an image should affect cropping) focus data (the top/left/zoom data for the focus area) This means that if you change any of these settings, either in $config->imageSizerOptions or in an $options array passed to a method like size(), and you already have variations at the requested size/crop, then ProcessWire will not create new variations and will continue to serve the old variations. In other words you won't see the effect of your changed ImageSizer options on the front-end until you delete the old variations.
      Features
      The Unique Image Variations module ensures that any changes to ImageSizer options and any changes to the focus area made in Page Edit are reflected in the variation filename, so new variations will always be generated and displayed on the front-end.
      Installation
      Install the Unique Image Variations module.
      In the module config, set the ImageSizer options that you want to include in image variation filenames.
      Warnings
      Installing the module (and keeping one or more of the options selected in the module config) will cause all existing image variations to be regenerated the next time they are requested. If you have an existing website with a large number of images you may not want the performance impact of that. The module is perhaps best suited to new sites where image variations have not yet been generated.
      Similarly, if you change the module config settings on an existing site then all image variations will be regenerated the next time they are requested.
      If you think you might want to change an ImageSizer option in the future (I'm thinking here primarily of options such as interlace that are typically set in $config->imageSizerOptions) and would not want that change to cause existing image variations to be regenerated then best to not include that option in the module config after you first install the module.
       
      https://github.com/Toutouwai/UniqueImageVariations
      https://modules.processwire.com/modules/unique-image-variations/
    • By Sebi
      I've created a small module which lets you define a timestamp after which a page should be accessible. In addition you can define a timestamp when the release should end and the page should not be accessable any more.
      ProcessWire-Module: http://modules.processwire.com/modules/page-access-releasetime/
      Github: https://github.com/Sebiworld/PageAccessReleasetime
      Usage
      PageAccessReleasetime can be installed like every other module in ProcessWire. Check the following guide for detailed information: How-To Install or Uninstall Modules
      After that, you will find checkboxes for activating the releasetime-fields at the settings-tab of each page. You don't need to add the fields to your templates manually.
      Check e.g. the checkbox "Activate Releasetime from?" and fill in a date in the future. The page will not be accessable for your users until the given date is reached.
      If you have $config->pagefileSecure = true, the module will protect files of unreleased pages as well.
      How it works
      This module hooks into Page::viewable to prevent users to access unreleased pages:
      public function hookPageViewable($event) { $page = $event->object; $viewable = $event->return; if($viewable){ // If the page would be viewable, additionally check Releasetime and User-Permission $viewable = $this->canUserSee($page); } $event->return = $viewable; } To prevent access to the files of unreleased pages, we hook into Page::isPublic and ProcessPageView::sendFile.
      public function hookPageIsPublic($e) { $page = $e->object; if($e->return && $this->isReleaseTimeSet($page)) { $e->return = false; } } The site/assets/files/ directory of pages, which isPublic() returns false, will get a '-' as prefix. This indicates ProcessWire (with activated $config->pagefileSecure) to check the file's permissions via PHP before delivering it to the client.
      The check wether a not-public file should be accessable happens in ProcessPageView::sendFile. We throw an 404 Exception if the current user must not see the file.
      public function hookProcessPageViewSendFile($e) { $page = $e->arguments[0]; if(!$this->canUserSee($page)) { throw new Wire404Exception('File not found'); } } Additionally we hook into ProcessPageEdit::buildForm to add the PageAccessReleasetime fields to each page and move them to the settings tab.
      Limitations
      In the current version, releasetime-protected pages will appear in wire('pages')->find() queries. If you want to display a list of pages, where pages could be releasetime-protected, you should double-check with $page->viewable() wether the page can be accessed. $page->viewable() returns false, if the page is not released yet.
      If you have an idea how unreleased pages can be filtered out of ProcessWire selector queries, feel free to write an issue, comment or make a pull request!
×
×
  • Create New...