adrian

No problem at all - sorry it's causing you problems The line you point to is to clean up the returned results for display - the results start with <ol> for both the standard and html5 validators so I am not sure why, but I have committed a new version which has a much cleaner approach to extracting the contents of the <ol> - hopefully this will mean that $this->result won't end up blank for you, which is what must be happening to cause that error which is triggered here: https://github.com/adrianbj/TracyDebugger/blob/master/ValidatorPanel.inc#L510 Please let me know if the new version helps.

I have had similar issues as well Steve, just last week actually - it's not just your Cloudfront node

@tpr - do you have apache authorization required for the website? I am trying to figure out that authorization error and that seems like the likely culprit. EDIT: http://www.hashbangcode.com/blog/using-authentication-and-filegetcontents - seems to be the cause, but maybe it's something else unrelated!

Sorry about that Charles - I reverted a commit from last night that turned out to be a bit buggy, but I forgot to revert the version number in the modules directory. I have just recommitted a fixed version with that new version number, so hopefully your update should now work. The new version uses a <select> for choosing from available alternate template files. I think this makes it easier. It now also remembers different dev versions for different templates. Obviously you need to create the file in the templates directory first before it will be available from the select dropdown. You can now also reset just this template, or all templates on the site. @tpr - thanks for those great mockups - I haven't had time to incorporate your ideas yet, but will do hopefully shortly. The error you are getting is specifically with the validation panel - I am not completely sure why file_get_contents is giving that authorization required error. I am using wireHttp first and falling back to file_get_contents. I will look into this soon also, but in the meantime, disabling the Validator will gets things going for you. The latest version also includes some core Tracy updates which introduced lazy rendering of panel contents - this should speed up initial rendering of the debugger bar significantly.

That makes such a huge difference - I have a query (that I was obviously caching) which was taking around 4-5 minutes, that now happens in 45seconds! Obviously I still need to optimize some other components, but this is a huge improvement - thanks to everyone involved in this!

Hey @tpr - thanks for your thoughts on this. Perhaps the styling of those buttons could be improved to make it more obvious what is selected. In the PanelSelector Panel I add an icon next to each panel to indicate it is is loaded "Once" which I think works, but perhaps it could be improved by having a selected/pushed state added to it. Anyone else have any thoughts on this? A design mockup sounds like it could be helpful, but please don't go to too much trouble - I think I understand what you are wanting.

Definitely weird - if $i->filename is definitely returning the full server path to the file, and PHP's filesize() isn't working on it, then I am baffled Apparently some hosts disable filesize(), but you mention that it works on the frontend, so that would rule out that possibility.

Another really cool (at least I think so ) panel. Template Path allows you to temporarily change the template file of the page. By default, it adds "-dev" suffix to the filename, eg. home-dev.php, but you can change this on-the-fly to whatever suffix you want, allowing you to easily test different versions. Like the selector panel, you can make the change "Once", or "Sticky" for the session. Sticking with the "alert" approach to icon colors, if the template icon is green, then it is loading the default template file. If it is red, then it is loading your temporary template file. Hopefully you'll all find this very useful when debugging live sites - no excuses now to ever make changes to a live file without testing first Please let me know if you have any suggestions for enhancing this feature - we all work differently, so there might be some cool approach that I could support that I haven't yet thought of.

Out of curiosity, does this work: filesize($file->filename); Hang on a second - you say that: $file->title works - but this is not properties of files What exactly is $file referencing?

I can see those tools putting the Mom and Pop Wordpress "developers" out of business, but as far as I know they have a very long way to go before they can build a complex interactive data driven website.

Does that fulfill your needs: http://modules.processwire.com/modules/media-library/ Or if you need more functionality: https://processwireshop.pw/plugins/media-manager/

Hi Steve - sorry you had to waste a couple of hours troubleshooting that, but thanks for the detailed analysis of the problem and the solution. The latest version should take care of it - please let me know if there are any continued problems. Thanks again!

Did you remember to get the id of the user whose name is matt and use that in the selector? You could do: $lostproperty = $pages->find("created_users_id=".$users->get("matt")->id.", template=lost-property"); Otherwise, make sure your template is correct. Also, to avoid confusion, I would go with $item instead of $items

Try: created_users_id= as the selector, rather than user.

http://modules.processwire.com/modules/jquery-file-upload/ https://github.com/adrianbj/FieldtypeVideo

Just add: protected static $fM; at line #19 You'll also need to change line 94 from: self::$fM['type']($f, $fM['label'], $data[$f], $fM['desc']) to: self::{$fM['type']}($f, $fM['label'], $data[$f], $fM['desc'])

I know this is very old, but I just stumbled across it - don't forget that AdminRestrictBranch (http://modules.processwire.com/modules/admin-restrict-branch/) will take care of #2 and #3

@rick900 - welcome to the PW forums. Any chance you could provide some code to show how to integrate payolee within ProcessWire.

Typically the easiest way to avoid loops with save hooks is to just save the field, rather than the whole page. So, do: $pageToSave->save('relatedPageField'); // or whatever the name of the field is

I have just added a new config setting: Local Root Path which you can use to modify the editor links from a production server to a your local dev files - I think this is a really handy improvement. If you have the remote server mapped as a local drive, you could even point to that if you'd prefer. It also includes a bunch of Tracy core updates, including support for AJAX errors on the bluescreen, but you guys can read more about the changes here (https://github.com/nette/tracy/commits/master) if you want.

Thanks for all the testing! Just to let everyone else know - Charles has tested the latest version (just committed) and it is working properly with PHP 7. Glad you sorted out the cron issues!

Have a read about the PHP modulus operator - that should get you started.

Thanks Charles, Please try the latest version. I don't have currently have a PHP 7 setup to test so there might be additional errors, but that one should be fixed.

Hi @dab, Glad you're finding it useful. I haven't used the module on a shared host with cpanel, so I am not sure whether there is maybe some interaction going on there. I don't think I have ever seen the module itself create these files. Obviously the module responds to: http://pw.dev/?hash=4ba942b72726bbc0fa527c0c3aa69f2bc6817534 but I don't know where that index.html version is coming from. Any chance there is a caching mechanism at play here. Maybe even ProCache? although I doubt it.

Unless I am missing something obvious, it should just be a matter of enabling url segments on your home template, then using the value of the segment to get the page details for that user name. https://processwire.com/docs/tutorials/how-to-use-url-segments/