Jump to content
tpr

AdminOnSteroids

Recommended Posts

Quote

html.pListShowActions .content .PageList .PageListItem { width: 100%; }

Thank you, that helped.

Quote

I recommend using Reno or Uikit theme

Unfortunately I love the default theme...

  • Like 1

Share this post


Link to post
Share on other sites

Been meaning to report this for a while. When the ASM search box option is enabled, the width of the dropdown is too narrow and look item titles wrap which looks ugly and confusing. I am seeing this in the UikIt theme - not sure about the others.

Thanks for taking a look!

Share this post


Link to post
Share on other sites

Another one for you:

On the Input tab of a Page Reference field with an AsmSelect inputfield, choose custom for the label field. This enables the "Custom page label format" field, but see how it's below the "Max Limit of Items" option. On UikIt with the newish "percentage" inputfield column widths option.

image.thumb.png.be0f2f810d2329a6f10a08c2ce977938.png

Share this post


Link to post
Share on other sites

@adrian Thanks, I've fixed these. The uikit field with issue is solved by adding the fields (max limit and asm placeholder) after the Required field.

@ottogal I wasn't able to find a CSS-only solution to the sticky menu + jump link issue you mentioned. Surely there's one but I've spent too much time on it without success so I let it go instead. I could add JS but that doesn't appeal to me.

There's a new productivity tweak for the Delete and Trash pagelist actions: if ctrl key is pressed you can skip the confirmation step. I found it very handy to quickly get rid of test pages. (on the Trash action I mean the one added by AOS that is available for non-superusers).

I'll release the update soon.

  • Like 3

Share this post


Link to post
Share on other sites
On 6/2/2018 at 4:21 AM, tpr said:

There's a new productivity tweak for the Delete and Trash pagelist actions

Speaking of deleting pages, what do you think about the idea I raised a while back...

Sometimes when testing you want to permanently delete a page after you have created or edited it, so it would be handy to be able to do that from the Delete tab rather than going back to the tree. Instead of another checkbox inside the "Move to Trash" inputfield like I showed in my earlier suggestion (I don't think it's even possible to do that with the forms API) it would be better to have a separate "Delete permanently" inputfield added to the Delete tab.

  • Like 1

Share this post


Link to post
Share on other sites

That's a great idea, thanks for the reminder, I'll add soon. 

  • Like 1

Share this post


Link to post
Share on other sites

1.9.5 is uploaded. I've disabled the FileCompiler because on Win localhost it was very slow, so if you have issues try to refresh the module cache.

Changelog:

- fix inline pagelist items if "Always show pagelist actions" was checked (reported by ottogal)
- Delete and Trash action (non-superusers): skip confirmation if ctrl key is pressed
- new Skip Trash? checkbox on page edit Delete tab (SuperUsers only, requested by Robin S)
- fix NavItems causing JS error on "Find Files to Translate" page Search box
- hotkey save: do not add blocking overlay until html5 required attribute requirements are not resolved (reported by Robin S, #95)
- asmSelect searchbox: allow wider dropdown
- AdminThemeUikit, percentage-based widths ON: move AsmSelect placeholder and maxlimit fields after Required field to avoid layout issues
- add namespace and FileCompiler=0 to bypass PW's FileCompiler (slow compile on Win localhost, may need modules refresh)

 

  • Like 5

Share this post


Link to post
Share on other sites
On 6/5/2018 at 8:39 AM, tpr said:

- new Skip Trash? checkbox on page edit Delete tab (SuperUsers only, requested by Robin S)

Thanks for adding this feature!

It might be good (just to avoid any confusion) to exclude the skip trash option on the delete tab of ProcessUser because the deletion there is permanent by default.

2018-06-11_113934.png.a1e0560e0af5882b18fd5547ffdd7818.png

  • Like 2

Share this post


Link to post
Share on other sites

Thanks, fixed in v197. There are other places where there's no need to add but thankfully we have $page->trashable().

  • Like 2

Share this post


Link to post
Share on other sites

When I mentioned earlier that I may decide to create to create a new admin theme from aos many of you liked the idea. Yesterday I tried it out and I see how easy it would be to port some features without hacks, and removing the extra code needed to support the 3 major admin themes. 

So if decide to rewrite that would mean a faster and leaner module that is easier to maintain, but at the cost of dropping support for the default and reno themes. Plus as it would be forked from the uikit theme, I would have to constantly adjust it when the original theme is updated.

So what do you think about it? 

Share this post


Link to post
Share on other sites
10 hours ago, tpr said:

So what do you think about it? 

I think several AOS features need to be in the core 🙂

Seriously though, if we could get the most used features in the core, then perhaps the lesser used ones could remain in a trimmed down AOS. I think I'd rather see a module that works on top of a core theme, rather than you creating a separate theme that misses out on new features that Ryan adds until you have a chance to add them to your version of the theme. Does that make sense?

I don't think you should being trying to maintain support for multiple themes though - I think going forward PW needs one solid flexible theme which can be restyled via CSS and functionality tweaked by hooks and js overrides. I think having multiple themes with different codebases just makes things difficult for Ryan because he often has to add new functionality to multiple themes - this is why I always stick with his default, which in my mind is UiKit these days. Anyway, I am a little OT now, but hopefully my ramblings make sense.

  • Like 3

Share this post


Link to post
Share on other sites
17 hours ago, tpr said:

So what do you think about it? 

I agree with Adrian - in the future you might get too busy or just want to take a break from developing AOS and then users wouldn't be able to get new features or bug fixes that Ryan applies to the core admin theme.

I also think it might turn out to be quite a hassle for you to apply core admin theme changes to your custom theme, because once the methods have been modified you won't be able to see changes easily via a simple diff. You'd have to monitor the core diffs instead and then manually hunt through your custom methods to find the equivalent locations.

But once AdminThemeUikit has been the default admin theme for some period of time then I think it would be quite reasonable to say that AOS requires AdminThemeUikit and doesn't support the older themes.

  • Like 3

Share this post


Link to post
Share on other sites

Ok, thanks for your opinions. I'll leave AOS as it is, and when things start going out of control it will support only one admin theme.

  • Like 6

Share this post


Link to post
Share on other sites
On 6/30/2018 at 9:32 PM, adrian said:

I think several AOS features need to be in the core 🙂

Seriously though, if we could get the most used features in the core, then perhaps the lesser used ones could remain in a trimmed down AOS. I think I'd rather see a module that works on top of a core theme, rather than you creating a separate theme that misses out on new features that Ryan adds until you have a chance to add them to your version of the theme. Does that make sense?

I don't think you should being trying to maintain support for multiple themes though - I think going forward PW needs one solid flexible theme which can be restyled via CSS and functionality tweaked by hooks and js overrides. I think having multiple themes with different codebases just makes things difficult for Ryan because he often has to add new functionality to multiple themes - this is why I always stick with his default, which in my mind is UiKit these days. Anyway, I am a little OT now, but hopefully my ramblings make sense.

I exactly think the same as Adrian.

Share this post


Link to post
Share on other sites

@tpr, I have two questions, but don't bear with me, If I just have overseen the answers. 🙂

1) is there a shortkey (like ctrl+s) for "Save and Add New" available, or is it possible to add this as new feature?

