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

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By MoritzLost
      This is a new module that provides a simple solution to clearing all your cache layers at once, and an extensible interface to perform various cache-related actions.
      The simple motivation behind this module was that I was tired of manually clearing caches in several places after deploying a change on a live site. The basic purpose of this module is a simple Clear all caches link in the Setup menu which clears out all caches, no matter where they hide. You can customize what exactly the module does through it's configuration menu:
      Expire or delete all cache entries in the database, or selectively clear caches by namespace ($cache API) Clear the the template render cache. Clear out specific folders inside your site's cache directory (/site/assets/cache) Refresh version strings for static assets to bust client-side browser caches (this requires some setup, see the full documentation for details). This is the basic function of the module. However, you can also add different cache management action through the API and execute them through the module's interface. For this advanced usage, the module provides:
      An interface to see all available cache actions and execute them. A system log and logging output on the module page to see verify what the module is doing. A CacheControlTools class with utility functions to clear out different caches. An API to add cache actions, execute them programmatically and even modify the default action. Permission management, allowing you granular control over which user roles can execute which actions. The complete documentation can be found in the module's README.
      Beta release
      Note that I consider this a Beta release. Since the module is relatively aggressive in deleting some caches, I would advise you to install in on a test environment before using it on a live site.
      Let me know if you're getting any errors, have trouble using the module or if you have suggestions for improvement!
      In particular, can someone let me know if this module causes any problems with the ProCache module? I don't own or use it, so I can't check. As far as I can tell, ProCache uses a folder inside the cache directory to cache static pages, so my module should be able to clear the ProCache site cache as well, I'd appreciate it if someone can test that for me.
      Future plans
      If there is some interest in this, I plan to expand this to a more general cache management solution. I particular, I would like to add additional cache actions. Some ideas that came to mind:
      Warming up the template render cache for publicly accessible pages. Removing all active user sessions. Let me know if you have more suggestions!
      Links
      https://github.com/MoritzLost/ProcessCacheControl ProcessCacheControl in the Module directory

    • By joshua
      This module is (yet another) way for implementing a cookie management solution.
      Of course there are several other possibilities:
      - https://processwire.com/talk/topic/22920-klaro-cookie-consent-manager/
      - https://github.com/webmanufaktur/CookieManagementBanner
      - https://github.com/johannesdachsel/cookiemonster
      - https://www.oiljs.org/
      - ... and so on ...
      In this module you can configure which kind of cookie categories you want to manage:

      You can also enable the support for respecting the Do-Not-Track (DNT) header to don't annoy users, who already decided for all their browsing experience.
      Currently there are four possible cookie groups:
      - Necessary (always enabled)
      - Statistics
      - Marketing
      - External Media
      All groups can be renamed, so feel free to use other cookie group names. I just haven't found a way to implement a "repeater like" field as configurable module field ...
      When you want to load specific scripts ( like Google Analytics, Google Maps, ...) only after the user's content to this specific category of cookies, just use the following script syntax:
      <script type="optin" data-type="text/javascript" data-category="statistics" data-src="/path/to/your/statistic/script.js"></script> <script type="optin" data-type="text/javascript" data-category="marketing" data-src="/path/to/your/mareketing/script.js"></script> <script type="optin" data-type="text/javascript" data-category="external_media" data-src="/path/to/your/external-media/script.js"></script> <script type="optin" data-type="text/javascript" data-category="marketing">console.log("Inline scripts are also working!");</script> The type has to be "optin" to get recognized by PrivacyWire, the data-attributes are giving hints, how the script shall be loaded, if the data-category is within the cookie consents of the user. These scripts are loaded asynchronously after the user made the decision.
      If you want to give the users the possibility to change their consent, you can use the following Textformatter:
      [[privacywire-choose-cookies]] It's planned to add also other Textformatters to opt-out of specific cookie groups or delete the whole consent cookie.
      You can also add a custom link to output the banner again with a link / button with following class:
      <a href="#" class="privacywire-show-options">Show Cookie Options</a> <button class="privacywire-show-options">Show Cookie Options</button> This module is still in development, but we already use it on several production websites.
      You find it here: https://github.com/blaueQuelle/privacywire/tree/master
      Download: https://github.com/blaueQuelle/privacywire/archive/master.zip
      I would love to hear your feedback 🙂
      Edit: Updated URLs to master tree of git repo
       
    • By David Karich
      Admin Page Tree Multiple Sorting
      ClassName: ProcessPageListMultipleSorting
      Extend the ordinary sort of children of a template in the admin page tree with multiple properties. For each template, you can define your own rule. Write each template (template-name) in a row, followed by a colon and then the additional field names for sorting.
      Example: All children of the template "blog" to be sorted in descending order according to the date of creation, then descending by modification date, and then by title. Type:
      blog: -created, -modified, title  Installation
      Copy the files for this module to /site/modules/ProcessPageListMultipleSorting/ In admin: Modules > Check for new modules. Install Module "Admin Page Tree Multible Sorting". Alternative in ProcessWire 2.4+
      Login to ProcessWire backend and go to Modules Click tab "New" and enter Module Class Name: "ProcessPageListMultipleSorting" Click "Download and Install"   Compatibility   I have currently tested the module only under PW 2.6+, but think that it works on older versions too. Maybe someone can give a feedback.     Download   PW-Repo: http://modules.processwire.com/modules/process-page-list-multiple-sorting/ GitHub: https://github.com/FlipZoomMedia/Processwire-ProcessPageListMultipleSorting     I hope someone can use the module. Have fun and best regards, David
    • 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 (has been tested up to v3.3), add Product: Facebook Login, on Facebook Login -> Settings, set Client OAuth Login: Yes, set Web OAuth Login: Yes, set Enforce HTTPS: Yes, add "https://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.


×
×
  • Create New...