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

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

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 teppo
      MarkupMenu is a markup module for generating menu trees. When provided a root page as a starting point, it generates a navigation tree (by default as a HTML "<ul>" element wrapped by a "<nav>" element) from that point onwards. If you've also provided it with current (active) page, the menu will be rendered accordingly, with current item highlighted and items rendered up to that item and its children (unless you disable the "collapsed" option, in which case the full page tree will be rendered instead).
      Modules directory: https://modules.processwire.com/modules/markup-menu/ GitHub repository: https://github.com/teppokoivula/MarkupMenu Usage
      As a markup module, MarkupMenu is intended for front-end use, but you can of course use it in a module as well. Typically you'll only need the render() method, which takes an array of options as its only argument:
      echo $modules->get('MarkupMenu')->render([ 'root_page' => $pages->get(1), 'current_page' => $page, ]); Note: if you omit root_page, site root page is used by default. If you omit current_page, the menu will be rendered, but current (active) page won't be highlighted etc.
      A slightly more complex example, based on what I'm using on one of my own sites to render a (single-level) top menu:
      echo $modules->get('MarkupMenu')->render([ 'current_page' => $page, 'templates' => [ 'nav' => '<nav class="{classes} menu--{menu_class_modifier}" aria-label="{aria_label}">%s</nav>', 'item_current' => '<a class="menu__item menu__item--current" href="{item.url}" tabindex="0" aria-label="Current page: {item.title}">{item.title}</a>', ], 'placeholders' => [ 'menu_class_modifier' => 'top', 'aria_label' => 'Main navigation', ], 'include' => [ 'root_page' => true, ], 'exclude' => [ 'level_greater_than' => 1, ], ]); Note: some things you see above may not be entirely sensible, such as the use of {menu_class_modifier} and {aria_label} placeholders. On the actual site the "nav" template is defined in site config, so I can define just these parts on a case-by-case basis while actual nav markup is maintained in one place.
      Please check out the README file for available render options. I'd very much prefer not to keep this list up to date in multiple places. Basically there are settings for defining "templates" for different parts of the menu (list, item, etc.), include array for defining rules for including in the menu and exclude array for the opposite effect, classes and placeholders arrays for overriding default classes and injecting custom placeholders, etc. 🙂
      MarkupMenu vs. MarkupSimpleNavigation
      TL;DR: this is another take on the same concept. There are many similarities, but also some differences – especially when it comes to the supported options and syntax. If you're currently using MarkupSimpleNavigation then there's probably no reason to switch over.
      I'd be surprised if anyone didn't draw lines between this module and Soma's awesome MarkupSimpleNavigation. Simply put, I've been using MSN (...) for a number of years, and it's been great – but there have been some smallish issues with it, particularly with the markup generation part, and it's also doing some things in a way that just doesn't work for me – the xtemplates thing being one of these. In many ways it's less about features, and more about style.
      In MarkupMenu I've tried to correct these little hiccups, modernise the default markup, and allow for more flexibility with placeholder variables and additional / different options. MarkupMenu was built for ProcessWire 3.0.112+ and PHP 7.1+, it's installable with Composer, and I have a few additional ideas (such as conditional placeholders) on my todo list.
      One smallish and rather specific difference is that MarkupMenu supports overriding default options via $config->MarkupMenu. I find myself redefining the default markup for every site, which until now meant that each site has a wrapper function for MarkupSimpleNavigation (to avoid code / config repetition), and this way I've been able to omit that 🙂
      Requirements
      ProcessWire >= 3.0.112 PHP >= 7.1.0 If you're working on an earlier version of ProcessWire or PHP, use MarkupSimpleNavigation instead.
    • By Robin S
      Repeater Images
      Adds options to modify Repeater fields to make them convenient for "page-per-image" usage. Using a page-per-image approach allows for additional fields to be associated with each image, to record things such as photographer, date, license, links, etc.
      When Repeater Images is enabled for a Repeater field the module changes the appearance of the Repeater inputfield to be similar (but not identical) to an Images field. The collapsed view shows a thumbnail for each Repeater item, and items can be expanded for field editing.
      Screencast

      Installation
      Install the Repeater Images module.
      Setup
      Create an image field to use in the Repeater field. Recommended settings for the image field are "Maximum files allowed" set to 1 and "Formatted value" set to "Single item (null if empty)". Create a Repeater field. Add the image field to the Repeater. If you want additional fields in the Repeater create and add these also. Repeater Images configuration
      Tick the "Activate Repeater Images for this Repeater field" checkbox. In the "Image field within Repeater" dropdown select the single image field. You must save the Repeater field settings to see any newly added Image fields in the dropdown. Adjust the image thumbnail height if you want (unlike the core Images field there is no slider to change thumbnail height within Page Edit). Note: the depth option for Repeater fields is not compatible with the Repeater Images module.
      Image uploads feature
      There is a checkbox to activate image uploads. This feature allows users to quickly and easily add images to the Repeater Images field by uploading them to an adjacent "upload" field.
      To use this feature you must add the image field selected in the Repeater Images config to the template of the page containing the Repeater Images field - immediately above or below the Repeater Images field would be a good position.
      It's recommended to set the label for this field in template context to "Upload images" or similar, and set the visibility of the field to "Closed" so that it takes up less room when it's not being used. Note that when you drag images to a closed Images field it will automatically open. You don't need to worry about the "Maximum files allowed" setting because the Repeater Images module overrides this for the upload field.
      New Repeater items will be created from the images uploaded to the upload field when the page is saved. The user can add descriptions and tags to the images while they are still in the upload field and these will be retained in the Repeater items. Images are automatically deleted from the upload field when the page is saved.
      Tips
      The "Use accordion mode?" option in the Repeater field settings is useful for keeping the inputfield compact, with only one image item open for editing at a time. The "Repeater item labels" setting determines what is shown in the thumbnail overlay on hover. Example for an image field named "image": {image.basename} ({image.width}x{image.height})  
      https://github.com/Toutouwai/RepeaterImages
      https://modules.processwire.com/modules/repeater-images/
    • By EyeDentify
      Hello There Guys.

      I am in the process of getting into making my first modules for PW and i had a question for you PHP and PW gurus in here.

      I was wondering how i could use an external library, lets say TwitterOAuth in my PW module.
      Link to library
      https://twitteroauth.com/

      Would the code below be correct or how would i go about this:
      <?PHP namespace ProcessWire; /* load the TwitterOAuth library from my Module folder */ require "twitteroauth/autoload.php"; use Abraham\TwitterOAuth\TwitterOAuth; class EyeTwitter extends WireData,TwitterOAuth implements Module { /* vars */ protected $twConnection; /* extend parent TwitterOAuth contructor $connection = new TwitterOAuth(CONSUMER_KEY, CONSUMER_SECRET, $access_token, $access_token_secret); */ public function myTwitterConnection ($consumer_key, $consumer_secret, $access_token, $access_token_secret) { /* save the connection for use later */ $this->twConnection = TwitterOAuth::__construct($consumer_key, $consumer_secret, $access_token, $access_token_secret); } } ?> Am i on the right trail here or i am barking up the wrong tree?
      I don´t need a complete solution, i just wonder if i am including the external library the right way.
      If not, then give me a few hint´s and i will figure it out.

      Thanks a bunch.

      /EyeDentify
    • 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 "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 kongondo
      FieldtypeRuntimeMarkup and InputfieldRuntimeMarkup
       
      Modules Directory: http://modules.processwire.com/modules/fieldtype-runtime-markup/
      GitHub: https://github.com/kongondo/FieldtypeRuntimeMarkup
      As of 11 May 2019 ProcessWire versions earlier than 3.x are not supported
      This module allows for custom markup to be dynamically (PHP) generated and output within a page's edit screen (in Admin).
       
      The value for the fieldtype is generated at runtime. No data is saved in the database. The accompanying InputfieldRuntimeMarkup is only used to render/display the markup in the page edit screen.
       
      The field's value is accessible from the ProcessWire API in the frontend like any other field, i.e. it has access to $page and $pages.
       
      The module was commissioned/sponsored by @Valan. Although there's certainly other ways to achieve what this module does, it offers a dynamic and flexible alternative to generating your own markup in a page's edit screen whilst also allowing access to that markup in the frontend. Thanks Valan!
       
      Warning/Consideration
      Although access to ProcessWire's Fields' admin pages is only available to Superusers, this Fieldtype will evaluate and run the custom PHP Code entered and saved in the field's settings (Details tab). Utmost care should therefore be taken in making sure your code does not perform any CRUD operations!! (unless of course that's intentional) The value for this fieldtype is generated at runtime and thus no data is stored in the database. This means that you cannot directly query a RuntimeMarkup field from $pages->find(). Usage and API
       
      Backend
      Enter your custom PHP snippet in the Details tab of your field (it is RECOMMENDED though that you use wireRenderFile() instead. See example below). Your code can be as simple or as complicated as you want as long as in the end you return a value that is not an array or an object or anything other than a string/integer.
       
      FieldtypeRuntimeMarkup has access to $page (the current page being edited/viewed) and $pages. 
       
      A very simple example.
      return 'Hello'; Simple example.
      return $page->title; Simple example with markup.
      return '<h2>' . $page->title . '</h2>'; Another simple example with markup.
      $out = '<h1>hello '; $out .= $page->title; $out .= '</h1>'; return $out; A more advanced example.
      $p = $pages->get('/about-us/')->child('sort=random'); return '<p>' . $p->title . '</p>'; An even more complex example.
      $str =''; if($page->name == 'about-us') { $p = $page->children->last(); $str = "<h2><a href='{$p->url}'>{$p->title}</a></h2>"; } else { $str = "<h2><a href='{$page->url}'>{$page->title}</a></h2>"; } return $str; Rather than type your code directly in the Details tab of the field, it is highly recommended that you placed all your code in an external file and call that file using the core wireRenderFile() method. Taking this approach means you will be able to edit your code in your favourite text editor. It also means you will be able to type more text without having to scroll. Editing the file is also easier than editing the field. To use this approach, simply do:
      return wireRenderFile('name-of-file');// file will be in /site/templates/ If using ProcessWire 3.x, you will need to use namespace as follows:
      return ProcessWire\wireRenderFile('name-of-file'); How to access the value of RuntimeMarkup in the frontend (our field is called 'runtime_markup')
       
      Access the field on the current page (just like any other field)
      echo $page->runtime_markup; Access the field on another page
      echo $pages->get('/about-us/')->runtime_markup; Screenshots
       
      Backend
       

       

       
      Frontend
       

×
×
  • Create New...