Jump to content
adrian

Tracy Debugger

Recommended Posts

Yep, that was fix.  Forgot that step.  Thanks for the quick help

  • Like 1

Share this post


Link to post
Share on other sites

Hi @adrian, I'm getting a curious error that wasn't there before. Some images on a site using $config->pagefileSecure = true; aren't being loaded anymore (worked fine before, not sure what changed). The images are being served by ProcessWire. When I open the image URL directly, I get this exception (see attachment). The image field is inside a Repeater Matrix. When I turn off Tracy Debugger, the error goes away. Not sure if it's a bug with Tracy or if it's just surfacing a deeper problem. Any idea what might be causing this?

Quote

SERVER DETAILS
ProcessWire: 3.0.155
PHP: 7.4.7
Webserver: Apache
MySQL Server: 5.5.5-10.1.44-MariaDB-0ubuntu0.18.04.1
MySQL Client: mysqlnd 7.4.7

 

 

pw-error-message.png

Share this post


Link to post
Share on other sites

Hi @MoritzLost - what version of Tracy are you running? Trying to figure out what is on line 409 as highlighted in the call stack. It doesn't seem to me like it's the latest version, but I could be wrong.

What changed that started the error? Did you update something?

 

  • Like 1

Share this post


Link to post
Share on other sites

@adrian I'll have to get back to you on monday ^^ Though when I got the error, I tried updating to the latest version and the error remained. Not 100% sure that the screenshot was taken with the current version though, sorry 😅 I haven't really changed much ... came back to the site after a week and the error was there, not sure when it started 😕 I'll try to find out more when I'm in the office ...

Share this post


Link to post
Share on other sites

Hello,

my RequestInfoPanel shows this error on all of my projects:

image.thumb.png.4de53801a6e1ff05c01689d20834491e.png

I have ProcessWire 3.0.161 dev and Tracy Debugger 4.21.17. I am on macOS with MAMP PRO 5.7.

Has anybody an idea what causes this error?

Thank you @adrian again for your great work with this module. 😀👍

Regards, Andreas

  • Like 1

Share this post


Link to post
Share on other sites

Hi @AndZyk - please try the latest version just committed.

  • Like 2

Share this post


Link to post
Share on other sites

This solves the error in my RequestInfoPanel, thank you. 😀

  • Like 1

Share this post


Link to post
Share on other sites

I just wanted to try out a barDumpBig. But I get an undefined function error:

<?php
barDumpBig($largeObject);
bdb($largeObject);

Am I missing something? I have never used it before. 😀

Regards, Andreas

Share this post


Link to post
Share on other sites

See the settings:

txiYaUs.png

  • Like 3

Share this post


Link to post
Share on other sites

Thank you. 👍

Of course I haven't looked there. 🙄

Share this post


Link to post
Share on other sites

So I am at a total loss. I was in the middle of working on a draft site and had recently updated Tracy to the latest version on one of them 4.21.19 from 4.21.17.

