Jump to content
tpr

AdminOnSteroids

Recommended Posts

Hey @tpr - you have been busy while I have been away :) I haven't played with it yet, but it looks awesome - do you feel like another feature request?

https://processwire.com/talk/topic/13041-pw-3015-new-quick-tree-debug-view-panels-and-more/?p=118514

Not sure how easy this would be to do in your module, but thought I'd throw it out there!

Share this post


Link to post
Share on other sites

I hope Ryan plans to add such features to the panels you requested. I guess some features could be implemented easily, like auto width, position next to content, etc. I'll see.

  • Like 2

Share this post


Link to post
Share on other sites

Ever got lost in asm field(set) hell? This might help:

post-3156-0-46179900-1465626292_thumb.gi

  • Like 6

Share this post


Link to post
Share on other sites

Just uploaded v019 with the collapsable asmSelect fields update. The screenshot in the previous post was updated because there's always an icon in the beginning of the row to make the hierarchy easier to see (there was only a "+" icon beforehands). Double-clicking on the ending item also collapses the section.

The update does not contain the ctrl+s CKEditor feature, I need to think it through how to organize.

  • Like 2

Share this post


Link to post
Share on other sites

hey tpr,

one thing that i find annoying some times is that multi-column-fields are stacked on mobile but also set to have the same height. on desktop that makes sense so that it is a proper grid, but on mobile the fields are stacked to 1 column and therefore it would be great if every field had only the height itself needs.

but maybe that should be more a fix of the core than an "enhancement" via your module. what do you think?

Share this post


Link to post
Share on other sites

I think the admin is meant to be used on desktop but I'll see if there's an easy fix to this, maybe setting height: auto or similar is enough. Could you show an example scenario where this happens? (what field to add with what settings)

Edit: try adding this to AdminOnSteroids.css and see if it helps:

.maxColHeightSpacer {
    display: none;
}
  • Like 1

Share this post


Link to post
Share on other sites
@media screen and (max-width: 767px) {
  .maxColHeightSpacer {
    display: none;
  }
}

that fixes the problem on the standard theme

what do you think? i think this should be fixed in the core.

Share this post


Link to post
Share on other sites

Seems OK to me - google shows that this was already on the table in PW forums:

https://processwire.com/talk/topic/10802-issues-with-javascript-setheight-function-in-pw-admin/

AOS v02 is just uploaded, with some AsmTweaks fixes and a feature to move the delete button to the left on Asm fields. I use a wide screen monitor and this bugged me a lot :)

  • Like 1

Share this post


Link to post
Share on other sites

Great addon! Have been using it and I like how it tweaks the admin. 

This feels like when I found out about HelperFieldLinks. Maybe one day all of this will go into "power user mode" module.

Share this post


Link to post
Share on other sites

Thanks! Glad to hear that. I also use it on my sites and it speeds up navigation and feels better, but of course that can be because it's tailored to my likings.

What submodules are you using?

I've also thought about adding edit links to fields/templates like HelperFieldLinks do, but without the info popup.

v021 is uploaded to GitHub:

  • sticky admin tabs when compact sticky header is enabled
  • stickyCKEditorToolbar fix for multilanguage fields
  • module submitted to modules directory
  • CSS fixes

The tabs are sticked to the header so when the site is scrolled down they are still visible, no need to scroll up.

aos-stickytabs.png

  • Like 2

Share this post


Link to post
Share on other sites

Another commit today containing the new Hotkeys submodule. This enables saving page on ctrl+s, even from within CKEditor. What's more, it works on various page types, eg. when editing templates, fields, roles, etc. As there was no general rule I could apply to save pages, I had to manually add the enabled ones, so if you find a page type which doesn't work but should, please report.

If enabled, the submodule will disable the default browser Save dialog on all admin pages. I think that dialog has no function in the admin but correct me if I'm wrong.

On save there's a white overlay with a fancy css3 animated floppy icon, to  indicate something's happening:

