Jump to content
tpr

AdminOnSteroids

Recommended Posts

That's something I've already thought of but the way I tried to make it work failed and there were other things to do :) I'm not sure this module is the best place to make admin theme corrections, but for a temporary solution it could do.

  • Like 1

Share this post


Link to post
Share on other sites

...I'm not sure this module is the best place to make admin theme corrections, but for a temporary solution it could do.

Well, all your mods should be part of ProcessWire by default, so... :P

  • Like 1

Share this post


Link to post
Share on other sites

very cool tpr!

feature request: an option to show the save options instantly on button hover. i find it really annoying to have to click on this little chevron to show the popup and then have to click again on the right option. i'm still missing the very quick "save+new" and "save+close" from joomla  :-X

offtopic: also thanks for the hint to netteforms - my project needs more time than i thought but it is getting more and more awesome :)

post-2137-0-51778500-1464300856_thumb.pn

Share this post


Link to post
Share on other sites

Giving admin theme corrections a second thought I support the idea. I have a few other fixes in my mind besides your suggestions so stay tuned.

  • Like 1

Share this post


Link to post
Share on other sites

Movie time!

These are two tweaks: always visible sidebar items and fixed header/sidebar. There are still some details to polish but seems useful.

post-3156-0-91689400-1464336862_thumb.gi

  • Like 4

Share this post


Link to post
Share on other sites

Thanks soo much! Can't wait to try it out. Unfortunately I have to deal with a deadline, but I will manage to try it out on the weekend, I'm sure.

  • Like 1

Share this post


Link to post
Share on other sites

feature request: an option to show the save options instantly on button hover.

I would prefer these extra buttons always visible. Waiting for the hover will cause frustration sooner or later :) Perhaps adding them below the main button? 

  • Like 1

Share this post


Link to post
Share on other sites

what i've also came across several times is when on mobile and you have a pagetable and you want to scroll down, if you tap on a pagetable item it will trigger the pagetable sort. it would be great to disable table sorting on mobile. or show just a sort symbol and allow sorting only on this icon.

:)

Share this post


Link to post
Share on other sites

I would prefer these extra buttons always visible. Waiting for the hover will cause frustration sooner or later :) Perhaps adding them below the main button? 

in this case i would prefer them to be rendered beside in one row (inline)

Share this post


Link to post
Share on other sites

v003 is uploaded with some "before-the-weekend" Reno theme updates:

  • Make header sticky: stick the header to the top of the browser window so it stays in place when scrolling down
  • Make sidebar sticky: stick the sidebar to the top to make it always visible
  • Auto hide sidebar on left: auto hide the sidebar so it's accessible by moving the mouse to the left side of the screen
  • Always show sidebar items (disable accordion): make sidebar submenus more compact and do not hide them
  • Place header button next to the main title: moves the top (cloned) main button next to the title to make it easier to reach
  • Move notice close buttons to the left: put the close button of the notice message to the left for easier access
  • Like 3

Share this post


Link to post
Share on other sites

Didn't try the module (great name btw) yet, but how about making header sticky in the default admin theme? after-the-weekend, of course :-)

  • Like 1

Share this post


Link to post
Share on other sites

don't know how your module is organized (deadline coming), but throwing in an idea:

maybe we could have a "custom" folder, where we can put in our own code snippets and your module will make them visible for toggling on/off. 

for example:

/custom/makeButtonsBigger.js would result in some custom code that makes admin buttons bigger and a checkbox in your module. that way we could build our own repository of admin tweaks, put them on github or the like and on every new pw-install we would just have to do a git clone and tick some checkboxes.

what do you think?

this is quite similar to admincustomfiles but i never found it really easy to use so i don't really use it a lot. maybe we could have some kind of syntax in thos files to restrict it to a selector and show some better descriptions in your module/panel

/* custom admin tweak example
 * 
 * #summary
 * this is a great summary
 * with lots of content
 *
 * #pageselector
 * id>10
 *
 * #editedpageselector
 * template=example
 */

$(document).ready(...);

#editedpageselector would refer to the currently edited page in processpageedit, whereas #pageselector would refer to the current admin page

any thoughts on this?

  • Like 1

Share this post


Link to post
Share on other sites

Didn't try the module (great name btw) yet, but how about making header sticky in the default admin theme? after-the-weekend, of course :-)

Check the latest commit (v004). There are other fixes as well for the admin themes, eg. do not apply some changes to modal contents, plus only add body classes to the proper admin themes.

maybe we could have a "custom" folder, where we can put in our own code snippets and your module will make them visible for toggling on/off. 

This would be surely possible but I need some time to fully understand it :) At first I'll concentrate on the "basics".

  • Like 1

Share this post