2) Is there a way, (also a none public one*), to get the configuration exported out of one installation and imported into another one?

* means, I'm also fine with it, to copy/paste parts from/to sql-dumps.

 

Share this post


Link to post
Share on other sites

Currently there's no such hotkey. I've tried it earlier without luck but surely there's a way. 

You can copy settings.php from one install to another. Check Save settings checkbox in the bottom of config and save the module. Then on the other site check the same checkbox and save. Then uninstall aos, put settings.php to aos dir and install.

Share this post


Link to post
Share on other sites

When I enable AOS and try to move files/images, this happens (incognito mode, no options selected, just enabled module, no js errors):

 

aos.gif

Disabling html.aos{min-width:100vw;overflow-x:hidden} helps. 

Share this post


Link to post
Share on other sites

@matjazp Thanks, I've fixed that (came to the same solution without reading yours first :))

In v1.9.9 there is a tweak to add counters to asmSelects (for Page Reference and Options fields):

asmCounter.gif.41f16240f67a11f21ef898ec6a2f49b4.gif

  • Like 4

Share this post


Link to post
Share on other sites

Hi @tpr - as always thanks for this module. I wanted to add a feature request, which is to make the case changer something that could be used on other text fields (not sure how feasible that is); using that one a lot and is really helpful; i hacked my own 'other field' usage for the moment.. (using AdminCustomFiles)

  • Like 1

Share this post


Link to post
Share on other sites

Interesting, I use it very rarely. I remember using it only once when I copied many badly formatted articles with random title cases, and it was a great help.

I've modified this feature so it works now on text(language) fields and file/image description fields as well, even after uploading new items. Plus it works with ajax loaded fields and repeaters too. It's also new that on case change an input change is also triggered so you'll get a confirmation alert to save on leaving the page. I've also fixed some positioning issues, eg with expanded language tabs.

I'll upload the new version tomorrow if everything goes well.

  • Like 5

Share this post


Link to post
Share on other sites

whoah that is super amazing! Thanks – yeah i have 2 sites with random capitalizations of words in a certain field and am case changing them all... sometimes editors use all caps for things..

  • Like 1

Share this post


Link to post
Share on other sites

