adrian

Tracy Debugger

Recommended Posts

Hi @adrian, I've an issue to report:

Error: ProcesswireInfoPanel
exception 'ErrorException' with message 'Undefined index: HTTP_MOD_REWRITE' in .../site/assets/cache/FileCompiler/site/modules/TracyDebugger/ProcesswireInfoPanel.inc:467
Stack trace:
#0 .../site/assets/cache/FileCompiler/site/modules/TracyDebugger/ProcesswireInfoPanel.inc(467): Tracy\Bar->Tracy\{closure}(8, 'Undefined index...', '...', 467, Array)
#1 .../site/assets/cache/FileCompiler/site/modules/TracyDebugger/tracy-master/src/Tracy/Bar.php(127): ProcesswireInfoPanel->getPanel()
#2 .../site/assets/cache/FileCompiler/site/modules/TracyDebugger/tracy-master/src/Tracy/Bar.php(81): Tracy\Bar->renderPanels()
#3 .../site/assets/cache/FileCompiler/site/modules/TracyDebugger/tracy-master/src/Tracy/Debugger.php(266): Tracy\Bar->render()
#4 [internal function]: Tracy\Debugger::shutdownHandler()
#5 {main}

I get this when my MAMP Pro's PHP mode is set to "CGI Mode" and the "Versions List" is turned on.

I have not found too much on this so called "CGI mode", only this:

http://documentation.mamp.info/en/MAMP-PRO-Mac/Servers-and-Services/Apache/

As far as I can see, this mode means the cgi_module is used, so I get the error, but when MAMP Pro's "module mode" is used instead, all is fine. According to PHP Info REDIRECT_HTTP_MOD_REWRITE is on, so it seems to be a strange issue to me.

 

  • Like 1

Share this post


Link to post
Share on other sites

Thanks @szabesz - it should be fixed in the latest version.

I also added a "*confirmed false" to the mod_security entry when we know it's definitely disabled. I am pretty sure this should be accurate, but would be keen to hear reports from you guys about this. If it doesn't have this "*confirmed false" text, and it is reported to be Off, we can't be certain because it's a sign that PHP is in PHP-FPM (CGI) mode and we may not be able to detect it. As far as I can tell if it reports it as On, then I think we can be certain of this no matter what mode PHP is in.

  • Like 1

Share this post


Link to post
Share on other sites

Thanks Adrien, "Undefined index: HTTP_MOD_REWRITE" is gone with even in "CGI mode".

About CGI mode with MAMP Pro:

in v3.3.2 I used to get:

  • non CGI mode: mod_rewrite: 1, mod_security: 
  • CGI mode: "Undefined index: HTTP_MOD_REWRITE"...

now in v3.3.3:

  • non CGI mode: mod_rewrite: 1, mod_security: *confirmed off 
  • CGI mode: mod_rewrite: , mod_security

So it does detect them properly when not in CGI mode, but just as you have noted they cannot be confirmed otherwise. It might be a good idea to use a short phrase, something like "probably not installed". What do you think? Also, the status of mod_rewrite seems to be uncertain too.

BTW, is it possible to have the Inputfield Fieldsets be closed by default? I keep getting lost when all of them are open, and they are always open even after saving the settings.

  • Like 1

Share this post


Link to post
Share on other sites

Hi Adrian,

I upgraded to 3.3.3 this morning, and noticed that the debug bar is no longer adding rows for AJAX requests, which I need to measure. Any idea what may have broken this?

Using PW3.

Thanks :)

  • Like 1

Share this post


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

I upgraded to 3.3.3 this morning, and noticed that the debug bar is no longer adding rows for AJAX requests, which I need to measure. Any idea what may have broken this?

Sorry Mike - looks like it was an issue with a recent change to the Tracy core. I have restored the core to an earlier commit and pushed a new version here which fixes the AJAX bar.

 

  • Like 1

Share this post


Link to post
Share on other sites

Hi @adrian,

Apologies if this has already been asked and answered before. When using the "Editor Protocol Handler" feature, the linked error is often to a file in the file compiler cache, e.g. "...\assets\cache\FileCompiler\site\templates\home.php".

But to correct the error you actually want to open "\site\templates\home.php" for editing. Would it be possible to rewrite links to compiled files so they point at the original uncompiled file instead?

  • Like 1

Share this post


Link to post
Share on other sites
6 minutes ago, Robin S said:

Would it be possible to rewrite links to compiled files so they point at the original uncompiled file instead?

