Jump to content
Soma

Admin Hot Keys

Recommended Posts

ProcessWire2.+ Admin Hot Keys 0.0.7

This modules adds hot keys functionality to PW backend. The keys can be configured in the module settings in the admin.

I created a repo here for download and if anyone interested in picking it up.

https://github.com/s...ic/AdminHotKeys

Currently it supports

  • Save : ctrl+s
  • Add New : ctrl+n
  • View Page : ctrl+v
  • Open Pages search : alt+q (search field can be configured)
  • Open Templates search : ctrl+shift+t
  • Open Fields search : ctrl+shift+f
  • Goto Pages : ctrl+shift+p
  • Goto Setup : ctrl+shift+s
  • Goto Modules : ctrl+shift+m
  • Goto Access : ctrl+shift+a

Note: If you're inside a text input it will ignore the hot keys, as to avoid problems with already defined key.

Tip: If you open up templates or fields autocomplete search `ctrl+shift+f|t` press `shift+tab` to focus on the link in the label previous to the search input box. Now hit enter to get right to the template or field screen. (If using FF make sure to enable tab focus for all elements in MacOSX: http://support.mozil...enus or buttons)

  • Like 14

Share this post


Link to post
Share on other sites

Your welcome. Thanks.

Little update after playing around a little.

  • changed to use save hot key for all edit screens to save not only page.
  • added "Add new" hot key support for Template, Fields, Users, anything that has a "Add new" button.

Have fun.

  • Like 1

Share this post


Link to post
Share on other sites

Hi Philipp,

Chrome on OS X likes it but I get some strange things happening in Firefox (13). I can't collapse any fields or use the PageListSelect.

Regards

Marty

Share this post


Link to post
Share on other sites

Thanks Marty, just commited an update that should fix it for FF.

Share this post


Link to post
Share on other sites

Added several new actions.

Added shortcuts to admin main pages.

The most fun is to open a autcomplete search to find and edit templates or fields. Now you can wherever you are press "ctrl+shift+t" or "ctrl+shift+f" and get something like this:

post-100-0-78689000-1342606119_thumb.png

Once open you can type and select, hit enter and directly go to edit screen.

Enter a char and hit backspace to show all.

Have fun.

Share this post


Link to post
Share on other sites

Wow, this is a nice little helper. Great work!

One suggestion. Is it possible to go to the templates / field main page if I just press enter in the empty modal? This way we dont't need a additonal shortcut for these pages.

  • Like 1

Share this post


Link to post
Share on other sites

Thanks all!

Little update for 0.0.6

- added View Page to the list "ctrl+v".

- Also, I was thinking about adding a shortcut to the Template and Field pages.

I figured simplest is to add a link in the label in front of the searchfield. If you open the dialog, you can now simply press "shift+tab" to focus on that link and hit enter.

Edit: lol, just figured that "shift+tab" doesn't seem to work in FF. Back to the drawingboard :D¨

Edit2: Ok this seem related to OS setting in MacOSX. If in FF make sure this in enabled http://support.mozil...enus or buttons

Share this post


Link to post
Share on other sites

I think this"little module" adds a way quicker workflow to ProcessWire, maybe it's a good thing to make it core module.

Share this post


Link to post
Share on other sites

Soma - CTRL+V is paste on a windows PC so not sure whether there are any issues there? Just a thought.

Share this post


Link to post
Share on other sites

Soma - CTRL+V is paste on a windows PC so not sure whether there are any issues there? Just a thought.

Yeah I know, you can change it in the settings. I also thought the same but couldn't decide what would be best.

Share this post


Link to post
Share on other sites

I don't know whether you could work around it by checking if an input field or textures is selected before deciding on the action? If a field is selected it would make sense to leave it as paste, else view page in a new window maybe.

Share this post


Link to post
Share on other sites

Thanks Pete. But that's not really a solution I like :D

Share this post


Link to post
Share on other sites

Ok lol funny, it seems the hotkey jquery plugin already is ignoring commands if inside text inputs! So this already is solved this way. I thought it would be unnecessary to implement and I'm not sure it really is the best solution, but will help avoid problems in first place (as it also stated in Resigs plugin) . It would be nice to not needing to leave input focus to be able to save or do other actions while typing. But guess not really an issue.

Share this post


Link to post
Share on other sites

Soma, you have swapped the labels of "Goto Setup" and "Goto Pages" in AdminHotkeys.module

Your module is now part of my default processwire setup. Really useful..

Share this post


Link to post
Share on other sites

Thanks, nice catch. It's corrected in the latest commit.

Share this post


Link to post
Share on other sites

Hello, just commited a new update.

  • Added new action to search for Pages using PW internal ajax search "alt+q". You can even select template to filter.
  • Added setting to change the fields used in page search. Default "title body". Search uses %= (SQL like)
  • Changed dialogs to position fixed so they appear right where you are and page doesn't jump
  • Added check so it doesn't get initialized on login screen

post-100-0-94410900-1342744540_thumb.png

post-100-0-59933800-1342744546_thumb.png

  • Like 1

Share this post


Link to post
Share on other sites

Great update Soma! I'm really liking the new ajax page search. Only thing I wanted to mention though was the default key assigned to this ALT+Q can't be assigned in OS X because it's the application Quit command. I did it, and it immediately quit the browser, closed all windows, etc. I changed it to CTRL+Q, which seems to work well, but am thinking you chose alt+q because ctrl+q has the same problem on windows? Maybe there is some other default for this that would be safe across platforms? Maybe something like CTRL+. or CTRL+[ or CTRL+-

I love everything about this module, except that I'm confused by the templates/fields search. Probably because I'm just accustomed to clicking, rather than typing template/field names in the admin. In most sites, the quantities here are small enough to make the search seem overkill. So if there were a most wished for feature on my part, it would be that either: 1) it showed a list of templates/fields rather than a search box. Or; 2) that the field/template search boxes showed all of the fields/templates (that you could click to edit) and then filtered (rather than created) in the list as you type.

  • Like 1

