adrian

Tracy Debugger

Recommended Posts

11 minutes ago, Macrura said:

sorry for my confusion, but didn't the P icon used to have a link to edit the page being viewed? I used to use this all the time to get from front end to backend edit page - was that link moved somewhere - the appearance of that P panel seems to have changed a lot.

Hi @Macrura - sorry for the confusion. I split the content of the PW Info panel into two panels - itself and the new Request Info panel. Discussion on this new panel starts here: https://processwire.com/talk/topic/12208-tracy-debugger/?do=findComment&comment=153033

You'll see that it has the page edit and template edit (if your code editor is configured for links) buttons at the bottom. 

The PW Info panel is now more about info and links for PW and the Request Info panel is about the current page/request.

Be sure to check out the new options for both these panels in the module config settings as well - lots of great new tools.

Let me know if you have any more questions about this.

Share this post


Link to post
Share on other sites

Small new feature that some of you may find useful. It is disabled by default so you will need to turn it on in the ProcessWire Info panel config settings section.

Goto Page By ID which is available in the PW Info panel:

 5a1d1db6c196b_ScreenShot2017-11-28at12_26_10AM.png.bf3af193d647cf04683e5f5c1646d7fb.png

It allows you to enter a page ID and click "View" or "Edit to be taken to the appropriate place. 

This was requested by a friend who is getting into PW development and I can see it being quite useful on sites where you reference key pages by ID in your template files and want quick access to view/edit them without browsing or typing a full URL, especially when you can't actually remember what pages they actually are :) 

  • Like 4

Share this post


Link to post
Share on other sites

Hello Adrian upgraded to the latest version and i didnt go well, i am unable to enable the plugin:

 

ProcessWire: ProcessModule: Unknown language

DEBUG MODE BACKTRACE ($config->debug == true):
#0 /var/www/html/wire/core/PagesLoader.php(813): ProcessWire\Languages->setLanguage(NULL)
#1 /var/www/html/wire/core/Pages.php(719): ProcessWire\PagesLoader->getPath(21, Array)
#2 /var/www/html/site/assets/cache/FileCompiler/site/modules/TracyDebugger/TracyDebugger.module(2662): ProcessWire\Pages->getPath('21')
#3 /var/www/html/wire/core/WireHooks.php(777): TracyDebugger->{closure}(Object(ProcessWire\HookEvent))
#4 /var/www/html/wire/core/Wire.php(442): ProcessWire\WireHooks->runHooks(Object(ProcessWire\Modules), 'saveModuleConfi...', Array)
#5 /var/www/html/wire/modules/Process/ProcessModule/ProcessModule.module(1309): ProcessWire\Wire->__call('saveModuleConfi...', Array)
#6 /var/www/html/wire/modules/Process/ProcessModule/ProcessModule.module(1136): ProcessWire\ProcessModule->renderEdit('TracyDebugger', Array)
#7 /var/www/html/wire/core/Wire.php(380): ProcessWire\ProcessModule->___executeEdit()
#8 /var/www/html/wire/core/WireHooks.php(698): ProcessWire\Wire->_callMethod('___executeEdit', Array)
#9 /var/www/html/wire/core/Wire.php(442): ProcessWire\WireHooks->runHooks(Object(ProcessWire\ProcessModule), 'executeEdit', Array)
#10 /var/www/html/wire/core/ProcessController.php(244): ProcessWire\Wire->__call('executeEdit', Array)
#11 /var/www/html/wire/core/Wire.php(380): ProcessWire\ProcessController->___execute()
#12 /var/www/html/wire/core/WireHooks.php(698): ProcessWire\Wire->_callMethod('___execute', Array)
#13 /var/www/html/wire/core/Wire.php(442): ProcessWire\WireHooks->runHooks(Object(ProcessWire\ProcessController), 'execute', Array)
#14 /var/www/html/wire/core/admin.php(113): ProcessWire\Wire->__call('execute', Array)
#15 /var/www/html/wire/modules/AdminTheme/AdminThemeReno/controller.php(13): require('/var/www/html/a...')
#16 /var/www/html/site/templates/admin.php(15): require('/var/www/html/a...')
#17 /var/www/html/wire/core/TemplateFile.php(268): require('/var/www/html/a...')
#18 /var/www/html/wire/core/Wire.php(380): ProcessWire\TemplateFile->___render()
#19 /var/www/html/wire/core/WireHooks.php(698): ProcessWire\Wire->_callMethod('___render', Array)
#20 /var/www/html/wire/core/Wire.php(442): ProcessWire\WireHooks->runHooks(Object(ProcessWire\TemplateFile), 'render', Array)
#21 /var/www/html/wire/modules/PageRender.module(514): ProcessWire\Wire->__call('render', Array)
#22 /var/www/html/wire/core/Wire.php(383): ProcessWire\PageRender->___renderPage(Object(ProcessWire\HookEvent))
#23 /var/www/html/wire/core/WireHooks.php(698): ProcessWire\Wire->_callMethod('___renderPage', Array)
#24 /var/www/html/wire/core/Wire.php(442): ProcessWire\WireHooks->runHooks(Object(ProcessWire\PageRender), 'renderPage', Array)
#25 /var/www/html/wire/core/WireHooks.php(782): ProcessWire\Wire->__call('renderPage', Array)
#26 /var/www/html/wire/core/Wire.php(442): ProcessWire\WireHooks->runHooks(Object(ProcessWire\Page), 'render', Array)
#27 /var/www/html/wire/modules/Process/ProcessPageView.module(205): ProcessWire\Wire->__call('render', Array)
#28 /var/www/html/wire/core/Wire.php(383): ProcessWire\ProcessPageView->___execute(true)
#29 /var/www/html/wire/core/WireHooks.php(698): ProcessWire\Wire->_callMethod('___execute', Array)
#30 /var/www/html/wire/core/Wire.php(442): ProcessWire\WireHooks->runHooks(Object(ProcessWire\ProcessPageView), 'execute', Array)
#31 /var/www/html/index.php(55): ProcessWire\Wire->__call('execute', Array)
#32 {main}
  • Like 1

