Jump to content
adrian

Tracy Debugger

Recommended Posts

@Ipa and @tpr - can you please try the latest version and see if that error is now gone?

Speaking of the latest version, it includes a few new features.

  1. The ability to force superusers to always be in DEVELOPMENT mode, even on a live site.
     
  2. The ability to restrict non-superusers by their IP address - this is very useful if you need to debug a live site for a guest (or non-superuser role) and want the debugger bar and other features normally restricted to development mode. You can set the mode to DEVELOPMENT, give the user the "tracey-debugger" permission, and then restrict to your current IP address.
     
  3. The Users panel provides details of IP Address restriction so you can always easily check if you're safe.

post-985-0-67599400-1456168043_thumb.png

  • Like 1

Share this post


Link to post
Share on other sites

Update version error is gone, thanks!

  • Like 1

Share this post


Link to post
Share on other sites

i just installed tracy and had some problems:

im on 2.7.2 and installation went without problems. but i can't see the debug bar. neither on frontend nor on backend. i tried with a different browser because i have some problems with visibility sometimes on my laptop and got the following error on the pw-login screen:

debug->true

Fatal error: Cannot use object of type TracyDebugger as array in /var/www/.../site/modules/TracyDebugger/TracyDebugger.module on line 476

Error: Cannot use object of type TracyDebugger as array (line 476 of /var/www/.../site/modules/TracyDebugger/TracyDebugger.module)

This error message was shown because site is in debug mode ($config->debug = true; in /site/config.php). Error has been logged. 

debug->false

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Error has been logged. 

besides those errors: do i have to do some additional things to see the tracy bar?

thanks for your help :)

Share this post


Link to post
Share on other sites

The original problem has not gone. At the moment all the frontend pages give me the error: "Class 'ProcessWire\TracyDebugger' not found". I have even tried to reinstall the module, but it doesn't help. I don't see the version mismatch on the upgrades page anymore. 

<?php 57: if(class_exists('TracyDebugger')) {

58: \ProcessWire\wire('templateVars', TracyDebugger::templateVars(get_defined_vars(), \ProcessWire\wire('page')));

59: }

Share this post


Link to post
Share on other sites

@BernhardB - are you using the latest version? Also, what version of PHP are you using - I wonder if there might be something connected with that?

@Ipa - can you please try emptying the site/assets/cache/FileCompiler/site/templates folder and see if it starts working after that?

Share this post


Link to post
Share on other sites

@BernhardB

Try setting Output Mode to "DEVELOPMENT"

Share this post


Link to post
Share on other sites

Actually I am seeing @BernhardB's issue when running 2.7.2 - I'll hopefully have a fix soon.

Share this post


Link to post
Share on other sites

hi adrian,

PHP Version 5.4.45 and tracy 0.5.4

the error came when i tried to reach the admin in a different browser where i was NOT logged in. in the browser where i installed tracy it seemed that everything worked but i could not see the debug panel. don't know if that's somehow related so my laptop or if i did not setup it correctly? i checked both checkboxes (frontend + backend)

Share this post


Link to post
Share on other sites

@BernhardB - please try the latest version for me.

  • Like 1

Share this post


Link to post
Share on other sites

@Ipa - can you please try emptying the site/assets/cache/FileCompiler/site/templates folder and see if it starts working after that?

The problem is with Show Variables Panel setting. After clearing the compiled files from cache with the Show Variables Panel setting off, everything works. But when I enable the Show Variables Panel, the error is back. 

Share this post


Link to post
Share on other sites

great adrian, that did it :) and i can also see the panel now, it was related to my browser.

Share this post


Link to post
Share on other sites

The problem is with Show Variables Panel setting. After clearing the compiled files from cache with the Show Variables Panel setting off, everything works. But when I enable the Show Variables Panel, the error is back. 

Yeah, it is that feature which is responsible for adding that line to the bottom of the compiled templates - I just don't yet know why you are still getting the error and @tpr isn't and I have never seen it :) What version of PW and PHP are you running?

great adrian, that did it  :) and i can also see the panel now, it was related to my browser.

Glad it's working now - thanks for letting me know. What do you mean about it being related to your browser?

Share this post


Link to post
Share on other sites

@adrian: I just pop in to report that Tracy Debugger 0.5.5 on ProcessWire 3.0.8 with PHP 5.6.10 works without a hitch so far :) Thanx once more!

  • Like 1

Share this post


Link to post
Share on other sites

@adrian: I just pop in to report that Tracy Debugger 0.5.5 on ProcessWire 3.0.8 with PHP 5.6.10 works without a hitch so far :) Thanx once more!

Awesome - thanks for letting me know.

I did just make another change though in an attempt to fix the problem @Ipa is still having with the Variables panel. Hopefully this might work and hopefully I haven't broken anything for anyone else :)

  • Like 1

