adrian

Hey Kongondo, Thanks for this - using it for the first time - very handy! Just a couple of warnings that I noticed appear in the admin until you have entered data: I also noticed that sometimes the co-ordinates weren't being populated properly - just showing "Infinity". I had to save the page again, then the next time I moved the markers, they worked correctly. I don't unfortunately have a reliable way to reproduce, but just wanted to let you know in case you can easily track it down.

I guess I have always been hesitant to put anything into the modules directory that is put together this quickly / still in alpha / or has limited use. That said, I do agree it can be hard to find these - some of which can still be very useful. I feel like it would be more appealing if the modules directory had a pre-alpha tag, or some other way to indicate that a module is not of a certain quality. The other problem with being the directory is that it will get picked up my the Upgrades module and if substantial upgrades are made, a module may have the potential to break someone's site. This is something I would consider very carefully with an officially released module, whereas posting one like this, I feel like this is less of a concern because I can notify users more easily in the thread and they need to manually update. I think the modules directory (and the upgrades module) really needs the ability to specify a "breaking changes" warning, along with the ability to display a list of the commit notes from the currently installed version to the latest available one. Do you have any thoughts on this idea?

Following up on the idea of some tool to do this, take a look at the module attached to this post: https://processwire.com/talk/topic/8406-set-multiple-templates-role-access/?p=81711 It will let you add selected fields to selected templates.