Share this post


Link to post
Share on other sites

Oddly in Windows it's Alt+F4 to quit an application, so Alt+Q probably starts your car by that logic ;)

Not saying Macs make any more sense mind, requiring a key with a fruit on when they ran out of letters and numbers that by all rights should produce an apple when pressed. :P

Share this post


Link to post
Share on other sites

Thanks Ryan for the suggestions. I'm not sure what u mean by this is quit application. On my mac command q is quit alt q is a special char. I sent you from my phone so keeping it short.

Share this post


Link to post
Share on other sites

I'm actually using a 1987 IBM Model-M keyboard with my Mac, so I have an ALT key rather than an Command (Apple) key. But unless I'm mistaken, ALT and Command (Apple) are just platform specific names for the same thing. Macs also have something called the Option key, which I don't think has an equivalent on the PC. In my case, I just have Option mapped to my caps-lock key since I'm using an elderly PC keyboard. Regardless, I think that anyone on a Mac that uses this module would find the default search command (ALT-Q) causes their browser to quit. :) Though given that my setup isn't conventional Mac, it might be good for someone else on OS X to confirm.

Share this post


Link to post
Share on other sites

The Alt key (also called the Option key) on Macs is normally used for special characters and adding umlauts and accents on letters. The default command for quit is CMD + Q. For me, the Alt + Q is not used for anything important (well it creates this nice character - œ )

Great module soma - very useful.

Did you think of a way around the issue with it not working when the field is in focus? I’d really like to be able to edit a field and then Ctrl + S to save - at present there is no way to quickly get out of the field so the shortcuts will work, without using the mouse. Maybe if you could press escape to exit the field and then use the shortcut? Or could you bind the plugin to all input fields? I am guessing you might also have some issues with Tinymce which has its own keyboard shortcuts. Probably not a simple solution to this one.

I like the search overlays, it’s like a quick launcher - pressing Escape to close the overlay dialog would be useful.

If you are looking for inspiration for more shortcuts I always thought the Gmail ones were very good

http://support.google.com/mail/bin/answer.py?hl=en&answer=6594

A way to navigate the tree would be great (although the “quick launcher” way is probably much better). Or a way to open next and previous items in the tree.