Share this post


Link to post
Share on other sites

Awesome - thanks for letting me know.

I did just make another change though in an attempt to fix the problem @Ipa is still having with the Variables panel. Hopefully this might work and hopefully I haven't broken anything for anyone else :)

Sorry, but it still doesn't work for me. I have PHP 5.5.29, PW 3.0.8 and Mac OS X 10.10.5.

Share this post


Link to post
Share on other sites

I switched to PHP 5.5.26 (that is the closest to 5.5.29 I happen have at the moment). I am also on OS X 10.10.5 but this should not matter too much I guess. I also updated to 0.5.6. Actually I have just realized, that although I do not get any errors with $Variables Panel turned on, it does not display any variables except for a strange empty array, like this:

array ()

That is all I have in the panel, however – for example – I have $title = $page->get('headline|title'); in my _init.php and <?= $title ?> outputs fine. Shouldn't it be a variable that is displayed in this panel?

Share this post


Link to post
Share on other sites

@Ipa - did you clear your FileCompiler templates cache after installing the new version? - this is essential to ensure the new version of the code is added into the templates when they are compiled.

I switched to PHP 5.5.26 (that is the closest to 5.5.29 I happen have at the moment). I am also on OS X 10.10.5 but this should not matter too much I guess. I also updated to 0.5.6. Actually I have just realized, that although I do not get any errors with $Variables Panel turned on, it does not display any variables except for a strange empty array, like this:

array ()

That is all I have in the panel, however – for example – I have $title = $page->get('headline|title'); in my _init.php and <?= $title ?> outputs fine. Shouldn't it be a variable that is displayed in this panel?

Sorry, I should have made it more obvious that for this feature to work, you need to clear your compiled templates cache as it needs to add a line to the bottom of the compiled template. Once you do this once, it will work for future updates to your templates.

Share this post


Link to post
Share on other sites

Thanks. I manually cleaned .../site/assets/cache/FileCompiler/site/modules and got fatal error as the class TracyDebugger was not found. (Class 'ProcessWire\TracyDebugger' not found). And using Admin > Modules > Site > [Clear Compiled Files] button afterwards did not help.

Deleting the FileCompiler folder itself gets rid of the error, but my original problem (that is not seeing any variables in the panel) remained.

One more thing. If I manually delete .../site/assets/cache/FileCompiler/site/modules and do not resave the module settings afterwards but try to reload the forntend, then the Fatal Error is back againg.

Share this post


Link to post
Share on other sites

What is folder permission for cache/FileCompiler?

Share this post


Link to post
Share on other sites

I cleared the cache both manually and with the button at Site -> Modules settings. The problem remains. I have also the empty array() in my $Variables panel.

Share this post


Link to post
Share on other sites

What is folder permission for cache/FileCompiler?

This is my local machine and I run Apache as my own user so that I always have read/write permissions while developing.

Share this post


Link to post
Share on other sites

You need to empty .../site/assets/cache/FileCompiler/site/templates, not .../site/assets/cache/FileCompiler/site/modules

Please tell me that works :)

Share this post


Link to post
Share on other sites

Yes, I have deleted files in site/assets/cache/FileCompiler/site/templates and it still gives those errors….

Share this post


Link to post
Share on other sites

So the line added to the end of my compiled template files currently looks like:

if(class_exists('TracyDebugger')) {
    TracyDebugger::$templateVars = TracyDebugger::templateVars(get_defined_vars(), \ProcessWire\wire('page'));
}

Does that match what you are currently seeing?

What if you manually add \ProcessWire\ in front of each TracyDebugerr, like this - just do it for one of the compiled template files and load a page with that template - this is just a test for me at the moment to help debug.

if(class_exists('\ProcessWire\TracyDebugger')) {
    \ProcessWire\TracyDebugger::$templateVars = \ProcessWire\TracyDebugger::templateVars(get_defined_vars(), \ProcessWire\wire('page'));
}

I feel like I am going off on a tangent here, but what happens if you also add false to that check, eg:

