Jump to content

AdminOnSteroids


tpr

Recommended Posts

Good idea. I can't think of any drawbacks that could happen, but maybe I'm wrong.

To avoid the clutter, I would do it on ctrl+click instead any visual icon or something. What do you think about it?

Plus alt+click for edit for example, that's something I have already planned.

  • Like 1
Link to comment
Share on other sites

my vote goes for

view: icon
edit: ctrl+click

:)

only drawback of my method would be if somebody is rewriting urls somehow... maybe also on multisite environments? but at least they have the option to switch it OFF ;)

  • Like 1
Link to comment
Share on other sites

My vote is: 

  • long click for view
  • ctrl+click to edit

or reversed :) Icons would make too much mess.

Btw, I most of the time can't get the long-click work in Chrome 51 (the built-in Edit/View feature). I works 1 times out of 10 or 20. In Firefox seems to work fine.

Link to comment
Share on other sites

Update: looks like it's SlimJet browser only, in Chrome longclicks seem OK.

I got the longclick to work, now I need a similar bright idea how to get the edit link ("/edit/?id=XXX"). Perhaps I need to add all the parents' IDs to an inline JS and get it from there.

  • Like 1
Link to comment
Share on other sites

v035 adds the abovementioned breadcrumb tweaks:

  • long-click on breadcrumb item to view page in frontend
  • ctrl+click to edit breadcrumb page

It's relatively buried under the "Hotkeys" submodule but I think it fits there. 

I'm open to ideas on different implementation of this feature but I woud like to keep the current "minimal" style (eg. better not using icons or hover menu).

  • Like 1
Link to comment
Share on other sites

I'll see, thanks. I think a confirm (yes-no) dialog would be of more help here. Strictly forbidding to save the page may result in data lost if the upload never finishes (so you can't save the page itself at all).

  • Like 2
Link to comment
Share on other sites

@tpr Good evening :)  While tinkering with the settings it occurred to me that it would be nice to be able to adjust the height of the rows of the Pages tree. The Reno theme uses this:

.content .PageList .PageListItem {
    border-bottom: 1px solid #e6ebf1;
    padding-top: 0.6 em;
    padding-bottom: 0.6 em;
    line-height: 1.3em;
}

Top/bottom padding with 0.3 em is quite usable too. Something like the "LongClickDuraton" inputbox would be nice to have to adjust this one too.

What do you think?

Link to comment
Share on other sites

I have tried to improve the page list but I have to admit it's close to perfect as it is (at least for me). I see that this tweak could save some space but I'll wait until other page list related needs arise.

  • Like 2
Link to comment
Share on other sites

The Page tree is a strange beast :) It works and it's usable but still... Anyway, thanks for putting my feature request on your todo list. I just want to save some scrolling. The Page tree of the Default Theme is more compact and I like it that way.

Link to comment
Share on other sites

Thanx in advance! Are you planning to make it adjustable on the fly? I mean not just in the module's settings (preferred default), but right on the page of the page list too. If we can stick to one setting only, then it is not so versatile.

Link to comment
Share on other sites

You mean the page thumbs? There will be one global default (image field name), or template-field pairs for those who need more. Plus a setting for square thumbs, and that's all.

I think these settings are easier to use because you can set everything at one place (module settings).

Link to comment
Share on other sites

I think I'll go with this syntax for the page thumbs:

{
	"featured_image": "template=wine|basic-page, children.count=0, parent!=1",
	"bg_image": ""
}

The idea is to use different fields (eg. "featured_image") and filter them with selectors. The first matching selector will be used. In this example featured_image is used on matching pages, and bg_image elsewhere.

I may modify the syntax to something that is easier to use. If only a string is entered, it will be treated as a global field to use on all pages.

  • Like 2
Link to comment
Share on other sites

8 hours ago, tpr said:

You mean the page thumbs?

Sorry, I was on mobile, and could not spend too much time on my reply. Actually, I was talking about the thumbnail list vs the simple but compact list I requested. If I understand you correctly, we are talking about two different representation of the same list (tree). One with image thumbs, the other one is without the thumbs. Of course, you can use small top/bottom padding regardless of the presence of the thumbnail images, making the list compact no matther what. It just won't be too "compact" with the otherwise optional thumbnails, right?

Link to comment
Share on other sites

