adrian

Thanks for the extra details @szabesz - unfortunately I still can't reproduce. Could you please try deleting your browser LocalStorage - maybe that is affecting the position under the scrollbar. Could you also send me your Tracy settings. You can use my ModuleSettingsImportExport module to make that easy. Regarding the SVG icon issue - does this occur both backend and frontend? Just wondering if maybe there is some frontend css (or custom backend css for that matter) that might be interfering.

What do you think about doing a mb_convert_encoding($str, "UTF-8", "Windows-1252"); before the json_encode. I guess we can't be certain it's Windows-1252 but it seems most likely and would maybe be a cleaner solution? Actually is it more likely 1252 or 1250 - most of my quick reading seems to refer to 1252.

@tpr - while we're at it, I am been having issues with page scrolling - when there are lots of fields or templates such that the dropdown menu extends beyond the viewport height, AOS prevents me from scrolling the page to access those items towards the bottom of the list. It is due to the UiKit sticky header setting.

@MilenKo - I have been seeing this since December: https://processwire.com/talk/topic/13389-adminonsteroids/?do=findComment&comment=177670

@matjazp - thanks for helping to figure that out. I think this error was introduced when I added caching to the two logs panels - wireCache json encodes content for storing. Do you think the fix you provided for the Terminal panel for converting unknown characters to "?" would also work in this case? Obviously the mysql error change would also work, but I don't want everyone to have to do that. @szabesz - I haven't seen any of these issues. Is it browser specific, or any chance the scrollbar issue could be related to this: https://processwire.com/talk/topic/13389-adminonsteroids/?do=findComment&comment=179123 or something else in AOS?

Thanks @Robin S - that's a really handy addition for my needs - hopefully others will enjoy also!

Putting this in your ready.php or admin.php should do it. You may want to add additional checks for admin only (not via API). $this->addHookAfter('Pages::added', function($event) { $p = $event->arguments[0]; $p->removeStatus('unpublished'); $p->save(); }); But, @Autofahrn has some excellent points about publishing a page which doesn't have any content other than the title, so use this with caution!

@Robin S - would you be willing to add support for User pages (ProcessUser) as well please?

@nbcommunication - just wanted to say a big thanks for this new version - what are your plans to get this into the modules directory?

Hey @bernhard - no rush, but @matjazp took care of some Windows / UTF8 issues which I have committed. I still can't replicate your layout problems, but when you get a minute it would be great if you could help to narrow down what might be causing the issues at your end. Thanks! Also, did my explanation help to alleviate your security concerns? If not, let me know what still concerns you and I'll address it.

Just in case it's helpful, this is what I do for Tracy - anything that is defined in the $config->tracy() array overwrites the settings stored in the DB. https://github.com/adrianbj/TracyDebugger/blob/3f1fb2cf0016b8b27cc1019f47e58bce8e2cbd3d/TracyDebugger.module.php#L322-L325

Ok, change is committed - @jmartsch let us know how it goes for you also please.

That seems to work well for me also. Are you happy for me to commit that change to Tracy yet, or do you want to wait?

Yeah, I think that was an accident by @bbeer

@jmartsch - I am going to leave this to @tpr, but this is interesting:

If you want proper 503 maintenance mode headers sent, then use: http://modules.processwire.com/modules/protected-mode/

@jmartsch - @tpr has just added support for the UserSwitcher panel to filterbox and made lots of other improvements. We all owe him a huge debt of gratitude for his work on this lately - maybe even send him a donation for his hard work on this: https://www.paypal.me/rolandtothpal/5 - it's such a huge improvement especially for the API Explorer and Captain Hook panels! Let us know how you find it with your 800 users - hopefully this will work well and there won't be a need for an ajax approach to loading users just yet, although if I do that, I think I'll probably just code something up myself - no real need for a library for this.

That's a lot of users to want to switch to. On sites that have large numbers of users I usually exclude that role, or if I need to be able to test someone with the same permissions, I create another role (with same permissions) and assign that to one test user. Sounds like that won't be useful in your case though. I am curious - that's a lot of <option> entries for that <select> field. Is it fairly performant? I worry about when you have 10K or 100K users though. @tpr and I have been looking into adding filterbox to this and it will probably work, but I do wonder whether some sort of autocomplete option would be better. @tpr suggested Select2 - they support ajax loading, so that might work. There is of course also selectize, but both of these require jQuery so I think I would probable just end up homebrewing something for this. I think I would automatically switch the input based on the number of available users. Any thoughts?

In your custom find, choose Custom (field=value) and enter check_access=0 in the far right column.

Is this a built-in FB option, or do I need to base its loading on countTotal(), or perhaps even conditionally load the filterbox files based on a PHP count of items?

I expect it would work ok, but I am wondering if you actually have that many users you need to switch to. Have you considered making use of the Restricted Roles option in the User Switcher settings? If that doesn't suit your needs and filterbox really is needed, let me know and I'll take a look at implementing it.

Can you explain this a little more please. I just tested on a Windows machine (although pointed to a linux server), but I can't see any issues. Could you maybe put together a screencast for me demonstrating the issue? Thanks!

@tpr has yet again put in lots of time to improve the filtering for the APIExplorer and Captain Hook panels:

The modules directory is still pointing to the original. I actually thought that the original didn't work at all with recent version of PW. This is an area that I think PW really needs to work on - there are several forks which are critical updates, but are not really linked to anywhere official.

@tires - I like the new look! Just in case you missed it, are you using @teppo's fork: https://github.com/teppokoivula/AdminBar which fixes a couple of critical bugs in the original.