All set, please try. I will check if I can add the case toggle to Batch Child Editor's page title field too, that would also come handy. If you have other special fields in mind to support, please tell.

  • Like 1

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 gebeer
      I am happy to present my new fieldtype FieldtypeImageFromPage. It is made up of 2 modules:
      Fieldtype Image Reference From Another Page is a Fieldtype that stores a reference to a single image from another page. The image can be selected with the associated Inputfield.
      Inputfield Select Image From Page is an Inputfield to select a single image from images on a predefined page and it's children.
      And there also is a helper module that takes care of cleanup tasks.
      This module evolved out of a discussion about my other Module FieldtypeImagePicker.  It caters for use cases where a set of images is being reused multiple times across a site. With this fieldtype these images can be administered through a chosen page. All images uploaded to that page will be available in the inputfield.
      When to use ?
      Let editors choose an image from a set of images that is being used site-wide. Ideal for images that are being re-used across the site.
      Suited for images that are used on multiple pages throughout the site (e.g. icons).
      Other than the native ProcessWire images field, the images here are not stored per page. Only references to images on another page are stored. This has several advantages:
      one central place to organize images when images change, you only have to update them in one place. All references will be updated, too. (Provided the name of the image that has changed stays the same) Features
      Images can be manipulated like native ProcessWire images (resizing, cropping etc.) Image names are fully searchable through the API Accidental image deletion is prevented. When you want to delete an image from one of the pages that hold your site-wide images, the module searches all pages that use that image. If any page contains a reference to the image you are trying to delete, deletion will be prevented. You will get an error message to help you edit those pages and remove references there before you can finally delete the image. How to install and setup
      Download and install this module like any other modules in ProcessWire Create a page in the page tree that will hold your images. This page's template must have an images field Upload some images to the page you created in step 2 Create a new field. As type choose 'Image Reference From Another Page'. Save the field. In 'Details' Tab of the field choose the page you created in step 2 Click Save button Choose the images field name for the field that holds your images (on page template from step 2) Click Save button again Choose whether you want to include child pages of page from step 2 to supply images Add the field to any template You are now ready to use the field View of the inputfield on the page edit screen:

      View of the field settings

      The module can be installed from this github repo. Some more info in the README there, too.
      In my tests it was fairly stable. After receiving your valued feedback, I will eventually add it to the modules directory.
      My ideas for further improvement:
      - add ajax loading of thumbnails
      Happy to hear your feedback!
       
    • By gebeer
      Although the PW backend is really intuitive, ever so often my clients need some assistance. Be it they are not so tech savvy or they are not working in the backend often.
      For those cases it is nice to make some help videos available to editors. This is what this module does.
      ProcessHelpVideos Module
      A Process module to display help videos for the ProcessWire CMS. It can be used to make help videos (screencasts) available to content editors.
      This module adds a 'Help Videos" section to the ProcessWire backend. The help videos are accessible through an automatically created page in the Admin page tree. You can add your help videos as pages in the page tree. The module adds a hidden page to the page tree that acts as parent page for the help video pages. All necessary fields and templates will be installed automatically. If there are already a CKEditor field and/or a file field for mp4 files installed in the system, the module will use those. Otherwise it will create the necessary fields. Also the necessary templates for the parent help videos page and it's children are created on module install. The module installs a permission process-helpvideos. Every user role that should have access to the help video section, needs this permission. I use the help video approach on quite a few production sites. It is stable so far and well received by site owners/editors. Up until now I installed required fields, templates and pages manually and then added the module. Now I added all this logic to the install method of the module and it should be ready to share.
      The module and further description on how to use it is available on github: https://github.com/gebeer/ProcessHelpVideos
      If you like to give it a try, I am happy to receive your comments/suggestions here.
    • By Robin S
      A module created in response to the topic here:
      Page List Select Multiple Quickly
      Modifies PageListSelectMultiple to allow you to select multiple pages without the tree closing every time you select a page.
      The screencast says it all:

       
      https://github.com/Toutouwai/PageListSelectMultipleQuickly
      https://modules.processwire.com/modules/page-list-select-multiple-quickly/
    • By gebeer
      Hello all,
      sharing my new module FieldtypeImagePicker. It provides a configurable input field for choosing any type of image from a predefined folder.
      The need for it came up because a client had a custom SVG icon set and I wanted the editors to be able to choose an icon in the page editor.
      It can also be used to offer a choice of images that are used site-wide without having to upload them to individual pages.
      There are no image manipulation methods like with the native PW image field.
      Module and full description can be found on github https://github.com/gebeer/FieldtypeImagePicker
      Kudos to @Martijn Geerts. I used his module FieldTypeSelectFile as a base to build upon.
      Here's how the input field looks like in the page editor:

      Hope it can be of use to someone.
      If you like to give it a try, I'm happy to hear your comments or suggestions for improvement. Eventually this will go in the module directory soon, too.
    • By bernhard
      @Sergio asked about the pdf creation process in the showcase thread about my 360° feedback/survey tool and so I went ahead and set my little pdf helper module to public.
      Description from PW Weekly:
       
      Modules Directory: https://modules.processwire.com/modules/rock-pdf/
      Download & Docs: https://github.com/BernhardBaumrock/RockPDF
       
      You can combine it easily with RockReplacer: 
      See also a little showcase of the RockPdf module in this thread:
       
×
×
  • Create New...