I'm afraid I'm lost somewhere in between :) I was talking about the existing page list but prepending a small thumbnails to the items, not a thumbnail-only page list (there's a module for that as I know). I don't plan to add the latter because that would require much modifications and it's not the purpose of AOS.

To make this pagelist compact with the thumbnails, I will see how usable it is with smaller thumbs but I'm not sure that would make much sense (thumbs were too small).

  • Like 2
Link to comment
Share on other sites

I have discovered an z-index issue with the Leaflet module. It concerns the breadcrumbs and headline div.

Screenshot_1.jpg

As you can see the magnifying glass on the right and and the size changer on the left side overlap.

Adding the following z-index to the breadcrumbs and headline div solves the problem:

#breadcrumbs {z-index:11}
#headline {z-index:11}

A lower index than 11 will not work.

Best regards

  • Like 1
Link to comment
Share on other sites

Thanks @Juergen (or z-index-man :)) Version 0.3.6 is uploaded which should fix it. The problem is that the leaflet field sets a z-index of 1000 so I decided to use much larger values.

@szabesz is also covered with the new "Set narrow pagelist items" to reduce row height for the main pagelist. It's Reno theme only so it can be found under the RenoTweaks submodule.

This update contains the "Pagelist thumbnails" feature. I'm sure this will have some iterations but I really like the "fieldname: selector" syntax to add thumbs, it's really flexible.

  • Like 3
Link to comment
Share on other sites

8 minutes ago, tpr said:

@szabesz is also covered with the new "Set narrow pagelist items" to reduce row height for the main pagelist. It's Reno theme only so it can be found under the RenoTweaks submodule.

Thank you very much, Sir! Double like :)

Have a good night!

  • Like 1