It should work that way. At least it used to work. I have disabled the compiler completely in all my sites so cannot test it quickly, but I was the first one to raise this issue an Adrian had solved it. If the issue is back, it was not intentional, I think.

  • Like 2

Share this post


Link to post
Share on other sites

I have enabled the compiler just to test it and it works as expected for me.

  • Like 1

Share this post


Link to post
Share on other sites
39 minutes ago, szabesz said:

I have enabled the compiler just to test it and it works as expected for me.

That's strange. I have the latest Tracy and PW versions, and if I introduce a deliberate error into home.php I get this:

tracy.png

Share this post


Link to post
Share on other sites
On 10/1/2016 at 11:40 PM, Robin S said:

That's strange. I have the latest Tracy and PW versions, and if I introduce a deliberate error into home.php I get this:

tracy.png

That is weird - it's certainly working for me. I think the problem is the "...\" at the start of the path.

Would you mind having a play around with the replacement code (https://github.com/adrianbj/TracyDebugger/blob/90d0fd95a5f7b77df044c4a66dc5bd01e97d41e5/TracyDebugger.module#L299-L311) to see if you can come up with a working solution. The thing that makes it a little complicated is that the Tracy guys stuck with my initial suggestion of strtr rather than going with my revised str_replace option which would have given much more flexibility since strtr won't replace the same substring more than once. What this means is that you must replace the entire path up to and including "FileCompiler/". Because yours is for some reason returning a relative, rather than absolute path, the replacement isn't being made.

Unfortunately I don't have a Windows box to test on, so I think I will have trouble reproducing, although I think it might also be the way your server is configured. I would certainly like to implement a working solution though if we can get one.

Share this post


Link to post
Share on other sites

Just spent an hour or so learning how to set-up custom scheme handlers in Arch linux to try this feature out and it's now working fine for me after a few false leads. This will really come in handy - thanks Adrian and the Tracy devs!

  • Like 3

Share this post


Link to post
Share on other sites
On 3/10/2016 at 2:00 AM, adrian said:

Would you mind having a play around with the replacement code (https://github.com/adrianbj/TracyDebugger/blob/90d0fd95a5f7b77df044c4a66dc5bd01e97d41e5/TracyDebugger.module#L299-L311) to see if you can come up with a working solution.

Hi @adrian,

I have had a look at this and I think the problem is due to the direction of file path slashes on Windows versus Unix.

You can see mixed forward and backslashes in this screenshot of the Template Resources panel.

tracy-1.png

It looks wrong but the links to the editor still work okay. Edit: apparently it's no big deal to mix forward and backslashes within a path for Windows.

In terms of the error notice links containing paths to the file compiler cache, this is because having the slashes around the wrong way prevents the str_replace in Helpers::editorMapping from replacing the necessary section of the path. I got the links to work by adding the following after line 303 in TracyDebugger.module

$compilerCachePath = str_replace('/', '\\', $compilerCachePath);

Of course this is not a real solution. But maybe there is some cross-platform way to deal with file paths?

  • Like 2

Share this post


Link to post
Share on other sites

Thanks @Robin S for looking into this.

I am bad about not remembering Windows path issues. For the most part they seem to be handled quite well by PHP and don't actually need "DIRECTORY_SEPARATOR", but I think the issue is when you're doing replacements. Could you please test removing your str_replace line and modifying 303 to the following which uses DIRECTORY_SEPARATOR on the end instead of the forward slash:

$compilerCachePath = isset($this->config->fileCompilerOptions['cachePath']) ? $this->config->fileCompilerOptions['cachePath'] : $this->config->paths->cache . 'FileCompiler' . DIRECTORY_SEPARATOR;

If that works as expected, I'll try to make similar changes throughout Tracy to deal with the mixed forward/back slash links like in the Template Resources panel.

  • Like 1

Share this post


Link to post
Share on other sites

@adrian - sorry for the delay. The change you suggested doesn't allow the file compiler path to be successfully replaced.

For me the $compilerCachePath variable before the change is...

D:/Websites/pw3-testing/site/assets/cache/FileCompiler/

...and after the change it is...

D:/Websites/pw3-testing/site/assets/cache/FileCompiler\

...but to successfully replace the link to the editor it needs to be...

D:\Websites\pw3-testing\site\assets\cache\FileCompiler\

I originally thought my str_replace suggestion was hacky but now I see there is already something similar in the nette/tracy source so maybe it is an okay way to deal with these path issues?

Share this post


Link to post
Share on other sites

No problem @Robin S - the catch with your:

$compilerCachePath = str_replace('/', '\\', $compilerCachePath);

fix is that it breaks the paths for us Mac/Linux folks. I feel like this shouldn't be that hard to sort out, but not being able to test doesn't help.I wonder if:

$compilerCachePath = realpath($compilerCachePath);

or something along those lines might work?

Share this post


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

$compilerCachePath = realpath($compilerCachePath);

This pretty much works - it just misses out the trailing slash from the original $compilerCachePath so results in a double slash in the link URL. But this could be corrected:

$compilerCachePath = realpath($compilerCachePath) . DIRECTORY_SEPARATOR;

Alternatively, slash replacement could be done conditional on what the directory separator is (thereby distinguishing Windows from Mac/Linux):

if(DIRECTORY_SEPARATOR == '\\') $compilerCachePath = str_replace('/', '\\', $compilerCachePath);

Or no conditional needed for this one:

$compilerCachePath = str_replace('/', DIRECTORY_SEPARATOR, $compilerCachePath);

 

  • Like 1

Share this post


Link to post
Share on other sites

Thanks @Robin S - really appreciate you testing all those options. It sounds like you are suggesting the last option is likely the best, which sounds good to me.

Before I commit that change, could you please check that editor paths work everywhere in Tracy on Windows.

Key places to check are:

  • errors panel
  • "bluescreen" fatal errors
  • links to file/line from dumps panel entries
  • log panels (does clicking on the message take you to that line in the log file)
  • template resources - page number links from variables, functions, other files etc
  • ToDo panel
  • PW Info panel - edit the template file icon

The reason to check all these is that many of them are not built by the Tracy core editorMapping option.

Thanks again!

PS - I am not suggesting that change of yours would break them if these other links were working already - I just want to make sure that there aren't any other situations we need to cover for Windows.

Share this post


Link to post
Share on other sites

Happy to do that. I'm just about to head away for a few days but will go through systematically when I'm back.

  • Like 1

Share this post


Link to post
Share on other sites

Just wanted to let you know you guys know that there have been a few tweaks to the console panel of late - nothing major, but improvements to error handling, and also notes that say "Processing" and "Completed" so you know that your script is running and when it has completed which is very handy when you are running a script that manipulates content, but doesn't output anything.

I was also just reminded of the outstanding issues with the AJAX bar and the PW SessionHandlerDB module - I was testing something on an older site (built when I used to install SessionHandlerDB as a matter of course) and couldn't figure out why bd() calls from the console panel weren't triggering the ajax bar to load. I usually use d() from the console panel so the results are right there and you don't need to refer to the dumps/dumps recorder panel, seeing the bd() reminded me that it's still not sorted.

Anyway, just wanted to remind everyone who uses SessionHandlerDB about this in case you didn't know / forgot like I did :)

 

  • Like 3

Share this post


Link to post
Share on other sites
On 9/10/2016 at 6:51 PM, adrian said:

Before I commit that change, could you please check that editor paths work everywhere in Tracy on Windows.

Key places to check are:

  • errors panel
  • "bluescreen" fatal errors
  • links to file/line from dumps panel entries
  • log panels (does clicking on the message take you to that line in the log file)
  • template resources - page number links from variables, functions, other files etc
  • ToDo panel
  • PW Info panel - edit the template file icon

Hi @adrian - with the change, the editor paths are working properly for me in all of these places.

  • Like 2

Share this post


Link to post
Share on other sites
2 hours ago, Robin S said:

Hi @adrian - with the change, the editor paths are working properly for me in all of these places.

Thanks @Robin S - that change was incorporated into the core already, so glad it works everywhere.

Thanks again for figuring out the change that was needed and for your thorough testing!

  • Like 2

Share this post


Link to post
Share on other sites
On 9/26/2016 at 10:32 PM, tpr said:

Folks at Nette are on fire :) And adrian keeps the pace :)