aos-save.gif

  • Like 7

Share this post


Link to post
Share on other sites

Version 0.2.3 is uploaded, and it's also available from the Modules Directory:

http://modules.processwire.com/modules/admin-on-steroids/

  • new submodule NoAnims: disable all admin animations (CSS & JS)
  • fix for module repository update showing "Requires 0.0.0 >= 0" (reported by matjazp)
  • CSS fixes
  • Like 3

Share this post


Link to post
Share on other sites

Updated to v025, here are the latest changes:

0.2.5 (2016-06-28)

  • new RenoTweak: miniScrollbar for main content and sidebar (using perfect-scrollbar.js)
  • added Language Translator page to the supported hotkey save pages

0.2.4 (2016-06-26)

  • remove ctrl+click feature to activate all language tabs of the same language (core feature from ProcessWire 3.023)
  • FireFox fix for clearing filterbox

miniScrollbar in action:

aos-customScrollbar.gif

  • Like 5

Share this post


Link to post
Share on other sites

@bernhard Just noticed that before you wrote, glad it's fixed.

AOS v026 is uploaded with two tiny update: allow ctrl+s on the first step of Add new page + adding sequential tabindices to inputs (textareas, selects). The latter solves the issue that often TABbing doesn't jump to the next input because there are other inputs in between. This solution isn't perfect but it's very simple, and it would do in most cases. Also works with ajax-loaded fields/tabs.

  • Like 1

Share this post


Link to post
Share on other sites

Great module tpr. Some really great features.

I just had an idea and wasn't sure if a module or feature request existed already? or wether it should belong here or in the core?

I like the minimalistic and ease of use by Processwire and mods your module offers and was thinking would be great to have an option to hide all notes for all fields, or the option to have these converted to an icon near the field title (such as a question mark icon), for fields which have them, and on hover to then show any notes set to the field. 

I think this would save a lot of screen real estate as users who are more frequent with the use of the CMS, tend to not require to see the notes after a while.

Not sure how hard this would be though? :)

Anyway, thanks for the great module!

  • Like 1

Share this post


Link to post
Share on other sites

I only occassionally use description and notes but I agree that it could save some space.

@bernhard I saw that topic earlier, thanks. At first I'll see if I can do it CSS only, that would be more lightweight and unobtrusive. Here is a quick demo of the first mockup (written in dev tools):

aos-css-tooltip.gif

Update: the double coffee worked :)

aos-css-tooltip-1.gif

aos-css-tooltip-2.gif

  • Like 5

Share this post


Link to post
Share on other sites

Just added two screencaps to the post above. On the last one the tooltip occupies the whole field area, I'm curious what do you think about that. It's better in dev POV because there are no z-index issues (in some cases the tooltip got cut by other elements). Or the tooltip could go to the right of the icon, with its arrow pointing leftwards.

  • Like 1

Share this post


Link to post
Share on other sites

Wow. What kind of coffee you drinking?! I didn't expect something so soon. :)

I like the last one too. Looks good!

  • Like 1

Share this post


Link to post
Share on other sites
31 minutes ago, grimezy said:

Wow. What kind of coffee you drinking?!

corporate :)

Here is the basic tooltip-version that have notes and description fields. On double-click the tooltip stays visible, to enable copying text. There is a hack to tackle IE and if the content has html, that's also covered.

aos-css-tooltip-3.gif

  • Like 5

Share this post


Link to post
Share on other sites

Well done.  

I was going to suggest something previously, such as a click to keep things visible for copying, but didn't want to push my luck!!

  • Like 1

Share this post


Link to post
Share on other sites

v027 is up with the Tooltips submodule. The CSS got a bit complicated but hopefully everything will be fine forever so I don't have to dive into it again :)