Link to comment
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 Robin S
      This module lets you add some custom menu items to the main admin menu, and you can set the dropdown links dynamically in a hook if needed.
      Sidenote: the module config uses some repeatable/sortable rows for the child link settings, similar to the ProFields Table interface. The data gets saved as JSON in a hidden textarea field. Might be interesting to other module developers?
      Custom Admin Menus
      Adds up to three custom menu items with optional dropdowns to the main admin menu.
      The menu items can link to admin pages, front-end pages, or pages on external websites.
      The links can be set to open in a new browser tab, and child links in the dropdown can be given an icon.
      Requires ProcessWire v3.0.178 or newer.
      Screenshots
      Example of menu items

      Module config for the menus

      Link list shown when parent menu item is not given a URL

      Advanced
      Setting child menu items dynamically
      If needed you can set the child menu items dynamically using a hook.
      Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); if($menu_number === 1) { $colours = $event->wire()->pages->findRaw('template=colour', ['title', 'url', 'page_icon']); $children = []; foreach($colours as $colour) { // Each child item should be an array with the following keys $children[] = [ 'icon' => $colour['page_icon'], 'label' => $colour['title'], 'url' => $colour['url'], 'newtab' => false, ]; } $event->return = $children; } }); Create multiple levels of flyout menus
      It's also possible to create multiple levels of flyout submenus using a hook.

      For each level a submenu can be defined in a "children" item. Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); if($menu_number === 1) { $children = [ [ 'icon' => 'adjust', 'label' => 'One', 'url' => '/one/', 'newtab' => false, ], [ 'icon' => 'anchor', 'label' => 'Two', 'url' => '/two/', 'newtab' => false, 'children' => [ [ 'icon' => 'child', 'label' => 'Red', 'url' => '/red/', 'newtab' => false, ], [ 'icon' => 'bullhorn', 'label' => 'Green', 'url' => '/green/', 'newtab' => false, 'children' => [ [ 'icon' => 'wifi', 'label' => 'Small', 'url' => '/small/', 'newtab' => true, ], [ 'icon' => 'codepen', 'label' => 'Medium', 'url' => '/medium/', 'newtab' => false, ], [ 'icon' => 'cogs', 'label' => 'Large', 'url' => '/large/', 'newtab' => false, ], ] ], [ 'icon' => 'futbol-o', 'label' => 'Blue', 'url' => '/blue/', 'newtab' => true, ], ] ], [ 'icon' => 'hand-o-left', 'label' => 'Three', 'url' => '/three/', 'newtab' => false, ], ]; $event->return = $children; } }); Showing/hiding menus according to user role
      You can determine which menu items can be seen by a role by checking the user's role in the hook.
      For example, if a user has or lacks a role you could include different child menu items in the hook return value. Or if you want to conditionally hide a custom menu altogether you can set the return value to false. Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); $user = $event->wire()->user; // For custom menu number 1... if($menu_number === 1) { // ...if user does not have some particular role... if(!$user->hasRole('foo')) { // ...do not show the menu $event->return = false; } } });  
      https://github.com/Toutouwai/CustomAdminMenus
      https://processwire.com/modules/custom-admin-menus/
    • By tcnet
      This module for ProcessWire sends a notification email for each failed login attempt. Similar modules exists already in the module directory of ProcessWire. However, this module is designed to notify, even if specified user doesn't exist.
      Settings
      The settings for this module are located in the menu Modules=>Configure=>LoginFailNotifier.
      Notification email
      Specifies the email address to which the notification emails should be sent.
        Email subject
      Specifies the subject line for the notification email.
        Post variables
      Specifies the $_POST variables to be included in the notification email. Each variable must be separated by a comma. For example: login_name,login_pass
        Server variables
      Specifies the $_SERVER variables to be included in the notification email. Each variable must be separated by a comma. For example: REMOTE_ADDR,HTTP_USER_AGENT
      Link to ProcessWire module directory:
      https://processwire.com/modules/login-fail-notifier/
      Link to github.com:
      https://github.com/techcnet/LoginFailNotifier
    • By Fokke
      ProcessWire 3.x markup module for rendering meta tags in HTML document head section. Note that this module is not a full-blown SEO solution, but rather a simple tool for rendering meta tags based on module configuration. Adding custom meta tags is also supported.
      Built-in meta tags
      The following meta tags are supported out-of-the-box:
      Document title consisting of page title and site name Character set Canonical Viewport Description Keywords Hreflang tags Open Graph og:title og:site_name og:type og:url og:description og:image og:image:width og:image:height Twitter meta tags twitter:card twitter:site twitter:creator twitter:title twitter:description twitter:image Facebook meta tags fb:app_id The full documentation with configurable options can be found here: https://github.com/Fokke-/MarkupMetadata
       
      Requirements:
      ProcessWire>=3.0.0 PHP >=7.1 Installation using Composer
      composer require fokke/markup-metadata Manual installation
      Download latest version from https://github.com/Fokke-/MarkupMetadata/archive/master.zip Extract module files to site/modules/MarkupMetadata directory.
    • By m.sieber
      ITRK-Service for ProcessWire
      Module for the automated transfer of imprint, data protection declaration and terms and conditions from IT-Recht Kanzlei to your ProcessWire installation
      What is ITRK Service for ProcessWire?
      ITRK-Service for ProcessWire is a free module for ProcessWire CMS. It provides an interface to the update service of IT-Recht Kanzlei, via which the legal texts of your online presence are automatically updated. In this way, the texts remain legally secure and warning-proof in the long term. Imprint, data protection declaration, revocation and general terms and conditions are currently supported.
      You can find our documentation (in german language) here: https://www.pupit.de/itrk-service-for-processwire/dokumentation/

      Download: https://www.pupit.de/itrk-service-for-processwire/
      Github: https://github.com/pupit-de/pwItrkServiceConnector
    • By LuisM
      Symprowire is a PHP MVC Framework based and built on Symfony using ProcessWire 3.x as DBAL and Service-Provider
      It acts as a Drop-In Replacement Module to handle the Request/Response outside the ProcessWire Admin. Even tough Symfony or any other mature MVC Framework could be intimidating at first, Symprowire tries to abstract Configuration and Symfony Internals away as much as possible to give you a quick start and lift the heavy work for you.
      The main Goal is to give an easy path to follow an MVC Approach during development with ProcessWire and open up the available eco-system.
      You can find the GitHub Repo and more Information here: https://github.com/Luis85/symprowire
      Documentation
      The Symprowire Wiki https://github.com/Luis85/symprowire/wiki How to create a simple Blog with Symprowire https://github.com/Luis85/symprowire/wiki/Symprowire-Blog-Tutorial Last Update
      16.07.2021 // RC 1 v0.6.0 centralized ProcessWire access trough out the Application by wrapping to a Service https://github.com/Luis85/symprowire/releases/tag/v0.6.0-rc-1 Requirements
      PHP ^7.4 Fresh ProcessWire ^3.0.181 with a Blank Profile Composer 2 (v1 should work, not recommended) The usual Symfony Requirements Features
      Twig Dependency Injection Monolog for Symprowire Support for .env YAML Configuration Symfony Console and Console Commands Symfony Webprofiler Full ProcessWire access inside your Controller and Services Webpack Encore support Caveats
      Symfony is no small Framework and will come with a price in terms of Memory Usage and added Overhead. To give you a taste I installed Tracy Debugger alongside to compare ProcessWire profiling with the included Symfony Webprofiler

      So in a fresh install Symprowire would atleast add another 2MB of Memory usage and around 40ms in response time, should be less in production due to the added overhead of the Webprofiler in dev env
       
×
×
  • Create New...