Link to post
Share on other sites

v006 is up - there are some new Reno theme tweaks plus LoadCollapsedModuleInfos. This auto-collapses module info fields on module configuration pages, saving space. 

  • Like 3

Share this post


Link to post
Share on other sites

v007 is up, with a Reno tweak that removes perhaps the biggest frustration the sidebar causes - the inability to single-click on the header links to navigate.

The module is featured in PW Weekly Nr 107, thanks!

Since the module is under rapid development it's likely that new features will be added before you even get to this post, which is why we won't even try to include a full list of features here.

So true, there's a lot of things awaiting to be fixed :)

  • Like 1

Share this post


Link to post
Share on other sites

v008 is committed to GitHub and it enables showing the Save dropdown menu on hover instead of on click. The only way I found to achieve this is adding a CSS class to the dropwdown which seems to work fine with the exception of Module config pages. Anyway, it covers 99% of the usage scenarios I think.

More agressive modifications were dropped because the markup wasn't generated the way I initially thought and it would be hard to solve.

  • Like 1

Share this post


Link to post
Share on other sites

v009 comes with a small feature update: ctrl+click on a language tab will activate all the language tabs of the same language. This is great for switching the current admin page fields to another language, eg. for checking contents of multiple fields at once.

  • Like 2

Share this post


Link to post
Share on other sites

The latest update (v010) can remove the masthead from the Reno theme. This is available only if sticky header is on. In fact this feature uses another approach for the sticky header because only the main content is scrollable, which perhaps makes it easier to see whether the page is scrolled down or not.

For the Reno theme there is a new setting "AlwaysShowSearch".

Other dropdown buttons are now also supported in the HoverSaveDropdown tweak. Remind me next time not trying to modify a cloned button instance because it won't work :)

There were numerous tweaks made to the admin configuration screen. Nested checkboxes now can't be modified if their parents are not checked, and also some space were saved by playing with field/fieldset options.

post-3156-0-86629700-1464639714_thumb.pn

  • Like 4

Share this post


Link to post
Share on other sites

Hi @tpr,

thanks for making this fine tool for us. Is it for PW 2.7 too, or only for PW 3.x?

I cannot see a "required" property in the getModuleInfo. In the modules header comment it states ProcessWire 3.x, but then I cannnot see a namespace declaration in the file. This all makes me abit unsure, therefor I ask here. Sorry!

  • Like 2

Share this post


Link to post
Share on other sites

Good question. These are mainly front-end stuff so I think it won't have issues with PW 2.x. I'll try it on a 2.x install.

  • Like 1

Share this post


Link to post
Share on other sites

It seems that there are too many little thing changed from v3 which prevents certain features to work on PW v2, at least this is the case with 2.6. There are also some features that are missing from v2 that this module tries to modify, e.g long click duration.

I could breathe life into most of the submodules with little changes but I tend to support v3 only. There's a Hungarian saying "who looks backwards goes ass front to the future" and I believe in it :)

There are some unpublished updates to the module, eg fixed CKEditor toolbar and page preview link next to title. And also there are some bugs still awaiting to eliminate so I'll keep it in the shadows for a while :)

post-3156-0-95109300-1464728731_thumb.pn

  • Like 2

Share this post


Link to post
Share on other sites

i think that would be a perfect fit for your module: https://processwire.com/talk/topic/13419-delete-a-lot-of-pics-at-once

something like an additional trash icon that, when clicked sets all images to deleted-state:

post-2137-0-66957100-1464812800_thumb.pn

maybe you could also include this one into that update ;)

filesort.gif