Btw, what about a shorthand syntax to bd()? I always have to search the docs or my previous code to get the name of the params. Something like bd(var, title, 3000, 10) would be much simpler. In fact what I need most of the time is var, maxLength, and perhaps maxDepth. But perhaps it's just me :)

Sorry for the delay on this - just thinking about it again now.

Now that I am using the LIVE option with bd(), I think that we can override depth and length limits completely. I have been playing with a new setting that makes these calls effectively have no limits by setting the depth to 99 and the length to 999999.

Screen Shot 2016-10-15 at 12.01.18 PM.png

I have been playing with it a bit here and seems to be great. One thing to keep in mind is that because Tracy's LIVE dump method renders object/array levels as you open them, setting the maxDepth so high won't actually do anything to what you see in an object/array that has been stored by the Dumps Recorder (with Preserve Dumps checked) after a page reload, but other than that, I think it works just fine, but I would really like you guys to keep an eye on things and let me know if you notice any issues.

Finally, this change does not affect items sent to the error bluescreen or the variables in the Template Resources panel, or the PW Info panel etc - these currently still rely on the maxDepth and maxLength settings in the module config.

I am not completely convinced this is a good idea yet, but I am going to leave this checked here and see how it goes. If you try it out, please let me know if you have any problems.

  • Like 1

