adrian

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.

Thanks for testing @bernhard - I'll see if I can duplicate the issues you are seeing with layout - it seems fine here, but I'll test some more and see if I can try on a Windows machine. I agree that I would mostly choose a real terminal over this, but if I don't know the credentials for the server (or I am away from my computer), this is a pretty good backup, which is the way I view this feature. Regarding security - I thought through this already and here's my reasons why it's not an issue: 1) The file is not available outside the process module - PW's htaccess restrictions ensure that. 2) The process module requires superuser permission. 3) It's no more dangerous than the Console panel or Hanna code - both let you run shell_exec commands on the server anyway. This just provides a nicer interface and returns the output for you. That said, if anyone can think of a security concern that I have overlooked, please let me know.

I had @tpr take a quick look and it sounded like it worked, but I don't think he tested thoroughly. Maybe @bernhard would be willing to have a look as well. I know it works well on Mac and Linux.

Hi everyone. Lots of new stuff this morning. 1) Terminal panel (available in a panel and also as a dedicated Process module - similar to how the Adminer feature is set up) NOTE: It does not support interactive commands like vi, nano, apt, etc. DO NOT attempt to use these as they may result in you needing to restart apache. This is a bash terminal that lets you quickly execute commands on a server. In addition to normal commands like: ls, cd, cat, mkdir, rm, chmod, chown, etc, you can also do mysql command line calls which is very handy if you need to add a new user, create a mysqldump etc. Note that for mysql commands you need to issue them individually - you can't simply start "mysql" and issue commands from there - each call needs to include your username and password and the command to be run, eg: mysql -u root -p mypassword -e "CREATE DATABASE newtablename"; There is also an upload and download command, eg "upload test.txt" which will spawn a file selector dialog on your machine to upload that file to your server with the given name. It also has arrow up and down for command history as well as tab autocompletion of commands and file names. 2) Lots of new filterbox implementations @tpr has again put in lots of work to implement filterbox on the APIExplorer, Captain Hook, and PHPInfo panels - these will be super helpful to search through these complex panels. I have also added a ALT+F shortcut to get your cursor into the Find input for all these panels. Let us know how these new features work out for you. Cheers!

Not sure - I fixed so many bugs I can't recall anymore ? Maybe have a read through my Github commits - it might note this, not sure.

Are you using my fork: https://github.com/adrianbj/MarkupSEO/commits/various-fixes-enhancements or the main repo?

Perhaps I was too hasty in removing the live option, so maybe it will make a comeback now that LAZY is the default - just need some more testing to see if it actually helps with large dumps, and whether there are issues with the integrity of the data. So far from what I can tell, LAZY does an awesome job even with: bd($page, array('maxDepth' => 99)); or the shortcut: bd($page, [99]);

Thanks for spotting the left over LIVE reference. Actually between 2.6 dev and the releases version of 2.6 of the Tracy core, they actually changed LIVE to LAZY. LIVE still exists as a separate option but it still has some downsides. In most cases LAZY is better. You can read more about it here: https://github.com/nette/tracy/issues/344#issuecomment-468123490 Your data is still truncated because of the default maxDepth of 3 which is tweakable in the module settings. With lazy it's possible to have a much greater depth without performance issues so maybe I will up that at some point. You can of course still use db() or bdb() or bd($var, [10]) or one of the other combinations to up the depth. You'll find that with the new LAZY approach you can actually do a bd($page, [10]) and it won't cause an out of memory error like it would with Tracy 2.5. Hope that helps. If you have any more technical questions let me know, or perhaps address them to @dg at Nette.

@Pete - maybe you have already noticed this, but https://processwire.com/talk/discover/unread/ has black rather thank pink links.

Looking at one of my Process Modules, I use: 'page' => array( 'name' => 'admin-actions', 'parent' => 'setup', 'title' => 'Admin Actions' ), The parent has no slashes and will be relative to admin.

Your link to Cerberus is incorrect: https://tedgoas.github.io/Ce vs https://tedgoas.github.io/Cerberus/

They're not actually uninstalled - just do a Modules > Refresh and you'll be back in business with all modules settings as they were.

I assume you have uninstalled and reinstalled your module? This is needed to create the admin pages. Sorry if this is obvious and you've already done it.