https://processwire.com/talk/topic/13064-inputfieldfile-image-sorting-autosorting/

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 adrian
      Tracy Debugger for ProcessWire
      The ultimate “swiss army knife” debugging and development tool for the ProcessWire CMF/CMS

       
      Integrates and extends Nette's Tracy debugging tool and adds 35+ custom tools designed for effective ProcessWire debugging and lightning fast development
      The most comprehensive set of instructions and examples is available at: https://adrianbj.github.io/TracyDebugger
      Modules Directory: http://modules.processwire.com/modules/tracy-debugger/
      Github: https://github.com/adrianbj/TracyDebugger
      A big thanks to @tpr for introducing me to Tracy and for the idea for this module and for significant feedback, testing, and feature suggestions.
    • By adrian
      This module allows you to automatically rename file (including image) uploads according to a configurable format
      This module lets you define as many rules as you need to determine how uploaded files will be named and you can have different rules for different pages, templates, fields, and file extensions, or one rule for all uploads. Renaming works for files uploaded via the admin interface and also via the API, including images added from remote URLs.   Github: https://github.com/adrianbj/CustomUploadNames
      Modules Directory: http://modules.processwire.com/modules/process-custom-upload-names/
      Renaming Rules
      The module config allows you to set an unlimited number of Rename Rules. You can define rules to specific fields, templates, pages, and file extensions. If a rule option is left blank, the rule with be applied to all fields/templates/pages/extensions. Leave Filename Format blank to prevent renaming for a specific field/template/page combo, overriding a more general rule. Rules are processed in order, so put more specific rules before more general ones. You can drag to change the order of rules as needed. The following variables can be used in the filename format: $page, $template, $field, and $file. For some of these (eg. $field->description), if they haven't been filled out and saved prior to uploading the image, renaming won't occur on upload, but will happen on page save (could be an issue if image has already been inserted into RTE/HTML field before page save). Some examples: $page->title mysite-{$template->name}-images $field->label $file->description {$page->name}-{$file->filesize}-kb prefix-[Y-m-d_H-i-s]-suffix (anything inside square brackets is is considered to be a PHP date format for the current date/time) randstring[n] (where n is the number of characters you want in the string) ### (custom number mask, eg. 001 if more than one image with same name on a page. This is an enhanced version of the automatic addition of numbers if required) If 'Rename on Save' is checked files will be renamed again each time a page is saved (admin or front-end via API). WARNING: this setting will break any direct links to the old filename, which is particularly relevant for images inserted into RTE/HTML fields. The Filename Format can be defined using plain text and PW $page variable, for example: mysite-{$page->path} You can preserve the uploaded filename for certain rules. This will allow you to set a general renaming rule for your entire site, but then add a rule for a specific page/template/field that does not rename the uploaded file. Just simply build the rule, but leave the Filename Format field empty. You can specify an optional character limit (to nearest whole word) for the length of the filename - useful if you are using $page->path, $path->name etc and have very long page names - eg. news articles, publication titles etc. NOTE - if you are using ProcessWire's webp features, be sure to use the useSrcExt because if you have jpg and png files on the same page and your rename rules result in the same name, you need to maintain the src extension so they are kept as separate files.
      $config->webpOptions = array(     'useSrcExt' => false, // Use source file extension in webp filename? (file.jpg.webp rather than file.webp) ); Acknowledgments
      The module config settings make use of code from Pete's EmailToPage module and the renaming function is based on this code from Ryan: http://processwire.com/talk/topic/3299-ability-to-define-convention-for-image-and-file-upload-names/?p=32623 (also see this post for his thoughts on file renaming and why it is the lazy way out - worth a read before deciding to use this module). 
       
       
      NOTE:
      This should not be needed on most sites, but I work with lots of sites that host PDFs and photos/vectors that are available for download and I have always renamed the files on upload because clients will often upload files with horrible meaningless filenames like:
      Final ReportV6 web version for John Feb 23.PDF

    • By Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.56
      Composer: rockett/jumplinks
      Jumplinks is an enhanced version of the original ProcessRedirects by Antti Peisa.
      The Process module manages your permanent and temporary redirects (we'll call these "jumplinks" from now on, unless in reference to redirects from another module), useful for when you're migrating over to ProcessWire from another system/platform. Each jumplink supports wildcards, shortening the time needed to create them.
      Unlike similar modules for other platforms, wildcards in Jumplinks are much easier to work with, as Regular Expressions are not fully exposed. Instead, parameters wrapped in curly braces are used - these are described in the documentation.
      Under Development: 2.0, to be powered by FastRoute
      As of version 1.5.0, Jumplinks requires at least ProcessWire 2.6.1 to run.
      View on GitLab
      Download via the Modules Directory
      Read the docs
      Features
      The most prominent features include:
      Basic jumplinks (from one fixed route to another) Parameter-based wildcards with "Smart" equivalents Mapping Collections (for converting ID-based routes to their named-equivalents without the need to create multiple jumplinks) Destination Selectors (for finding and redirecting to pages containing legacy location information) Timed Activation (activate and/or deactivate jumplinks at specific times) 404-Monitor (for creating jumplinks based on 404 hits) Additionally, the following features may come in handy:
      Stale jumplink management Legacy domain support for slow migrations An importer (from CSV or ProcessRedirects) Feedback & Feature Requests
      I’d love to know what you think of this module. Please provide some feedback on the module as a whole, or even regarding smaller things that make it whole. Also, please feel free to submit feature requests and their use-cases.
      Note: Features requested so far have been added to the to-do list, and will be added to 2.0, and not the current dev/master branches.
      Open Source

      Jumplinks is an open-source project, and is free to use. In fact, Jumplinks will always be open-source, and will always remain free to use. Forever. If you would like to support the development of Jumplinks, please consider making a small donation via PayPal.
      Enjoy! :)
×
×
  • Create New...