Share this post


Link to post
Share on other sites
On 28.10.2017 at 8:30 PM, adrian said:

I have rebuilt the Dumps Recorder panel as well. You probably won't want this most of the time, so it is no longer enabled by default on new Tracy installs, so if you are upgrading, I recommend disabling the Dumps Recorder panel by default and just enabling via the Panel Selector as needed. It no longer has a "Preserve Dumps" option, because that is now it's only purpose, so when it is enabled, it will preserve all dumps across all page / ajax requests and reloads. You can click "Clear Dumps" whenever you want, and of course disabling it will also clear the recorded dumps.

hi adrian,

I hope i'm using tracy wrong in this case because the missing option is quite annoying for me. I'm debugging a lot via bd('mytest') calls in my project and when i reload i want to see all dumps based on that single reload most of the time. with the missing option i always have to clean the dump and then reload. if i dont clean the dump it gets messy and misleading sometimes (showing variable values from a previous pageload).

thanks for your help :)

Share this post


Link to post
Share on other sites

Hi @erikvanberkum - sorry for the trouble upgrading. I am wondering if you'd mind helping me debug this please?

Firstly, what version of PW and PHP are you running?

Could you please go into wire/core/PagesLoader.php and echo $languageID before line 813. It should return 0 and the if($languageID) condition on 813 should fail, but for some reason $languages->setLanguage($language); is being called with $language set to NULL, hence the error you are seeing.

It's almost like your version of PHP is treating if($languageID) as true, when it should be false if set to 0

If you can report on these things, hopefully we can figure out what is going wrong.

Share this post


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

hi adrian,

I hope i'm using tracy wrong in this case because the missing option is quite annoying for me. I'm debugging a lot via bd('mytest') calls in my project and when i reload i want to see all dumps based on that single reload most of the time. with the missing option i always have to clean the dump and then reload. if i dont clean the dump it gets messy and misleading sometimes (showing variable values from a previous pageload).

thanks for your help :)

Hey @bernhard - as I mentioned, I now leave the Dumps Recorder disabled by default and only enable it via the Panel Selector if I need it which is usually only if there are some weird redirects going on that Tracy is missing. The main Dumps panel is now my own version (not the Tracy core) so I can control how it looks and behaves, and also the way it stores consecutive ajax requests.

Does that make sense and work for you? I can bring back the "Preserve Dumps" option if it's really needed, but really the new "Preserve Dumps" approach is to enable the Dumps Recorder when needed and when not, just don't load it.

  • Like 2

Share this post


Link to post
Share on other sites

thanks adrian!

i didn't know that a dumps panel appears automatically when i do a " bd('test') " anywhere in my code. so i thought i have to activate the dumps recorder :)

great new feature :) (y) 

  • Like 1

Share this post


Link to post
Share on other sites

Some nice updates this morning for the Console and the Snippets Runner panels.