Share this post


Link to post
Share on other sites

Thanks! For me this should be OK but will report if something goes wrong.

  • Like 2

Share this post


Link to post
Share on other sites

hi adrian,

would it be hard to get the possibility to have multiple console windows open at a time? it would be nice in some cases (for example one to create some stuff via api, eg fields or templates) and one to delete it - would be great here for testing install and uninstall method from a new module. that way you could test things really quickly. at the moment when you open the console in a new window, it loads in the "_blank" window and if you open the next console it reloads that window instead of opening a new one.

or maybe there's already a better way of doing this?

thanks :)

update: in that case it is really easy to do that, so please don't put any effort in this if you think it could not be of use in other scenarios...

$m = $modules->get('sample_module');
$m->uninstall();
$m->install();
$m->uninstall();

update2:

i still think it would be nice to have such a possibility! or at least have the option to DISABLE the code remember feature, as this overwrites the code of the current browser tab when you open the panel again. if that would not be the case we would be able to have multiple browser tabs open with multiple tracy bars with multiple console-windows. or maybe an option that the console panel does NOT close automatically? i don't know when it closes and when not. sometimes it stays open. i have not found a regularity here...

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 thomasaull
      Some time ago I created a site profile for creation of a REST API with ProcessWire. Since I kept struggeling with updating stuff between different projects which use this, I decided to convert it into a module. It is now ready for testing: https://github.com/thomasaull/RestApi
      Additionally I added a few small features:
      automatic creation of JWT Secret at module install routes can be flagged as auth: false, which makes them publicly accessible even though JWT Auth is activated in module settings To check things out, download and install the module and check the folder /site/api for examples.
      If you find any bugs or can think of improvements, please let me know!
    • By kongondo
      Sites Manager
       
      16 September 2018:
      FOR NOW, PLEASE DO NOT USE THIS MODULE IN A PRODUCTION SITE. A  RECENT ProcessWire UPDATE HAS BROKEN THE MODULE. I AM WORKING ON A FIX.
       
      ################
       
      Sites Manager is a module for ProcessWire that allows Superusers to easily create/install ProcessWire sites on the same serverspace the module is running in. Only Superusers can use the module. You can create both stand-alone and multi-sites.
       
      Single/Stand-alone Sites
      Stand-alone or single-sites are sites that will run in their own document root/directory with their own wire and site folders, .htaccess, index.php, etc. In other words, a normal ProcessWire site.
      Multiple Sites
      Multi-sites are sites that will run off one wire folder (shared amongst two or more sites) each having their own site folder and database. In this regard, it is important to note that Sites Manager is not in itself a multiple sites solution! Rather, it is a utility that helps you create multi-sites to be run using the ProcessWire core multiple sites feature. For more on this core feature, see the official ProcessWire documentation, specifically the solution referred to as Option #1.
      Option #1 approach requires the site admin to initially install ProcessWire in a temporary directory for each new site. The directory then needs to be renamed as site-xxx, where ‘xxx’ is any name you want to use to differentiate the installation from other sites, before it is moved to the webroot. For instance, site-mysite, site-another, site-whatever. In addition, the /wire/index.config.php file must be copied/moved to the webroot. Each time a site is added, the index.config.php has to be edited to add ‘domain’ => ‘site-directory’ key=>value pairs for the site. This process can become a bit tedious. This module aims to automate the whole multi-site site creation process.
      The module is based off the official ProcessWire installer. Creating a site is as simple as completing and submitting a single form! You also have the option to type and paste values or reuse a pre-defined install configuration.
       
      The module will:
      Install a ProcessWire site in your named directory, applying chmod values as specified
      Move the directory to your webroot
      Update/Create a Superuser account as per the submitted form, including setting the desired admin theme and colour
      For multi sites, update sites.json (used by index.config.php to get array of installed sites)
       
      For multi sites, the only difference in relation to the core multi-sites index.config.php is that this file is slightly different from the one that ships with ProcessWire.
      Download from GitHub: Sites Manager (Beta Release)
      Features
      Install unlimited number of sites in one (multi-sites) or independent (single-site) ProcessWire installs. Install by completing a Form, Typing or pasting in configurations or using pre-created install configurations. Choose an Admin Theme to auto-install along with the site installation. For single-sites installation, download, save and reuse ProcessWire versions of your choice. Install and maintain site profiles for reuse to create other sites. Create install configurations to speed up installation tasks. Client and server-side validation of site creation values. Edit uploaded profiles (e.g., replace profile file). Lock installed sites, configurations and profiles to prevent editing. Bulk delete items such as site profiles, installed site directories and/or databases (confirmation required for latter two). View important site details (admin login, chmod, etc). Links to installed sites home and admin pages. Timezones auto-complete/-suggest. Pre-requisites, Installation & Usage
      Please see the documentation.
      Technicalities/Issues
      Only Superusers can use the module.
      ProcessWire 2.7 - 3.x compatible
      Currently using ProcessWire 2.7 installer (install.php)
      For multi-sites, potential race condition when sites.json is being updated on a new site install vs. index.config.php accessing the json file?
      Not tested with sub-directory installs (for instance localhost/pw/my-site-here/)
      Currently not doing the extra/experimental database stuff (database charset and engine)
      Future Possibilities
      Install specified modules along with the ProcessWire install
      Profile previews?
      Credits
      @ryan: for the ProcessWire installer
      @abdus: for the index.config.php reading from JSON idea
      @swampmusic: for the challenge
      Video Demo
      Demo  showing how quick module works on a remote server [YMMV!]. Video shows downloading and processing two versions of ProcessWire (~takes 7 seconds) and installing a single/stand-alone ProcessWire 3 site using the new Admin Theme UI Kit (~2 seconds) on a remote server.
       
      Screens
      1

      2

       
       
    • By Robin S
      Breadcrumb Dropdowns
      Adds dropdown menus of page edit links to the breadcrumbs in Page Edit.

      Installation
      Install the Breadcrumb Dropdowns module. The module requires ProcessWire >= v3.0.83 and AdminThemeUikit.
      There is a checkbox option in the module config that determines if the breadcrumb dropdowns will include pages that the user does not have permission to edit.
      Features/details
      The module adds an additional breadcrumb item at the end for the currently edited page. That's because I think it's more intuitive for the dropdown under each breadcrumb item to show the item's sibling pages rather than the item's child pages. In the dropdown menus the current page and the current page's parents are highlighted in a crimson colour to make it easier to quickly locate them in case you want to edit the next or previous sibling page. Unpublished and hidden pages are indicated in the dropdowns with similar styling to that used in Page List. If the option to include uneditable pages is selected then those pages are indicated by italics with a reduced text opacity and the "not-allowed" cursor is shown on hover. There is a limit of 25 pages per dropdown for performance reasons and to avoid the dropdown becoming unwieldy. If the current user is allowed to add new pages under the parent page an "Add New" link is shown at the bottom of the breadcrumb dropdown. If the currently edited page has children or the user may add children, a caret at the end of the breadcrumbs reveals a dropdown of up to the first 25 children and/or an "Add New" link. Overriding the listed siblings for a page
      If you want to override the siblings that are listed in the dropdowns you can hook the BreadcrumbDropdowns::getSiblingsmethod and change the returned PageArray. For most use cases this won't be necessary.
      Incompatibilities
      This module replaces the AdminThemeUikit::renderBreadcrumbs method so will potentially be incompatible with other modules that hook the same method.
       
      https://modules.processwire.com/modules/breadcrumb-dropdowns/
      https://github.com/Toutouwai/BreadcrumbDropdowns
    • By bernhard
      Some of you might have followed the development of this module here: https://processwire.com/talk/topic/15524-previewdiscussion-rockdatatables/ . It is the successor of "RockDataTables" and requires RockFinder to get the data for the grid easily and efficiently. It uses the open source part of agGrid for grid rendering.
       
      WHY?
      ProcessWire is awesome for creating all kinds of custom backend applications, but where it is not so awesome in my opinion is when it comes to listing this data. Of course we have the built in page lister and we have ListerPro, but none of that solutions is capable of properly displaying large amounts of data, for example lists of revenues, aggregations, quick and easy sorts by the user, instant filter and those kind of features. RockGrid to the rescue 😉 
       
      Features/Highlights:
      100k+ rows Instant (client side) filter, search, sort (different sort based on data type, eg "lower/greater than" for numbers, "contains" for strings) extendable via plugins (available plugins at the moment: fullscreen, csv export, reload, batch-processing of data, column sum/statistics, row selection) all the agGrid features (cell renderers, cell styling, pagination, column grouping etc) vanilla javascript, backend and frontend support (though not all plugins are working on the frontend yet and I don't plan to support it as long as I don't need it myself)  
      Limitations:
      While there is an option to retrieve data via AJAX the actual processing of the grid (displaying, filtering, sorting) is done on the client side, meaning that you can get into troubles when handling really large datasets of several thousands of rows. agGrid should be one of the most performant grid options in the world (see the official example page with a 100k row example) and does a lot to prevent problems (such as virtual row rendering), but you should always have this limitation in mind as this is a major difference to the available lister options that do not have this limitation.
      Currently it only supports AdminThemeUikit and I don't plan to support any other admin theme.
       
      Download: https://gitlab.com/baumrock/FieldtypeRockGrid
      Installation: https://gitlab.com/baumrock/RockGrid/wikis/Installation
      Quikckstart: https://gitlab.com/baumrock/RockGrid/wikis/quickstart
      Further instructions: https://gitlab.com/baumrock/RockGrid/wikis/quickstart#further-instructions
      Changelog: https://gitlab.com/baumrock/FieldtypeRockGrid/raw/master/changelog.md
       
      Module status: alpha, License: MIT
      Note that every installation and uninstallation sends an anonymous google analytics event to my google analytics account. If you don't want that feel free to remove the appropriate lines of code before installation/uninstallation.
       
      Contribute:
      You can contribute to the development of this and other modules or just say thank you by
      testing, reporting issues and making PRs at gitlab liking this post buying me a drink: paypal.me/baumrock/5 liking my facebook page: facebook.com/baumrock hiring me for pw work: baumrock.com  
      Support: Please note that this module might not be as easy and plug&play as many other modules. It needs a good understanding of agGrid (and JavaScript in general) and it likely needs some looks into the code to get all the options. Please understand that I can not provide free support for every request here in the forum. I try to answer all questions that might also help others or that might improve the module but for individual requests I offer paid support for 60€ per hour (excl vat).
       
      Use Cases / Examples:
      Colored grid cells, Icons, Links etc. The Grid also has a "batcher" feature built in that helps communicating with the server via AJAX and managing resource intensive tasks in batches:

      Filters, PW panel links and instant reload on panel close:

      You can combine the grid with a chart library like I did with the (outdated) RockDataTables module:

    • By Ken Muldrew
      I'm trying to get a short routine to run once per day that will look at some pages and send a reminder email when that customer's subscription (yearly) is about to expire. When I run the code in a template then it works without issue, but inside my lazycron service routine, I get an "Error: Uncaught Error: Call to a member function get() on null" as if the database cannot be found. My autoload module is just the sample HelloWorld module included with ProcessWire, editted to perform this task. The whole of it is included below (I've stripped out the code that generates the email because it never gets past $pages->find):
       
      <?php namespace ProcessWire;
      /**
       * ProcessWire 'LazyCronLoad'  module
       *
       */
      class LazyCronLoad extends WireData implements Module {
          public static function getModuleInfo() {
              return array(
                  'title' => 'LazyCronLoad', 
                  'version' => 1, 
                  'summary' => 'Just loads a lazy cron callback.',
                  'singular' => true, 
                  'autoload' => true, 
                  );
          }
          public function init() {
              // initialize the hook in the AutoLoad module
              $this->addHook('LazyCron::everyDay', $this, 'myHook');
              
          }
          public function myHook(HookEvent $e) {
              // called once per day
              wire('log')->save('user_activities',' lazy cron service routine');
                  $transport_pages = $pages->find("template=aggregate-entry, aggregate_type.title='Transport'");
                  foreach ($transport_pages as $page) {
                      if (($page->purchase_date + 30325800 < time()) && ($page->purchase_date + 30412600 > time())) { // between 351 and 352 days
                          wire('log')->save('user_activities', $page->id . ' email reminder sent');
                          // send email
                  }
              }
          }        
          
      }
      The first wire('log') shows up but the second one doesn't (the purchase_date condition is met (as demonstrated by running the code in a template close in time to when the lazycron routine executes)). The error log gives the Uncaught Error shown above. 
      I think this is a beginner's mistake with something obvious being missed and would be grateful for any assistance in fixing it.