adrian

Beautifully done - @ryan needs to see this

Sorry @Juergen - it looks like that function doesn't exist in all environments - Windows perhaps? The latest version checks if it exists before trying to use it. There was also a problem with the checkbox not actually disabling this panel which is also fixed now. Can you please confirm that this fixes it for you, both checked and unchecked? Thanks!

PHP 7.1 is returning a: A non well formed numeric value encountered on line 713 notice because you are relying on PHP's auto int casting. I didn't do a thorough check to see if this is ok, but so far it's working for me: $_timestamp = ((int)$_timestamp + $file['last_modified']);

Very nice!

I am sure there are some good ideas in there @szabesz - I don't want to get too carried away, because a lot of that info is available from the PHPInfo panel, but I am certainly open to requests for things to add. I did just update it with Apache version because this may be relevant when debugging htaccess issues.

It has always been good practice to note any 3rd party modules that you are using when posting an issue/bug report for the PW core, but after seeing @ryan's recent note about issues: https://github.com/processwire/processwire/issues/8 - "Indicate any 3rd party modules that are installed.", I thought it might be helpful to make it easy to get a formatted list of installed modules that you can simply copy/paste into your issue report. The latest version of Tracy includes an update to the ProcessWire Info panel that provides a new "Versions List" section that lists all modules and their version numbers in a textarea to make it easy to copy/paste. It also shows the PW, PHP, and MySQL versions. For those of you updating from an existing version of Tracy, you'll need to check this new panel section in the module config settings:

Thanks for this @valan - any chance you could submit this as an Issue or PR to Github?

I know, I and sometimes I do that when a file is really deeply nested and I already have it open in Forklift (plug for the best Mac file manager), but usually I don't really find it much quicker than browsing from PW.

Honestly, I almost never use drag and drop - I am a big fan of maximizing windows (maybe I am just bad at multtasking) so it's not really that easy to drag 'n drop. Maybe if I had a dual monitor setup (which I have sort of had in the past), or a 30+ inch screen it would be different.

Try: new \DateTime($enddate);

You can even just do $pages->find ..... when bootstrapping in PW 3

The changes I made will only affect the console - it's just a matter of whether the encoding change breaks anything else. I checked the pageNameUTF8 sanitizer (because it was the issue that you had with that which resulted in the change that deleted "+" signs) and that still works great, so hopefully we are good

Ok, bit of a rushed fix, but hopefully I haven't broken anything else regarding console encoding. Please let me know how you go with the latest version.

I found it - the "++" is being lost, so it's processing: echo $i ; hence the continuous loop! Must be some encoding issue. I was url encoding, but I stopped doing that to fix another issue. I will revisit and see what I can do to fix. Thanks for reporting.

Not sure yet, but note that it works fine in the Template Editor - just use the Test button / CTRL+Enter. Let me see if I can see out why the console is misbehaving with that. The console is ajax driven, whereas the template editor/tester isn't.

You might be able to do a: bd($this->path); before that line (if you have Tracy installed). Depending on when the CacheFile.php is loaded, this may or may not work. Turning on Tracy's Dump Recorder and Preserve Dumps option may also help. Alternatively you could do: wire('log')->save('testing', $this->path); and then check the value recorded in the 'testing' log file.

Do you think that log entry is related? Have you checked the value of $this->path when this is called (line 208 of CacheFile.php)? $dir = new DirectoryIterator($this->path);

Awesome! It also seems like the w3.org version that we're now using is significantly faster - I was typically getting 750 to 1000ms times on the validator.nu service - now it's around 500ms.

Honestly it looks like you module might be more complete - you are using a js code editor which would make for a much nicer editing experience and it looks like your use of php file tree also makes for a better interface. I don't think this should be hidden at all - I think I'd rather see it in the modules directory as well as Nico's, rather than being lost.

Hi @Juergen - please try the latest commit - I switched it from using validator.nu to validator.w3.org/nu/ and it seems to be fine now. They both use the same checker so hopefully everything will be fine. I have a feeling that this might be a bit of a moving target though, so if anyone ever comes across issues with it, let me know and I'll try to get it working again.

Does this only happen with this template? Does it happen with ML support disabled? Any third party modules that might be affecting the page name/title?

We have a team of keeners - I think that you @szabesz are definitely one of us now too

I am not saying that at all. Nico is working at an agency these days that is mostly using MeteorJS, so I don't think he has much time to maintain his modules. I just thought it might be worth contacting him and seeing if perhaps you could take over his module, or let us know what advantages yours has over his. We're just all keen on limiting the number of module duplicates that WP suffers with - certainly not trying to diminish your efforts at all - sorry if it came across that way. I wasn't even sure if you knew about his module so it was also a bit of a heads up in that regard. Keep up the great work!

No problem at all - we all received lots of thoughtful advice when we started with PW and as you have seen we try hard to return that favor. It's always great to see new users and to see them start to contribute when they feel able!

Hi @flyrs88 - welcome to PW and the forums! What you are looking for is: "include=hidden" You can also use "include=all" to find hidden and unpublished pages. Enjoy your PW journey!