1) The code injection feature (the one that lets you run hooks etc at init, ready, and finished) now has better error handling. It will no longer inject code if it detects any type of error (previously it wasn't properly detecting 500 errors).

2) The Console panel now makes use of orange and red icon colors. The orange simply indicates that you are currently injecting code, and the red indicates that there is an error in your code and as such, nothing is being injected.

3) The Console panel now restores the last error to the results section on page load so if you missed the error when you clicked "Run" to register the code, you will see it again as a reminder of what needs fixing.

4) 500 errors in the Console and Snippet Runner panels now show the full error message - previously this had to be tracked down in the browser dev console's Network tab.

Hopefully these changes will be nice improvements to debugging code in the Console and Snippet Runner panels.

Let me know if you notice any problems.

Cheers!

PS I have been using the Console code injection feature for all my hook testing lately and really enjoying it.

  • Like 4

Share this post


Link to post
Share on other sites

Adrian

Upgraded from to 4.8.11 today but problem stays

i am running

PW 3.0.62 on PHP 7.0.22-0 on an ubuntu0.16.04.1

echo $languageID before line 813

returns a 0

i have a total of 4 languages installed on this instance. 

Any ideas for further investigation?

  • Like 1

Share this post


Link to post
Share on other sites

Thanks @erikvanberkum - well it is returning 0 as expected, but the first line in your error shows that setLanguage is still being called.

Could you please temporarily replace:

if($languageID) $languages->setLanguage($language);

with:

if($languageID) {
    echo 'test' . $language->name;
    //$languages->setLanguage($language);
}

and let me know what you get.

Share this post


Link to post
Share on other sites

Might sound a little insignificant to mention, but I have found myself using the GOTO Page ID feature a lot :) but it was annoying me that there was no way to open the View/Edit links in a new tabs. Well, now you can - just use your standard "new tab" shortcut: middle-click, right-click > new tab, CTRL+left-click, 3-finger click, etc - really handy!

  • Like 3

Share this post


Link to post
Share on other sites

@adrian 

Replacing this code makes it work again. Now I am able to enable and disable Tracey.

if($languageID) {
    echo 'test' . $language->name;
    //$languages->setLanguage($language);
}

I cant find the output from the echo test, language name. The default language in my installation is English.

I only have the error when i enable or disable the Tracey. When its enabled and I remove the above code it keep working properly.

 

  • Like 1

Share this post


Link to post
Share on other sites

@erikvanberkum 

I just tested on 3.0.60 (I didn't have easy access to 3.0.62 using the PW Version switcher :)) and I can actually reproduce the issue you are having.

Turns out it's a bug in the PW core in that version. Look at the difference between:

3.0.60

if($languages) $languages->setLanguage($language);

3.0.84

if($languageID) $languages->setLanguage($language);

I would recommend upgrading to 3.0.84 to fix the problem!

PS - in my experience, 3.0.84 is more stable than the current "stable" version.

  • Like 2

Share this post


Link to post
Share on other sites
On ‎28‎/‎11‎/‎2017 at 9:32 AM, adrian said:

It allows you to enter a page ID and click "View" or "Edit to be taken to the appropriate place. 

I haven't try this feature so far but the first idea that came to me was to have some kind of info about the page even without clicking on the buttons. How about an ajax loaded line showing the page title as you type, in the bottom of the panel? I think that would make the panel more versatile but of course it's only a nice-to-have kind of request :)

  • Like 1

Share this post


Link to post
Share on other sites
18 hours ago, tpr said:

How about an ajax loaded line showing the page title as you type, in the bottom of the panel?

Hi @tpr - thanks for your idea. I almost did that when building this feature the first time, but struggled to come up with the right UX. Been going around in circles for way too long on this and I am still not sure how it should look. 

I am attaching a version of Tracy that includes the admin ajax search feature embedded into the PW Info panel. It's rough in look, but it works and returns exactly the same results as the admin version. Please note that it actually only works in the backend of your site at the moment - some missing dependencies.

I know this is not really what you asked for, but I am wondering what the best combo would actually be. Would you guys make use of an ajax search? Would it make sense to combine the ID and page search into one feature? Do we want edit and view links for results searched by name, rather than ID. 

Anyway, I am happy to implement something here - just looking for feedback on what you guys would find useful.

TracyDebugger.zip

Share this post


Link to post
Share on other sites
6 hours ago, adrian said:

Anyway, I am happy to implement something here - just looking for feedback on what you guys would find useful.

The attached version of TD doesn't offer anything extra compared to the built-in admin search so I don't regard it too useful - of course on the frontend side it could be handy. In this case it would be great having a non-panel version of it, only a small input line in the TD bar, with results appearing above it, growing upwards. Probably this is harder to implement, just an idea.