You can switch whether to use it for field descriptions and/or notes, and whether to use the "overlay" style.

  • Like 6

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 Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-07-03 -- SnipWire 0.8.7 (beta) released! Fixes some small bugs and adds an indicator for TEST mode 2020-04-06 -- SnipWire 0.8.6 (beta) released! Adds support for Snipcart subscriptions and also fixes some problems 2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Multi currency support Custom order and cart fields Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  

       
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • By Sten
      Hello
      Till now I hacked something with the twig template but it works no more with new PW versions so I look forward to create a module. I am working on a site in multiple languages : French, English, Italian, German, Spanish, Portuguese, Hebrew, Russian. The new posts are entered in any language with a field for language. Till now, I got twig files to get the translations with constants defined for each part of the pages.
      So I'd like to create a module to include theses files added according to the url /fr/en/...
      Have you some observations to do before I begin about the direction to take ?
      Thank you
    • By ukyo
      Mystique Module for ProcessWire CMS/CMF
      Github repo : https://github.com/trk/Mystique
      Mystique module allow you to create dynamic fields and store dynamic fields data on database by using a config file.
      Requirements
      ProcessWire 3.0 or newer PHP 7.0 or newer FieldtypeMystique InputfieldMystique Installation
      Install the module from the modules directory:
      Via Composer:
      composer require trk/mystique Via git clone:
      cd your-processwire-project-folder/ cd site/modules/ git clone https://github.com/trk/Mystique.git Module in live reaction with your Mystique config file
      This mean if you remove a field from your config file, field will be removed from edit screen. As you see on youtube video.
      Using Mystique with your module or use different configs path, autoload need to be true for modules
      Default configs path is site/templates/configs/, and your config file name need to start with Mystique. and need to end with .php extension.
      Adding custom path not supporting anymore !
      // Add your custom path inside your module class`init` function, didn't tested outside public function init() { $path = __DIR__ . DIRECTORY_SEPARATOR . 'configs' . DIRECTORY_SEPARATOR; Mystique::add($path); } Mystique module will search site/modules/**/configs/Mystique.*.php and site/templates/Mystique.*.php paths for Mystique config files.
      All config files need to return a PHP ARRAY like examples.
      Usage almost same with ProcessWire Inputfield Api, only difference is set and showIf usage like on example.
      <?php namespace ProcessWire; /** * Resource : testing-mystique */ return [ 'title' => __('Testing Mystique'), 'fields' => [ 'text_field' => [ 'label' => __('You can use short named types'), 'description' => __('In file showIf working like example'), 'notes' => __('Also you can use $input->set() method'), 'type' => 'text', 'showIf' => [ 'another_text' => "=''" ], 'set' => [ 'showCount' => InputfieldText::showCountChars, 'maxlength' => 255 ], 'attr' => [ 'attr-foo' => 'bar', 'attr-bar' => 'foo' ] ], 'another_text' => [ 'label' => __('Another text field (default type is text)') ] ] ]; Example:
      site/templates/configs/Mystique.seo-fields.php <?php namespace ProcessWire; /** * Resource : seo-fields */ return [ 'title' => __('Seo fields'), 'fields' => [ 'window_title' => [ 'label' => __('Window title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'attr' => [ 'placeholder' => __('Enter a window title') ] ], 'navigation_title' => [ 'label' => __('Navigation title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'showIf' => [ 'window_title' => "!=''" ], 'attr' => [ 'placeholder' => __('Enter a navigation title') ] ], 'description' => [ 'label' => __('Description for search engines'), 'type' => Mystique::TEXTAREA, 'useLanguages' => true ], 'page_tpye' => [ 'label' => __('Type'), 'type' => Mystique::SELECT, 'options' => [ 'basic' => __('Basic page'), 'gallery' => __('Gallery'), 'blog' => __('Blog') ] ], 'show_on_nav' => [ 'label' => __('Display this page on navigation'), 'type' => Mystique::CHECKBOX ] ] ]; Searching data on Mystique field is limited. Because, Mystique saving data to database in json format. When you make search for Mystique field, operator not important. Operator will be changed with %= operator.
      Search example
      $navigationPages = pages()->find('my_mystique_field.show_on_nav=1'); $navigationPages = pages()->find('my_mystique_field.page_tpye=gallery');
    • By Robin S
      This is a module I made as an experiment a while ago and never got around to releasing publicly. At the time it was prompted by discussions around using Repeater fields for "page builder" purposes, where the depth feature could possibly be used for elements that would be nested inside other elements. I thought it would be useful to enforce some depth rules and translate the depth data into a multi-dimensional array structure.
      I'm not using this module anywhere myself but maybe it's useful to somebody.
      Repeater Depth Helper
      This module does two things relating to Repeater fields that have the "Item depth" option enabled:
      It enforces some depth rules for Repeater fields on save. Those rules are:
      The first item must have a depth of zero. Each item depth must not be more than one greater than previous item depth. It provides a RepeaterPageArray::getDepthStructure helper method that returns a nested depth structure for a Repeater field value.
      Helper method
      The module adds a RepeaterPageArray::getDepthStructure method that returns a multi-dimensional array where the key is the page ID and the value is an array of nested "child" items, or null if there are no nested children.
      Example

      The module doesn't make any assumptions about how you might want to use the depth structure array, but here is a way you might use it to output a nested unordered list.
      // Output a nested unordered list from a depth structure array function outputNestedList($depth_structure, $repeater_items) { $out = "<ul>"; foreach($depth_structure as $page_id => $nested_children) { $out .= "<li>" . $repeater_items->get("id=$page_id")->title; // Go recursive if there are nested children if(is_array($nested_children)) $out .= outputNestedList($nested_children, $repeater_items); $out .= "</li>"; } $out .= "</ul>"; return $out; } $repeater_items = $page->my_repeater; $depth_structure = $repeater_items->getDepthStructure(); echo outputNestedList($depth_structure, $repeater_items);
       
      https://github.com/Toutouwai/RepeaterDepthHelper
      https://modules.processwire.com/modules/repeater-depth-helper/
    • By MoritzLost
      Cacheable Placeholders
      This module allows you to have pieces of dynamic content inside cached output. This aims to solve the common problem of having a mostly cacheable site, but with pieces of dynamic output here and there.  Consider this simple example, where you want to output a custom greeting to the current user:
      <h1>Good morning, <?= ucfirst($user->name) ?></h1> This snippet means you can't use the template cache (at least for logged-in users), because each user has a different name. Even if 99% of your output is static, you can only cache the pieces that you know won't include this personal greeting. A more common example would be CSRF tokens for HTML forms - those need to be unique by definition, so you can't cache the form wholesale.
      This module solves this problem by introducing cacheable placeholders - small placeholder tokens that get replaced during every request. The replacement is done inside a Page::render hook so it runs during every request, even if the response is served from the template cache. So you can use something like this:
      <h1>Good morning, {{{greeting}}}</h1> Replacement tokens are defined with a callback function that produces the appropriate output and added to the module through a simple hook:
      // site/ready.php wire()->addHookAfter('CachePlaceholders::getTokens', function (HookEvent $e) { $tokens = $e->return; $tokens['greeting'] = [ 'callback' => function (array $tokenData) { return ucfirst(wire('user')->name); } ]; $e->return = $tokens; }); Tokens can also include parameters that are parsed and passed to the callback function. There are more fully annotated examples and step-by-step instructions in the README on Github!
      Features
      A simple and fast token parser that calls the appropriate callback and runs automatically. Tokens may include multiple named or positional parameters, as well as multi-value parameters. A manual mode that allows you to replace tokens in custom pieces of cached content (useful if you're using the $cache API). Some built-in tokens for common use-cases: CSRF-Tokens, replacing values from superglobals and producing random hexadecimal strings. The token format is completely customizable, all delimiters can be changed to avoid collisions with existing tag parsers or template languages. Links
      Github Repository & documentation Module directory If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
×
×
  • Create New...