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

@bernhard - good idea. Fixed in the latest version.

  • Thanks 1

Share this post


Link to post
Share on other sites

Hi Adrian
I was updating my site a few minutes ago and it started displaying a 500 error. When I turned on notifications, I saw the following error.

Fatal error: Cannot declare class TracyDebugger, because the name is already in use in /home/p752009485/public_html/site/assets/cache/FileCompiler/site/modules/TracyDebugger/TracyDebugger.module.php on line 19

 

Is it ok to manually remove the Module somehow?

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 David Karich
      ProcessWire InputfieldRepeaterMatrixDuplicate
      Thanks to the great ProModule "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 a content module on a different page (e.g. in the same design), you have to rebuild each item manually every time.
      This module extends the commercial ProModule "RepeaterMatrix" by the function to duplicate repeater items from one page to another page. The condition is that the target field is the same matrix field from which the item is duplicated. This module is currently understood as proof of concept. There are a few limitations that need to be considered. The intention of the module is that this functionality is integrated into the core of RepeaterMatrix and does not require an extra module.
      Check out the screencast
      What the module can do
      Duplicate multible repeater items from one page to another No matter how complex the item is Full support for file and image fields Multilingual support Support of Min and Max settings Live synchronization of clipboard between multiple browser tabs. Copy an item and simply switch the browser tab to the target page and you will immediately see the past button Support of multiple RepeaterMatrix fields on one page Configurable which roles and fields are excluded Configurable dialogs for copy and paste Duplicated items are automatically pasted to the end of the target field and set to hidden status so that changes are not directly published Automatic clipboard update when other items are picked Automatically removes old clipboard data if it is not pasted within 6 hours Delete clipboard itself by clicking the selected item again Benefit: unbelievably fast workflow and content replication What the module can't do
      Before an item can be duplicated in its current version, the source page must be saved. This means that if you make changes to an item and copy this, the old saved state will be duplicated Dynamic loading is currently not possible. Means no AJAX. When pasting, the target page is saved completely No support for nested repeater items. Currently only first level items can be duplicated. Means a repeater field in a repeater field cannot be duplicated. Workaround: simply duplicate the parent item Dynamic reloading and adding of repeater items cannot be registered. Several interfaces and events from the core are missing. The initialization occurs only once after the page load event Changelog
      2.0.0
      Feature: Copy multiple items at once! The fundament for copying multiple items was created by @Autofahrn - THX! Feature: Optionally you can disable the copy and/or paste dialog Bug fix: A fix suggestion when additional and normal repeater fields are present was contributed by @joshua - THX! 1.0.4
      Bug fix: Various bug fixes and improvements in live synchronization Bug fix: Items are no longer inserted when the normal save button is clicked. Only when the past button is explicitly clicked Feature: Support of multiple repeater fields in one page Feature: Support of repeater Min/Max settings Feature: Configurable roles and fields Enhancement: Improved clipboard management Enhancement: Documentation improvement Enhancement: Corrected few typos #1 1.0.3
      Feature: Live synchronization Enhancement: Load the module only in the backend Enhancement: Documentation improvement 1.0.2
      Bug fix: Various bug fixes and improvements in JS functions Enhancement: Documentation improvement Enhancement: Corrected few typos 1.0.1
      Bug fix: Various bug fixes and improvements in the duplication process 1.0.0
      Initial release Support this module
      If this module is useful for you, I am very thankful for your small donation: Donate 5,- Euro (via PayPal – or an amount of your choice. Thank you!)
      Download this module (Version 2.0.0)
      > Github: https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate
      > PW module directory: https://modules.processwire.com/modules/inputfield-repeater-matrix-duplicate/
      > Old stable version (1.0.4): https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate/releases/tag/1.0.4
    • By Robin S
      A new module that hasn't had a lot of testing yet. Please do your own testing before deploying on any production website.
      Custom Paths
      Allows any page to have a custom path/URL.
      Note: Custom Paths is incompatible with the core LanguageSupportPageNames module. I have no experience working with LanguageSupportPageNames or multi-language sites in general so I'm not in a position to work out if a fix is possible. If anyone with multi-language experience can contribute a fix it would be much appreciated!
      Screenshot

      Usage
      The module creates a field named custom_path on install. Add the custom_path field to the template of any page you want to set a custom path for. Whatever path is entered into this field determines the path and URL of the page ($page->path and $page->url). Page numbers and URL segments are supported if these are enabled for the template, and previous custom paths are managed by PagePathHistory if that module is installed.
      The custom_path field appears on the Settings tab in Page Edit by default but there is an option in the module configuration to disable this if you want to position the field among the other template fields.
      If the custom_path field is populated for a page it should be a path that is relative to the site root and that starts with a forward slash. The module prevents the same custom path being set for more than one page.
      The custom_path value takes precedence over any ProcessWire path. You can even override the Home page by setting a custom path of "/" for a page.
      It is highly recommended to set access controls on the custom_path field so that only privileged roles can edit it: superuser-only is recommended.
      It is up to the user to set and maintain suitable custom paths for any pages where the module is in use. Make sure your custom paths are compatible with ProcessWire's $config and .htaccess settings, and if you are basing the custom path on the names of parent pages you will probably want to have a strategy for updating custom paths if parent pages are renamed or moved.
      Example hooks to Pages::saveReady
      You might want to use a Pages::saveReady hook to automatically set the custom path for some pages. Below are a couple of examples.
      1. In this example the start of the custom path is fixed but the end of the path will update dynamically according to the name of the page:
      $pages->addHookAfter('saveReady', function(HookEvent $event) { $page = $event->arguments(0); if($page->template == 'my_template') { $page->custom_path = "/some-custom/path-segments/$page->name/"; } }); 2. The Custom Paths module adds a new Page::realPath method/property that can be used to get the "real" ProcessWire path to a page that might have a custom path set. In this example the custom path for news items is derived from the real ProcessWire path but a parent named "news-items" is removed:
      $pages->addHookAfter('saveReady', function(HookEvent $event) { $page = $event->arguments(0); if($page->template == 'news_item') { $page->custom_path = str_replace('/news-items/', '/', $page->realPath); } }); Caveats
      The custom paths will be used automatically for links created in CKEditor fields, but if you have the "link abstraction" option enabled for CKEditor fields (Details > Markup/HTML (Content Type) > HTML Options) then you will see notices from MarkupQA warning you that it is unable to resolve the links.
      Installation
      Install the Custom Paths module.
      Uninstallation
      The custom_path field is not automatically deleted when the module is uninstalled. You can delete it manually if the field is no longer needed.
       
      https://github.com/Toutouwai/CustomPaths
      https://modules.processwire.com/modules/custom-paths/
    • By teppo
      Hey folks!
      I'm happy to finally introduce a project I've been working on for quite a while now: it's called Wireframe, and it is an output framework for ProcessWire.
      Note that I'm posting this in the module development area, maily because this project is still in rather early stage. I've built a couple of sites with it myself, and parts of the codebase have been powering some pretty big and complex sites for many years now, but this should still be considered a soft launch 🙂
      --
      Long story short, Wireframe is a module that provides the "backbone" for building sites (and apps) with ProcessWire using an MVC (or perhaps MVVM... one of those three or four letter acronyms anyway) inspired methodology. You could say that it's an output strategy, but I prefer the term "output framework", since in my mind the word "strategy" means something less tangible. A way of doing things, rather than a tool that actually does things.
      Wireframe (the module) provides a basic implementation for some familiar MVC concepts, such as Controllers and a View layer – the latter of which consists of layouts, partials, and template-specific views. There's no "model" layer, since in this context ProcessWire is the model. As a module Wireframe is actually quite simple – not even nearly the biggest one I've built – but there's still quite a bit of stuff to "get", so I've put together a demo & documentation site for it at https://wireframe-framework.com/.
      In addition to the core module, I'm also working on a couple of site profiles based on it. My current idea is actually to keep the module very light-weight, and implement most of the "opinionated" stuff in site profiles and/or companion modules. For an example MarkupMenu (which I released a while ago) was developed as one of those "companion modules" when I needed a menu module to use on the site profiles.
      Currently there are two public site profiles based on Wireframe:
      site-wireframe-docs is the demo&docs site mentioned above, just with placeholder content replaced with placeholder content. It's not a particularly complex site, but I believe it's still a pretty nice way to dig into the Wireframe module. site-wireframe-boilerplate is a boilerplate (or starter) site profile based on the docs site. This is still very much a work in progress, but essentially I'm trying to build a flexible yet full-featured starter profile you can just grab and start building upon. There will be a proper build process for resources, it will include most of the basic features one tends to need from site to site, etc. --
      Requirements and getting started:
      Wireframe can be installed just like any ProcessWire module. Just clone or download it to your site/modules/ directory and install. It doesn't, though, do a whole lot of stuff on itself – please check out the documentation site for a step-by-step guide on setting up the directory structure, adding the "bootstrap file", etc. You may find it easier to install one of the site profiles mentioned above, but note that this process involves the use of Composer. In the case of the site profiles you can install ProcessWire as usual and download or clone the site profile directory into your setup, but after that you should run "composer install" to get all the dependencies – including the Wireframe module – in place. Hard requirements for Wireframe are ProcessWire 3.0.112 and PHP 7.1+. The codebase is authored with current PHP versions in mind, and while running it on 7.0 may be possible, anything below that definitely won't work. A feature I added just today to the Wireframe module is that in case ProcessWire has write access to your site/templates/ directory, you can use the module settings screen to create the expected directories automatically. Currently that's all, and the module won't – for an example – create Controllers or layouts for you, so you should check out the site profiles for examples on these. (I'm probably going to include some additional helper features in the near future.)
      --
      This project is loosely based on an earlier project called pw-mvc, i.e. the main concepts (such as Controllers and the View layer) are very similar. That being said, Wireframe is a major upgrade in terms of both functionality and architecture: namespaces and autoloader support are now baked in, the codebase requires PHP 7, Controllers are classes extending \Wireframe\Controller (instead of regular "flat" PHP files), implementation based on a module instead of a collection of drop-in files, etc.
      While Wireframe is indeed still in a relatively early stage (0.3.0 was launched today, in case version numbers matter) for the most part I'm happy with the way it works, and likely won't change it too drastically anytime soon – so feel free to give it a try, and if you do, please let me know how it went. I will continue building upon this project, and I am also constantly working on various side projects, such as the site profiles and a few unannounced helper modules.
      I should probably add that while Wireframe is not hard to use, it is more geared towards those interested in "software development" type methodology. With future updates to the module, the site profiles, and the docs I hope to lower the learning curve, but certain level of "developer focus" will remain. Although of course the optimal outcome would be if I could use this project to lure more folks towards that end of the spectrum... 🙂
      --
      Please let me know what you think – and thanks in advance!
    • By tcnet
      PageViewStatistic for ProcessWire is a module to log page visits of the CMS. The records including some basic information like IP-address, browser, operating system, requested page and originate page. Please note that this module doesn't claim to be the best or most accurate.
      Advantages
      One of the biggest advantage is that this module doesn't require any external service like Google Analytics or similar. You don't have to modify your templates either. There is also no JavaScript or image required.
      Disadvantages
      There is only one disadvantage. This module doesn't record visits if the browser loads the page from its browser cache. To prevent the browser from loading the page from its cache, add the following meta tags to the header of your page:
      <meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate" /> <meta http-equiv="Pragma" content="no-cache" /> <meta http-equiv="Expires" content="0" /> How to use
      The records can be accessed via the Setup-menu of the CMS backend. The first dropdown control changes the view mode. There are 4 different view modes.
      View mode "Day" shows all visits of the selected day individually with IP-address, browser, operating system, requested page and originate page. Click the update button to see new added records. View mode "Month" shows the total of all visitors per day from the first to the last day of the selected month. View mode "Year" shows the total of all visitors per month from the first to the last month of the selected year. View mode "Total" shows the total of all visitors per year for all recorded years. Please note that multiple visits from the same IP address within the selected period are counted as a single visitor.
      Settings
      You can access the module settings by clicking the Configuration button at the bottom of the records page. The settings page is also available in the menu: Modules->Configure->ProcessPageViewStat.
      IP2Location
      This module uses the IP2Location database from: http://www.ip2location.com. This database is required to obtain the country from the IP address. IP2Location updates this database at the begin of every month. The settings of ProcessPageViewStat offers the ability to automatically download the database monthly. Please note, that automatically download will not work if your webspace doesn't allow allow_url_fopen.
      Dragscroll
      This module uses DragScroll. A JavaScript available from: http://github.com/asvd/dragscroll. Dragscroll adds the ability in view mode "Day" to drag the records horizontally with the mouse pointer.
      parseUserAgentStringClass
      This module uses the PHP class parseUserAgentStringClass available from: http://www.toms-world.org/blog/parseuseragentstring/. This class is required to filter out the browser type and operating system from the server request.
      Special Feature
      PageViewStatistic for ProcessWire can record the time a visitor viewed the page. This feature is deactivated by default. To activate open the module configuration page and activate "Record view time". If activated you will find a new column "S." in the records which means the time of view in seconds. With every page request, a Javascript code is inserted directly after the <body> tag. Every time the visitor switches to another tab or closes the tab, this script reports the number of seconds the tab was visible. The initial page request is recorded only as a hyphen (-).
       
    • By MoritzLost
      This module allows you to integrate hCaptcha bot / spam protection into ProcessWire forms. hCaptcha is a great alternative to Google ReCaptcha, especially if you are in the EU and need to comply with privacy regulations.

      The development of this module is sponsored by schwarzdesign.
      The module is built as an Inputfield, allowing you to integrate it into any ProcessWire form you want. It's primarily intended for frontend forms and can be added to Form Builder forms for automatic spam protection. There's a step-by-step guide for adding the hCaptcha widget to Form Builder forms in the README, as well as instructions for API usage.
      Features
      Inputfield that displays an hCaptcha widget in ProcessWire forms. The inputfield verifies the hCaptcha response upon submission, and adds a field error if it is invalid. All hCaptcha configuration options for the widget (theme, display size etc) can be changed through the inputfield configuration, as well as programmatically. hCaptcha script options can be changed through a hook. Error messages can be translated through ProcessWire's site translations. hCaptcha secret keys and site-keys can be set for each individual inputfield or globally in your config.php. Error codes and failures are logged to help you find configuration errors. Please check the README for setup instructions.
      Links
      Github Repository and documentation InputfieldHCaptcha in the module directory Screenshots (configuration)

      Screenshots (hCaptcha widget)

       
       

       
×
×
  • Create New...