And a help overlay mapped to ? which shows current shortcuts would be useful during the Shortcut learning phase (and for clients)

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Robin S
      A community member raised a question and I thought a new sanitizer method for the purpose would be useful, hence...
      Sanitizer Transliterate
      Adds a transliterate method to $sanitizer that performs character replacements as defined in the module config. The default character replacements are based on the defaults from InputfieldPageName, but with uppercase characters included too.
      Usage
      Install the Sanitizer Transliterate module.
      Customise the character replacements in the module config as needed.
      Use the sanitizer on strings like so:
      $transliterated_string = $sanitizer->transliterate($string);
       
      https://github.com/Toutouwai/SanitizerTransliterate
      https://modules.processwire.com/modules/sanitizer-transliterate/
       
    • By dimitrios
      Hello,
      this module can publish content of a Processwire page on a Facebook page, triggered by saving the Processwire page.
      To set it up, configure the module with a Facebook app ID, secret and a Page ID. Following is additional configuration on Facebook for developers:
      Minimum Required Facebook App configuration:
      on Settings -> Basics, provide the App Domains, provide the Site URL, on Settings -> Advanced, set the API version to 2.10, add Product: Facebook Login, on Facebook Login -> Settings, set Client OAuth Login: Yes, set Web OAuth Login: Yes, set Enforce HTTPS: Yes, add "http://www.example.com/processwire/page/" to field Valid OAuth Redirect URIs. This module is configurable as follows:
      Templates: posts can take place only for pages with the defined templates. On/Off switch: specify a checkbox field that will not allow the post if checked. Specify a message and/or an image for the post.
      Usage
      edit the desired PW page and save; it will post right after the initial Facebook log in and permission granting. After that, an access token is kept.
       
      Download
      PW module directory: http://modules.processwire.com/modules/auto-fb-post/ Github: https://github.com/kastrind/AutoFbPost   Note: Facebook SDK for PHP is utilized.


    • By thomasaull
      I created a little helper module to trigger a CI pipeline when your website has been changed. It's quite simple and works like this: As soon as you save a page the module sets a Boolean via a pages save after hook. Once a day via LazyCron the module checks if the Boolean is set and sends a POST Request to a configurable Webhook URL.
      Some ideas to extend this:
      make request type configurable (GET, POST) make the module trigger at a specified time (probably only possible with a server cronjob) trigger manually Anything else? If there's interest, I might put in some more functionality. Let me know what you're interested in. Until then, maybe it is useful for a couple of people 🙂
      Github Repo: https://github.com/thomasaull/CiTrigger
    • By Robin S
      I created this module a while ago and never got around to publicising it, but it has been outed in the latest PW Weekly so here goes the support thread...
      Unique Image Variations
      Ensures that all ImageSizer options and focus settings affect image variation filenames.

      Background
      When using methods that produce image variations such as Pageimage::size(), ProcessWire includes some of the ImageSizer settings (height, width, cropping location, etc) in the variation filename. This is useful so that if you change these settings in your size() call a new variation is generated and you see this variation on the front-end.
      However, ProcessWire does not include several of the other ImageSizer settings in the variation filename:
      upscaling cropping, when set to false or a blank string interlace sharpening quality hidpi quality focus (whether any saved focus area for an image should affect cropping) focus data (the top/left/zoom data for the focus area) This means that if you change any of these settings, either in $config->imageSizerOptions or in an $options array passed to a method like size(), and you already have variations at the requested size/crop, then ProcessWire will not create new variations and will continue to serve the old variations. In other words you won't see the effect of your changed ImageSizer options on the front-end until you delete the old variations.
      Features
      The Unique Image Variations module ensures that any changes to ImageSizer options and any changes to the focus area made in Page Edit are reflected in the variation filename, so new variations will always be generated and displayed on the front-end.
      Installation
      Install the Unique Image Variations module.
      In the module config, set the ImageSizer options that you want to include in image variation filenames.
      Warnings
      Installing the module (and keeping one or more of the options selected in the module config) will cause all existing image variations to be regenerated the next time they are requested. If you have an existing website with a large number of images you may not want the performance impact of that. The module is perhaps best suited to new sites where image variations have not yet been generated.
      Similarly, if you change the module config settings on an existing site then all image variations will be regenerated the next time they are requested.
      If you think you might want to change an ImageSizer option in the future (I'm thinking here primarily of options such as interlace that are typically set in $config->imageSizerOptions) and would not want that change to cause existing image variations to be regenerated then best to not include that option in the module config after you first install the module.
       
      https://github.com/Toutouwai/UniqueImageVariations
      https://modules.processwire.com/modules/unique-image-variations/
    • By Sebi
      I've created a small module which lets you define a timestamp after which a page should be accessible. In addition you can define a timestamp when the release should end and the page should not be accessable any more.
      ProcessWire-Module: http://modules.processwire.com/modules/page-access-releasetime/
      Github: https://github.com/Sebiworld/PageAccessReleasetime
      Usage
      PageAccessReleasetime can be installed like every other module in ProcessWire. Check the following guide for detailed information: How-To Install or Uninstall Modules
      After that, you will find checkboxes for activating the releasetime-fields at the settings-tab of each page. You don't need to add the fields to your templates manually.
      Check e.g. the checkbox "Activate Releasetime from?" and fill in a date in the future. The page will not be accessable for your users until the given date is reached.
      If you have $config->pagefileSecure = true, the module will protect files of unreleased pages as well.
      How it works
      This module hooks into Page::viewable to prevent users to access unreleased pages:
      public function hookPageViewable($event) { $page = $event->object; $viewable = $event->return; if($viewable){ // If the page would be viewable, additionally check Releasetime and User-Permission $viewable = $this->canUserSee($page); } $event->return = $viewable; } To prevent access to the files of unreleased pages, we hook into Page::isPublic and ProcessPageView::sendFile.
      public function hookPageIsPublic($e) { $page = $e->object; if($e->return && $this->isReleaseTimeSet($page)) { $e->return = false; } } The site/assets/files/ directory of pages, which isPublic() returns false, will get a '-' as prefix. This indicates ProcessWire (with activated $config->pagefileSecure) to check the file's permissions via PHP before delivering it to the client.
      The check wether a not-public file should be accessable happens in ProcessPageView::sendFile. We throw an 404 Exception if the current user must not see the file.
      public function hookProcessPageViewSendFile($e) { $page = $e->arguments[0]; if(!$this->canUserSee($page)) { throw new Wire404Exception('File not found'); } } Additionally we hook into ProcessPageEdit::buildForm to add the PageAccessReleasetime fields to each page and move them to the settings tab.
      Limitations
      In the current version, releasetime-protected pages will appear in wire('pages')->find() queries. If you want to display a list of pages, where pages could be releasetime-protected, you should double-check with $page->viewable() wether the page can be accessed. $page->viewable() returns false, if the page is not released yet.
      If you have an idea how unreleased pages can be filtered out of ProcessWire selector queries, feel free to write an issue, comment or make a pull request!
×
×
  • Create New...