adrian

Done!

Yeah, let's do it - I'll look into it more later. For now, here is what the latest info looks like when pasted into Github: Thanks again @horst and @szabesz for your feedback and suggestions.

Sorry I missed the bit about whether it can be increased - as far as I know, that's just a matter of checking for safe mode? Do you know if there is anything else to consider? This sounds interesting, but I think it sounds like a dedicated image panel, rather than info to be included in this "Version List" (outdated name now) section. Is that what you are thinking also?

Thanks @horst - great ideas! I'll add all those xdebug, GD and Imagick metrics. As for MySQL version - I am already capturing that in the Server Details section (along with PW, PHP, and Apache versions). Does that cover your needs, or are you thinking of something else?

I am tempted to add a few key PHP settings in another sub-section of this list - I think it could really help with quickly identifying some issues. What do you guys think of this list of metrics? mod_rewrite mod_security allow_url_fopen post_max_size upload_max_filesize max_input_time max_execution_time max_input_vars memory_limit Adding in @ryan and @horst to see if you guys have any other specific Apache/PHP settings that you think would be useful to include in Debug info. I think these (together with the pw/php/mysql/apache and module version details mentioned above should cover most common issues (including image uploading problems). Btw, if you're confused what I am talking about, scan a few posts up to see this new feature in Tracy for copying a Github-friendly formatted collpased/expandable list of debug info for inclusion in Github Issue reports.

Maybe your file compiler settings are not compiling included files:

Looks like you have a namespace issue. Have you tried clearing the FileCompiler cache? I don't think it should matter, but do you have the ProcessWire namespace added to your home template, but not others?

https://clipboardjs.com/ Of course I could have just put the markdown code in the textarea, but I wanted to keep that simply for viewing and copy/pasting into the forum (in a spoiler), etc.

Pretty stoked by this morning's update The Versions List now has a "Copy for Github" button, as well as a "Copy plain text" button. The Github button copies MarkDown code to your clipboard that results in this formatted output: Absolutely no excuses now for not including all your server and module info details in your Github Issue reports. Please let me know if anyone has any problems or suggestions for improvements / things to include.

I haven't used ServerPilot, but I have heard it's very helpful if you are new to server management. I know it works with Digital Ocean, but assume it can be setup on any Linux box. Perhaps you'd be better off with a fully managed server environment, rather than having to manage everything yourself. I am not the best person to answer this as I have always managed my own servers, but I am sure those with more experience in managed servers will chime in shortly.

Hi @MMG8 - welcome to the forums. I would agree that in general you are better off with a Linux server over Windows. As for the distribution, I have always gone with Debian, which in case you don't know is the basis of Ubuntu. I don't think it will really make that much difference to you, but Debian would be my recommendation. You may find some useful info in this article: http://inthebox.webmin.com/choosing-a-linux-distribution-for-web-server which compares Debian, Ubuntu, and CentOS.

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.