See the attached image how I imagined the ajax-loaded page title (plus the template name used). It should be one line only, cropped if too long, with a small font size. Also its placeholder space should be there all the time to avoid jumping when typing.

td-ajax-title.jpg

  • Like 1

Share this post


Link to post
Share on other sites
11 hours ago, tpr said:

In this case it would be great having a non-panel version of it, only a small input line in the TD bar, with results appearing above it, growing upwards. Probably this is harder to implement, just an idea.

I'll have a think about this one - thanks for the idea.

 

11 hours ago, tpr said:

It should be one line only, cropped if too long, with a small font size. Also its placeholder space should be there all the time to avoid jumping when typing.

I have implemented this in the latest version - please take a look and let me know what you think.

  • Like 2

Share this post


Link to post
Share on other sites

Thanks, I like it. Perhaps the template link attracts the attention too much, I would go with something like this - but of course I can live with the current one too :)

td-gotopage.thumb.png.32f127f5181c847d50cf6c43d0a8d1df.png

  • Like 1

Share this post


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

Perhaps the template link attracts the attention too much, I would go with something like this

No worries - it's changed in the latest version. Thanks for the feedback!

  • Like 1

Share this post


Link to post
Share on other sites

Hi, my Tracy Debug bar has gone missing. It was in the lower right hand corner of the screen, but now there is just an icon that doesn't do anything in the lower LEFT hand corner of the screen. Before this I exported my site profile and am working on a new site, though I'm not sure what that would have to do with it. I have looked at all the options on the module settings page and no matter what I choose, nothing happens. I have now just upgraded to version 4.8.23. I'm testing locally on MAMP.

Attached are some screenshots of the icon and the errors I get in Chrome. Any ideas? Thanks!

 

 

errors.png

tracy.png

Share this post


Link to post
Share on other sites

@ryanC 

  • Do you have PW's debug mode on?
  • Any php errors being displayed or logged?
  • Any errors on the dev console's Network tab regarding Tracy files not being loaded?
  • Any issues with file permissions on the files within the Tracy folder after moving to new site?
  • Any files missing from the Tracy folder? Can you replace with a fresh set from Github?

 

  • 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   1 member

  • Similar Content

    • By Rudy
      Hi,
      I am writing a custom module that requires storing array of settings in the module config/settings.
      Is there a built-in fieldtype that allows me to store settings in an array (sort of like Repeater)?
      I tried using InputfieldAceExtended and InputfieldTextarea to store JSON array. Both times, my data was stored in the module settings (in the database) but upon reload, that information was not retrieved.
      Thanks
      Rudy
       
    • By Anssi
      A simple module to enable easy navigation between the public and the admin side of the site. After installation a green bar will appear to the upper side of the screen, containing a few navigation elements and displaying the PW version number.
      Heavily inspired by @apeisa's great AdminBar (Thanks!). I needed a bit simpler tool for my projects and as a result, this was made. Available on GitHub .

    • 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.
      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!
    • By David Karich
      Thanks to the great Pro module "RepeaterMatrix" I have the possibility to create complex repeater items. With it I have created a quite powerful page builder. Many different content modules, with many more possible design options. The RepeaterMatrix module supports the cloning of items, but only within the same page. Now I often have the case that very design-intensive pages and items are created. If you want to use this module on a different page (e.g. in the same design), you have to rebuild each item manually every time.
      With this proof of concept I have created a module which adds the feature to copy a repeater item to the clipboard so that you can paste this item to another page with the same repeater field. The module has been developed very rudimentarily so far. It is currently not possible to copy nested items. There is also no check of Min/Max. You can also only copy items that have the same field on different pages. And surely you can solve all this more elegantly with AJAX. But personally I lack the deeper understanding of the repeaters. Also missing on the Javascript side are event triggers for the repeaters, which would make it easier. Like e.g. RepeaterItemInitReady or similar.
      it would be great if @ryan would implement this functionality in the core of RepeaterMatrix. I think he has better ways to implement this. Or what do you think, Ryan?
      Everybody is welcome to work on this module and improve it, if it should not be integrated into the matrix core. Therefore I put it for testing and as download on GitHub: https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDublicate
      You can best see the functionality in the screencast: 
       
    • By anderson
      Hi,
      Please take a look at this:
      https://templatemag.com/demo/Good/
      The upper nav bar, including dropdowns like "pages" and "portfolios", what do you call this whole thing? At first I guess it's called "dropdown nav bar", but seems not.
      AND of course, what's the simplest way/module to achieve this in PW?
      Thanks in advance.