I think there is still an outstanding bug (https://github.com/ryancramerdesign/ProcessWire/issues/1803) with images on user pages - it seems like outputformatting is always off which results in the need for first(), even when maxFiles is set to 1. Try this: $user_image->first()->url

Thanks - I have made those changes. I also upped the size of the icons a couple of pixels which should also help a little. I played around with adding a legend to the panel, but it just kind of looked messy and took up too much extra space, so I just added tooltips to the icons - hopefully this helps a little.

Happy to help make this easier to see, but firstly I am wondering if what you are seeing on your setup matches the screenshot above, or if it's different - perhaps there is some CSS at play again that is altering them? If they are the same, perhaps you wouldn't mind playing with them till you're happy with how they look - would save us potentially going back and forward over several different versions. They are both SVG (https://github.com/adrianbj/TracyDebugger/blob/master/PanelSelectorPanel.inc#L124), so it will be easy for you to change the size and color. Thanks for the link - I hadn't seen that - looks pretty cool actually - I'll definitely give it a go.

Try Soma's suggestion about using Pages::trashed https://processwire.com/talk/topic/5918-function-getting-run-twice/

Sorry if that came across the wrong way - I am just always in awe of how great you guys are at being multilingual. It was meant to be a compliment! I know a little travel Spanish and it seems so hard to get beyond that. I also remember a teenage German asking me questions about English grammar and I didn't know the answer - I think unfortunately those of us who are from English speaking countries typically don't get the same grounding in languages and their rules - we just know what sounds right without knowing why. That's why in some ways you probably do have a better grasp of English and how it works. And it's such a bastard language with all these weird exceptions to rules - I don't know how anyone ever learns it!

You Europeans make me smile - your English is probably better than mine Latest version comes with a few general tweaks/fixes, but the most significant are related to the Selector panel based on our recent discussions. It now returns to the "Sticky" state when you reload after a "Once" change (previously, it returned to default from the config settings). There are also now icons indicating if: the panel is set in the default list in the module config settings ("Tick" icon), the state of the panel is different for the current view, ie you have made a "Once" change (number "1" icon) In the following example, you can see that: Debug Mode is disabled. Default is enabled (checkbox icon). There is no "1" icon so it is a Sticky setting. ProcesswireInfo is disabled. Default is enabled (checkbox icon), There is a "1" icon so you know it's a "Once" only setting. Validator is enabled. Default is disabled (no checkbox icon). There is a "1" icon so you know it's a "Once" only setting. Hope that all makes sense and provides a quick visual of what the current panel settings are and what they will be when the page is reloaded.

Sorry - poor wording on my part - I am talking about enabling an extra panel (or disabling one) using the "Once" option - hopefully that sentence makes more sense like that

I think I mostly agree with you here - the downside to the current option is that requires a page reload (when you click Once or Sticky) to load the Validator panel. An AJAX option would be much quicker - you could have the panel always loaded with no content and a button to trigger the validation request. I am not really sure how much this really matters though - if you decide to do a "Once" validation and you see errors, you'll probably then "Sticky" it until you have things fixed, then "Reset". I think in the end I probably agree with you and won't worry about changing things at the moment This sounds useful - I am thinking just one icon positioned after each of the default panels so you know what is the set that is defined in the main module config settings. I would actually like your thoughts on the current behaviour regarding making some "Sticky" changes and then adding an additional panel "Once" - currently any time you do a "Once" it clears the previous "Sticky" options which I don't think it very helpful or expected. I think I will change this so that on the next reload, the states is restored to the last sticky state, rather than the default state - sound ok?

No problem - thanks for clarifying and for helping to sort this out. Latest version includes that style. Let me know if there are still any problems.

Do you mean so that loads in the background so that it doesn't slow the rendering of the page itself? If so, then that sounds like a good idea. Interestingly, as I am testing the generation speed of various panels on different servers, I am seeing that almost all panels are very fast on a decent server - it seems like it is mostly my aging Macbook dev setup that is struggling - maybe I don't need to worry as much as I thought. What are you guys seeing? Thanks for looking into this - I am happy to add those styles to Tracy, but I am not sure from your message whether or not you still need those with the version I posted that includes the all: initial - can you please confirm that your code is still needed and still works on the latest version. Thanks for the kudos - glad you are loving it

New version: New config setting for the number of entries to show in log viewer panels (now defaults to 10 rather than 25 to speed things up a little). You might even want to change this to 5. The PW logs panel isn't too bad, but currently the Tracy logs panel is definitely a little slow - I will also be looking into speeding this up. Panel generation time is now listed at the bottom of each panel which should help you to decide which ones to not show by default. Unfortunately the PW Info panel is one of the slower ones at the moment, so I will tackle trying to speed that one up first. Not surprisingly, the Diagnostics and Validator panels are also relatively slow, so depending on the speed of your server, it might pay to have those off by default. Let me know if any of you notice any panels that are particularly slow on your systems.

Well CSS is not my strongest skill, but I think this is generally tricky. There is: all: initial which has pretty good support these days, but I am still having some troubles getting initial values for everything. I have made some changes that may help you, including using proper <label> tags for the checkboxes. On an unrelated note, there is now also a toggle all checkbox for even quicker modification of panel selection. Please let me know if any of my changes helped and if not, it would be great if you could spend a little time figuring out what rules are conflicting - thanks!

Thanks for the feedback on this - I'd love to know which two panels sped things up the most - maybe I can optimize them. Thanks for reporting - I'll look into it although I am curious what styles you have that are moving the checkboxes over the labels.

https://processwire.com/blog/posts/processwire-3.0-alpha-2-and-2.6.22-rc1/#new-module-file-compiler-tags

Sorry - another minor improvement. You now have "Once" vs "Sticky" options. "Sticky" behaves like the previous version - the selected panels will remain until you reset or close the browser. The new "Once" option will only change the panels for the one reload that happens when you click the button. This should make it even easier to quickly view a panel you rarely need like PHP Info for example.

Latest version adds a "Panel Selector" panel to the debugger bar. I added this because I noticed that the overhead of having all panels loaded all the time can sometimes be a few seconds depending on the server. With this new feature you can pare down the main "Show Panels" module config setting to just the ones you want all the time and then use this new panel to quickly and easily enable additional panels for a specific purpose without having to go to the module's settings and mess with the defaults. The changes to the list of panels is stored in a session cookie, so as soon as you close the browser (or you use the "Reset Default" option), you'll return to your default set of panels. Hopefully you'll find this speeds things up for you. On this note, if you are finding things slow you may want to consider the config setting for switching to the stable version of the Tracy core (this was mentioned several posts ago, but in case you missed it, it can make a huge difference. Hopefully the Tracy guys will come up with a solution (https://github.com/nette/tracy/issues/157) for the master/dev branch before it is marked stable). I am also going to do some code review on all the panels in an attempt to speed things up - I am sure there are some things I overlooked in initial development that can be dramatically improved. Let me know if anyone has any ideas though.

Check out this: https://processwire.com/docs/tutorials/troubleshooting-guide/page3 I am guessing it's a rewritebase issue

I really love the enhancements you show horst - showing the names and filtering will be very helpful. This can be done automatically via CustomUploadNames (http://modules.processwire.com/modules/process-custom-upload-names/), but I would also like to the option for manual renaming in the core.

A small, but hopefully useful timesaver - I have added a new method: TD::debugAll() debugAll() da() This will output the content via all dumping/logging methods: barDump(), dump(), fireLog(), log() This can come in handy when you want the expandable tree that you get with barDump, dump and fireLog, but also want to store in a log file for later comparisons. It can also be useful in AJAX calls or some other instance when you're not sure if barDump / dump will work or not, or if there is a page redirect which causes them to disappear from fireLog / dump Obviously this will be a little slower (depending on the complexity of what is being dumped), so maybe don't use it by default, but it's as another useful timesaving tool in your arsenal. Note - you'll need to enable the debugAll() and da() shortcuts in the config settings.

Hey Pete - be sure to post about this in the Tracy support thread so I can take a look. It works out of the box with the settings as they are. For more info though, be sure to check out the blog post: https://processwire.com/blog/posts/introducing-tracy-debugger/

I decided to go ahead and make the validator work with local dev sites as well (note the local ".dev" domain in the results). Also note that the validator is now using the html5.validator.nu version when it sees a HTML5 doctype declaration. Note the colored "cross" icon indicating some errors.

Apologies - you are correct - I don't think I ever realized PW did that. If you look at the database tables for a date field (without time) it is stored as Y-m-d, so I guess I assumed it would return just that. Note that it returns the timestamp for 12:00:00AM GMT that day. By contrast, a datetime field is stored as a timestamp so I would expect a timestamp to be returned as the unformatted value.