I was in the process of revamping the site from delayed output to markup regions and then when I went to preview (which I hadn't done) the screen was blank with the exception of Tracy. No source, no nothing. No errors. Tracy reported the page object loaded, all the children, etc.

I reverted to the old version of the templates. No difference. I compared it with another copy of the same site on a different domain that still had 4.21.17 installed. Front-end looked fine.

I updated the second site to 4.21.19 - blank screen on the front end, no errors being shown, nothing.

All else being equal, I have to assume there's something in the change from 4.21.17 to 19 - but I purged 19 from the site/modules, cleansed the copies from the FileCompiler cache directory - got rid of everything I could to remove it.

Both site are still showing blank with nothing in the PHP logs and no displayed errors. Backend still works perfectly fine.

I don't really know what to do next, but I'm pretty frustrated about the situation. If I had error codes to work with that would at least be something. If there are errors (which I could create) Tracy was reporting and displaying them. But I can't get the site templates to output anything. Not even replacing with generic echo.

I'm running 3.0.161.

Is there something in the page rendering hooks that got installed that I might need to manually remove? Any ideas on how I can get my sites back? At the moment I am probably going to pull down another site made with the same template and try doing a diff across the site/wire directories.

I don't really know how to troubleshoot a situation where no errors appear, but no markup either.

Share this post


Link to post
Share on other sites

Hi @gornycreative - sorry you're have a rough time with this. Did you properly uninstall 4.21.19, or did you just remove the files?

I know you said you aren't getting any errors, but are you talking about PHP errors only? Does the browser dev console show any JS errors? What about errors in the apache logs?

Have you done a modules refresh and clear session & cookies from the Processwire Info panel in Tracy?

Do the sites work in a different browser / incognito window?

Share this post


Link to post
Share on other sites

It's really weird. And I'm afraid to experiment too much more on other working sites as I don't want to break anything further.

I uninstalled 4.21.19 from the modules area, cleared all cache and then double checked the asset cache FileCompiler area. Turned off opcache in PHP. turned off as much caching as I could find in modules. Removed all traces of files. Purged CloudFlare cache and made sure dev mode was on.

I've turned off prepend and append and even substituted a very basic HTML file as the output template with no look-ups.

There are no PHP or LiteSpeed errors logged. There's nothing in the console.

I decided after cleaning out the system I'd reinstall Tracy fresh. What I don't understand is that it is as if the PHP is working, but the HTML is just not getting output. With devtools open there not alot going on, but Tracy has an HTML DOM that it is sitting in, which is even stranger.

I know you've pushed priority up on loading - perhaps it is possible there is a module that is failing to load immediately after? Maybe I can look at the modules table in adminer and sort by priority?

It's absolutely nuts - when I look at source for the loaded page all I get is <!--tracy debugger bar --> and then the script tags. That's in an incognito window.

Chrome puts it into a makeshift DOM but firefox has no idea what to do with it. There it is just a blank page.

 

Share this post


Link to post
Share on other sites

What I can't fathom is that you uninstalled Tracy and it's still a problem. It suggests to me that it's not Tracy related.

I am running the latest version on several different sites and different servers without any problems.

2 hours ago, gornycreative said:

I was in the process of revamping the site from delayed output to markup regions

This sounds like the likely issue - I know you said you put the old versions of the templates back and they are still broken, but with Tracy uninstalled and its folder removed, it can't be impacting things anymore.

Any chance you accidentally messed with the htaccess file?

Share this post


Link to post
Share on other sites

The thing is, I had another site built using the exact same basic template setup as the original. All that I did to that site was upgrade it from 4.21.17 to 4.21.19. Nothing else on that site was touched - it went from loading the templates fine to a blank screen with . I'd rather not sacrifice another development site to prove the point without really understanding what changed between versions.

Are you running this on 161 or 148?

The strange thing is - I set the request logger on for the site - the HTML is getting passed in the response. I have no idea why the browser is not rendering the code. Chrome is up to date (which I know can be a problem sometimes).

Share this post


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

Are you running this on 161 or 148?

Local dev is 161 (actually just updated to today's commits). At the moment, the live sites vary between 156 and 160.

Share this post


Link to post
Share on other sites

Okay.

Regarding the switch, there was no need to touch the htaccess at all.

I had a single file that included a bunch of variable sets that were global (settings factory stuff) and a few variables set from the home page (gotten through pages() ) - none of the things I pulled required access to page() and those got moved to _init.php

Everything else got moved to _main.php - which at the time was just a bunch of components in a layout that I was going to pick and choose and render in the main template file into regions - this was not supposed to be anything super crazy or elaborate.

Then, when I turned off the prepend/append and switched to a plain jane HTML hello world scenario and still got a blank page, I got even more frustrated. I split a text file into three text files - pretty routine stuff. And boom.

I do agree with you that it doesn't make sense for the HTML to still not render after uninstalling Tracy and putting the original templates back if Tracy was the problem.

I will move on from this I guess. If somehow you come across a situation where you run into the same thing, please let me know.

Share this post


Link to post
Share on other sites
23 minutes ago, gornycreative said:

I will move on from this I guess.

How can you move on at the moment - I thought your sites were still broken?

Share this post


Link to post
Share on other sites

So I found another site built off the same template that had not had Tracy installed prior. After clearing the module cache and letting it rebuild, the site broke - so it must be another module that needs some rewarming from 161.

39 minutes ago, adrian said:

How can you move on at the moment - I thought your sites were still broken?

Moving on meaning I need to start dropping other modules until the site works, since Tracy doesn't logically seem to be the issue.

Share this post


Link to post
Share on other sites

I found the culprit. It wasn't Tracy. It was another module I probably should have suspected since it has never really worked out that well for me - despite being a good idea.

Thanks for your effort in trying to help me debug this - coincidences and panic are a lousy combination.

  • Like 1

Share this post


Link to post
Share on other sites
8 hours ago, gornycreative said:

It was another module

Is it a publicly available module? If so, it would be good to know which one.

Share this post


Link to post
Share on other sites

Oh sorry - yes and I raised the issue on their module support thread.

Template Engine Factory - I'm thinking it might be related to the auto compilation switch function - I haven't dug into it because I am no longer really interested in using Smarty or Twig.

Share this post


Link to post
Share on other sites

Hi @adrian could you please add a $session->redirect after the email-sent-flag has been reset? I've had it several times the last days that I had a tab oben and got an error "file could not be removed" on reload which was caused by a ?tracy-clear-email-sent-flag-whatsoever=1 that was still left in the url.

Thx 🙂 

  • 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 Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-07-03 -- SnipWire 0.8.7 (beta) released! Fixes some small bugs and adds an indicator for TEST mode 2020-04-06 -- SnipWire 0.8.6 (beta) released! Adds support for Snipcart subscriptions and also fixes some problems 2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Multi currency support Custom order and cart fields Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  

       
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • By Sten
      Hello
      Till now I hacked something with the twig template but it works no more with new PW versions so I look forward to create a module. I am working on a site in multiple languages : French, English, Italian, German, Spanish, Portuguese, Hebrew, Russian. The new posts are entered in any language with a field for language. Till now, I got twig files to get the translations with constants defined for each part of the pages.
      So I'd like to create a module to include theses files added according to the url /fr/en/...
      Have you some observations to do before I begin about the direction to take ?
      Thank you
    • By ukyo
      Mystique Module for ProcessWire CMS/CMF
      Github repo : https://github.com/trk/Mystique
      Mystique module allow you to create dynamic fields and store dynamic fields data on database by using a config file.
      Requirements
      ProcessWire 3.0 or newer PHP 7.0 or newer FieldtypeMystique InputfieldMystique Installation
      Install the module from the modules directory:
      Via Composer:
      composer require trk/mystique Via git clone:
      cd your-processwire-project-folder/ cd site/modules/ git clone https://github.com/trk/Mystique.git Module in live reaction with your Mystique config file
      This mean if you remove a field from your config file, field will be removed from edit screen. As you see on youtube video.
      Using Mystique with your module or use different configs path, autoload need to be true for modules
      Default configs path is site/templates/configs/, and your config file name need to start with Mystique. and need to end with .php extension.
      Adding custom path not supporting anymore !
      // Add your custom path inside your module class`init` function, didn't tested outside public function init() { $path = __DIR__ . DIRECTORY_SEPARATOR . 'configs' . DIRECTORY_SEPARATOR; Mystique::add($path); } Mystique module will search site/modules/**/configs/Mystique.*.php and site/templates/Mystique.*.php paths for Mystique config files.
      All config files need to return a PHP ARRAY like examples.
      Usage almost same with ProcessWire Inputfield Api, only difference is set and showIf usage like on example.
      <?php namespace ProcessWire; /** * Resource : testing-mystique */ return [ 'title' => __('Testing Mystique'), 'fields' => [ 'text_field' => [ 'label' => __('You can use short named types'), 'description' => __('In file showIf working like example'), 'notes' => __('Also you can use $input->set() method'), 'type' => 'text', 'showIf' => [ 'another_text' => "=''" ], 'set' => [ 'showCount' => InputfieldText::showCountChars, 'maxlength' => 255 ], 'attr' => [ 'attr-foo' => 'bar', 'attr-bar' => 'foo' ] ], 'another_text' => [ 'label' => __('Another text field (default type is text)') ] ] ]; Example:
      site/templates/configs/Mystique.seo-fields.php <?php namespace ProcessWire; /** * Resource : seo-fields */ return [ 'title' => __('Seo fields'), 'fields' => [ 'window_title' => [ 'label' => __('Window title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'attr' => [ 'placeholder' => __('Enter a window title') ] ], 'navigation_title' => [ 'label' => __('Navigation title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'showIf' => [ 'window_title' => "!=''" ], 'attr' => [ 'placeholder' => __('Enter a navigation title') ] ], 'description' => [ 'label' => __('Description for search engines'), 'type' => Mystique::TEXTAREA, 'useLanguages' => true ], 'page_tpye' => [ 'label' => __('Type'), 'type' => Mystique::SELECT, 'options' => [ 'basic' => __('Basic page'), 'gallery' => __('Gallery'), 'blog' => __('Blog') ] ], 'show_on_nav' => [ 'label' => __('Display this page on navigation'), 'type' => Mystique::CHECKBOX ] ] ]; Searching data on Mystique field is limited. Because, Mystique saving data to database in json format. When you make search for Mystique field, operator not important. Operator will be changed with %= operator.
      Search example
      $navigationPages = pages()->find('my_mystique_field.show_on_nav=1'); $navigationPages = pages()->find('my_mystique_field.page_tpye=gallery');
    • By Robin S
      This is a module I made as an experiment a while ago and never got around to releasing publicly. At the time it was prompted by discussions around using Repeater fields for "page builder" purposes, where the depth feature could possibly be used for elements that would be nested inside other elements. I thought it would be useful to enforce some depth rules and translate the depth data into a multi-dimensional array structure.
      I'm not using this module anywhere myself but maybe it's useful to somebody.
      Repeater Depth Helper
      This module does two things relating to Repeater fields that have the "Item depth" option enabled:
      It enforces some depth rules for Repeater fields on save. Those rules are:
      The first item must have a depth of zero. Each item depth must not be more than one greater than previous item depth. It provides a RepeaterPageArray::getDepthStructure helper method that returns a nested depth structure for a Repeater field value.
      Helper method
      The module adds a RepeaterPageArray::getDepthStructure method that returns a multi-dimensional array where the key is the page ID and the value is an array of nested "child" items, or null if there are no nested children.
      Example

      The module doesn't make any assumptions about how you might want to use the depth structure array, but here is a way you might use it to output a nested unordered list.
      // Output a nested unordered list from a depth structure array function outputNestedList($depth_structure, $repeater_items) { $out = "<ul>"; foreach($depth_structure as $page_id => $nested_children) { $out .= "<li>" . $repeater_items->get("id=$page_id")->title; // Go recursive if there are nested children if(is_array($nested_children)) $out .= outputNestedList($nested_children, $repeater_items); $out .= "</li>"; } $out .= "</ul>"; return $out; } $repeater_items = $page->my_repeater; $depth_structure = $repeater_items->getDepthStructure(); echo outputNestedList($depth_structure, $repeater_items);
       
      https://github.com/Toutouwai/RepeaterDepthHelper
      https://modules.processwire.com/modules/repeater-depth-helper/
    • 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 If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
×
×
  • Create New...