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

@tpr  Thank you for looking into it. It's not such a big issue to waste time on it.

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

Yep, working great, thanks again!

  • Like 1

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...