if(class_exists('\ProcessWire\TracyDebugger', false)) {
    \ProcessWire\TracyDebugger::$templateVars = \ProcessWire\TracyDebugger::templateVars(get_defined_vars(), \ProcessWire\wire('page'));
}

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
      --- Please use RockFinder3 ---
    • By MoritzLost
      Cacheable Placeholders
      This module allows you to have pieces of dynamic content inside cached output. This aims to solve the common problem of having a mostly cacheable site, but with pieces of dynamic output here and there.  Consider this simple example, where you want to output a custom greeting to the current user:
      <h1>Good morning, <?= ucfirst($user->name) ?></h1> This snippet means you can't use the template cache (at least for logged-in users), because each user has a different name. Even if 99% of your output is static, you can only cache the pieces that you know won't include this personal greeting. A more common example would be CSRF tokens for HTML forms - those need to be unique by definition, so you can't cache the form wholesale.
      This module solves this problem by introducing cacheable placeholders - small placeholder tokens that get replaced during every request. The replacement is done inside a Page::render hook so it runs during every request, even if the response is served from the template cache. So you can use something like this:
      <h1>Good morning, {{{greeting}}}</h1> Replacement tokens are defined with a callback function that produces the appropriate output and added to the module through a simple hook:
      // site/ready.php wire()->addHookAfter('CachePlaceholders::getTokens', function (HookEvent $e) { $tokens = $e->return; $tokens['greeting'] = [ 'callback' => function (array $tokenData) { return ucfirst(wire('user')->name); } ]; $e->return = $tokens; }); Tokens can also include parameters that are parsed and passed to the callback function. There are more fully annotated examples and step-by-step instructions in the README on Github!
      Features
      A simple and fast token parser that calls the appropriate callback and runs automatically. Tokens may include multiple named or positional parameters, as well as multi-value parameters. A manual mode that allows you to replace tokens in custom pieces of cached content (useful if you're using the $cache API). Some built-in tokens for common use-cases: CSRF-Tokens, replacing values from superglobals and producing random hexadecimal strings. The token format is completely customizable, all delimiters can be changed to avoid collisions with existing tag parsers or template languages. Links
      Github Repository & documentation Module directory (pending approval) If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
    • By Craig
      I've been using Fathom Analytics for a while now and on a growing number of sites, so thought it was about time there was a PW module for it.
      WayFathomAnalytics
      WayFathomAnalytics is a group of modules which will allow you to view your Fathom Analytics dashboard in the PW admin panel and (optionally) automatically add and configure the tracking code on front-end pages.
      Links
      GitHub Readme & documentation Download Zip Modules directory Module settings screenshot What is Fathom Analytics?
      Fathom Analytics is a simple, privacy-focused website analytics tool for bloggers and businesses.

      Stop scrolling through pages of reports and collecting gobs of personal data about your visitors, both of which you probably don't need. Fathom is a simple and private website analytics platform that lets you focus on what's important: your business.
      Privacy focused Fast-loading dashboards, all data is on a single screen Easy to get what you need, no training required Unlimited email reports Private or public dashboard sharing Cookie notices not required (it doesn't use cookies or collect personal data) Displays: top content, top referrers, top goals and more
    • By daniels
      This is a lightweight alternative to other newsletter & newsletter-subscription modules.
      You can find the Module in the Modules directory and on Github
      It can subscribe, update, unsubscribe & delete a user in a list in Mailchimp with MailChimp API 3.0. It does not provide any forms or validation, so you can feel free to use your own. To protect your users, it does not save any user data in logs or sends them to an admin.
      This module fits your needs if you...
      ...use Mailchimp as your newsletter / email-automation tool ...want to let users subscribe to your newsletter on your website ...want to use your own form, validation and messages (with or without the wire forms) ...don't want any personal user data saved in any way in your ProcessWire environment (cf. EU data regulation terms) ...like to subscribe, update, unsubscribe or delete users to/from different lists ...like the Mailchimp UI for creating / sending / reviewing email campaigns *I have only tested it with PHP 7.x so far, so use on owners risk
      EDIT:
      Since 0.0.4, instructions and changelog can be found in the README only. You can find it here  🙂
      If you have questions or like to contribute, just post a reply or create an issue or pr on github, thanks!
    • By MoritzLost
      Sorry for the convoluted title. I have a problem with Process modules that define a custom page using the page key through getModuleInfo (as demonstrated in this excellent tutorial by @bernhard). Those pages are created automatically when the module is installed. The problem is that the title of the page only gets set in the current language. That's not a problem if the current language (language of the superuser who is installing the module) is the default language; if it isn't, the Process page is missing a title in the default language. This has the very awkward effect that a user using the backend in the default language (or any other language) will see an empty entry in the setup menu:

      This screenshot comes from my Cache Control module which includes a Process page. Now I realize the description sounds obscure, but for us it's a common setup: We a multiple bilingual sites where the default language is German and the second language is English. While the clients use the CMS in German, as a developer I prefer the English interface, so whenever I install a Process module I get this problem.
      As a module author, is there a way to handle this situation? I guess it would be possible to use post-installation hooks or create the pages manually, but I very much prefer the declarative approach. The page title is already translatable (through the __ function), but of course at the time of installation there is no translation, and as far as I'm aware it's not possible to ship translations with a module so they are used automatically. Could this situation be handled better in the core? I would prefer if the module installation process would always set the title of the Process page in the default language, instead of the language of the current user.
×
×
  • Create New...