Jump to content
tpr

AdminOnSteroids

Recommended Posts

Works really well TPR. Thank you for adding this feature. :) 

  • Like 1

Share this post


Link to post
Share on other sites

Wow! Works like a charme!!

The only thing I would change is the color of the bold text in the tooltipps. I dont know why but, you use #777 as color. I think the contrast between the background and the color of the bold text is not really good.

Screenshot_1.jpg

Here is your CSS part:

.description strong, .notes strong {
    color: #777;
    font-weight: 700;
}

I would use #fff for bold text too so it would be better readable.

Congratulations to this awesome module!

  • Like 3

Share this post


Link to post
Share on other sites

Thanks!

Actually it's not the module's CSS but the base (Reno) theme. My module only overwrites values, though I tried to fix this but with only partial success (on load the initial CSS styling was still visible). Now I corrected this text color issue (no version change).

  • Like 3

Share this post


Link to post
Share on other sites

What I have also discovered is a z-index issue of the tooltip icons.

Screenshot_10.jpg

As you can see the icons are always visible if you scroll the page down.

 

  • Like 1

Share this post


Link to post
Share on other sites

Thanks, I haven't noticed that (I'm using the "Compact header"). This should be fixed in v028 that is just uploaded + some small other fixes.

  • Like 2

Share this post


Link to post
Share on other sites

Hello tpr,

I am so sorry, but I found another z-index issue at the image field.

Screenshot_11.jpg

As you can see the image upload field overlap the static bar at the top. I have only discovered that with the image upload field. It seems that the static part should have a much higher z-index.

Best regards

Share this post


Link to post
Share on other sites
3 hours ago, Juergen said:

As you can see the image upload field overlap the static bar at the top.

I see but can't reproduce. Could you send a screenshot of your module settings and share your PW version and browser info?
There's a slight chance that I modified the CSS in the meantime and that's why it's not happening here.

A new version is uploaded (v029), which contains a tweak to make the module list page more compact by removing section titles and keeping only the first table header.

aos_compactModuleList.png

  • Like 1

Share this post


Link to post
Share on other sites

Hello tpr,

I use the latest Version (3.24) and I found out that this only happens if you have a special image grid setting. It is the last one which shows the inputfield for the title. If you switch to the grid views without the input field it works correctly.

Maybe this could help you to reproduce the behaviour. If not please let me know. 

  • Like 1

Share this post


Link to post
Share on other sites

Thanks, that helped. Download again and it should be fixed.

  • Like 1

Share this post


Link to post
Share on other sites

Just added a few CSS tweaks to the compact module list feature and it got really compact :)

Since clicking on the module names loads the module settings page I added a small icon next to them, and hided the Settings button. It may take some time get familiar with this but I think it makes sense.

Install and delete buttons are placed to the far right, so rows usually fit in one row now (depending on screen resolution and module descriptions). The delete button also got a reddish background color.

Edit: module main icons are moved to the right within their cells, so module names align nicely to the left, making them more readable (otherwise modules with no icons caused "ragged" column)

aos_compact-modules-1.png

Edited by tpr
new screenshot
  • Like 5

Share this post


Link to post
Share on other sites

Just uploaded v032 which features a (fake) CSS loader. This is to avoid seeing the underlying styling of the Default/Reno themes for a split second.

Share this post


Link to post
Share on other sites

Just thought I'd mention some things I have noticed. Sorry TPR!

Using ProDrafts cuts off the top title.

Screen Shot 2016-07-13 at 9.59.38 pm.png

The sticky header, or button has no padding to the right and is right up against the page if not set to the left of the title.

Screen Shot 2016-07-13 at 10.01.17 pm.png 

The compact list and fake css loader though have been very nice additions.  Keep them coming! 

 

Share this post


Link to post
Share on other sites

Thanks! I can add margin to the right but unfortunately I haven't got ProDrafts to fix the overlap issue. As I see there's an extra element under the breadcrumb that pushes things down, so here a major fix would be needed.

Share this post


Link to post
Share on other sites

I thought that would be the case, but that's ok.  Also just noticed this one also:

Repeater(repeater matrix field) field cuts some of the notes/info icon.

(This only happens if the repeater field is closed first.  Not sure if this has something to do with the 3.x to remember open closed repeaters.)

Screen Shot 2016-07-13 at 10.40.23 pm.png

Thanks tpr.

Edited by grimezy
More info added.
  • Like 1

Share this post


Link to post
Share on other sites

Nice we now moved from a plain module list (PW2.1) to sections for sake of overview, now you make it flat again with this module :) 

I think while it's nice to have all these steroids, it's something I'm trying to keep away from doing too much admin tweaking. Some of these should be considered in core and not via such an module. It's prone to errors and confusions once core admin changes stuff around. Not trying to drag you down. Just my 2 cents.

  • Like 2

Share this post


Link to post
Share on other sites

I want to add my 2 cents too. :)

@Soma: yes it maybe error prone, and yes some of these steroids should belong into the core.

In the past we have had some small modules that tweeked a single thing in the admin, fe add more button functionality for pages directly in the page tree overview, your "page is edited reminder" to avoid accidentaly leaving a page without saving, and others.

Over the time, many of this was included into the core. And I believe not all would have benn incorporated without becoming a module first.

So, besides all the good steroids stuff here, there are two things I additionally like on AdminOnSteroids:  1) that it collects many usefull parts into a single collection, avoiding to deal with 10+ small modules, and 2) to have the ability to see (and early use) what all can be possible. Ah, there are more: 3) for Ryan it can be a good way to just try out things, and, hopefully incorporate some into the core than. 4) I can decide for every single feature to en- or disable it. I even can install AOS and have the unchanged default admin theme.

So, if there is an error (CSS/JS) I simply can disable a feature or the complete module.

  • Like 7

Share this post


Link to post
Share on other sites

I haven't had the chance to know PW 2.1 so bear with me :)

Well I don't care if something should belong to the core or not. If I need a feature that I can solve relatively easily with CSS/JS to simplify my admin life, I'll do it. If it makes itself into the core I'll happily remove from the module. But it's unlikely that these feature will be part of PW within months or even years, and I need them now. Even the admin themes don't change too rapidly so I have time to fix the errors.

Apart from these it's fun to play with this :)

@grimezy download the latest from GitHub, the button and matrix repeater issues should be fixed. The latter was present in simple repeaters too and that was already covered.

  • Like 6

Share this post


Link to post
Share on other sites
58 minutes ago, horst said:

So, if there is an error (CSS/JS) I simply can disable a feature or the complete module.

Have you encountered any JS errors with AOS?

  • Like 1

Share this post


Link to post
Share on other sites
29 minutes ago, tpr said:

Have you encountered any JS errors with AOS?

No, there are no errors! It was just a thought / explanation that, even if someday there would be one, I simply can disable it. :)

  • Like 1

Share this post


Link to post
Share on other sites

I have an issue with the z-index of the UL with the id="notices". When I scroll it overlays the mainmenu as seen on screenshot. Z-Index should be lower. PW 3.0.25

2016-07-19 13_12_00-Bearbeite Seite_ admin • localhost.png

Share this post


Link to post
Share on other sites

Thanks, v034 should fix this. The default admin theme is a bit of a stepbrother because I don't use it so such bugs may come up more frequently there.

I also got rid of a z-index renumbering issue coming from sass but this doesn't mean there will be no more z-index issues :) 

There are some other CSS fixes regarding the layout for the default theme, hopefully I haven't broke anyting. The loader animation should be vertically centered too.

  • Like 3

Share this post


Link to post
Share on other sites

hi @tpr (ok now the @ is working...)

did you implement my filesort? it does show up on the checkbox but does not seem to have any effect?

2016-07-21 18_02_03-Modules • ProcessWire • mustangs2016.dev.png

2016-07-21 18_01_44-Edit Page_ Testnews • mustangs2016.dev.png

 

edit: also the textarea autosize does not work on ckeditor fields. is that intended? neither on default nor on reno theme.

edit2: it's impossible to click on links in field descriptions!2016-07-21 18_14_09-Edit Template_ blogitem • mustangs2016.dev.png

edit 3: i have this weird bug on hover buttons

hover.gif

Share this post


Link to post
Share on other sites

No, filesort is not implemented.

Autosize never worked on ckeditor, use the autogrow plugin for that, cke is a different beast :)

Double click on description icon to freeze the tooltip, then you can copy text or click on a link.

I believe the button hover issue was always there, even before AOS. I tried to solve it but haven't succeed.

  • Like 2

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
      TrelloWire
      This is a module that allows you to automatically create Trello cards for ProcessWire pages and update them when the pages are updated. This allows you to setup connected workflows. Card properties and change handling behaviour can be customized through the extensive module configuration. Every action the module performs is hookable, so you can modify when and how cards are created as much as you need to. The module also contains an API-component that makes it easy to make requests to the Trello API and build your own connected ProcessWire-Trello workflows.
      Features
      All the things the module can do for you without any custom code: Create a new card on Trello whenever a page is added or published (you can select applicable templates). Configure the target board, target list, name and description for new cards. Add default labels and checklists to the card. Update the card whenever the page is updated (optional). When the status of the card changes (published / unpublished, hidden / unhidden, trashed / restored or deleted), move the card to a different list or archive or delete it (configurable). You can extend this through hooks in many ways: Modifiy when and how cards are created. Modify the card properties (Target board & list, title, description, et c.) before they are sent to Trello. Create your own workflows by utilizing an API helper class with many convenient utility methods to access the Trello API directly. Feedback & Future Plans
      Let me know what you think! In particular:
      If you find any bugs report them here or on Github, I'll try to fix them. This module was born out of a use-case for a client project where we manage new form submissions through Trello. I'm not sure how many use-cases there are for this module. If you do use it, tell me about it! The Trello API is pretty extensive, I'll try to add some more helper methods to the TrelloWireApi class (let me know if you need anything in particular). I'll think about how the module can support different workflows that include Twig – talk to me if you have a use-case! Next steps could be a dashboard to manage pages that are connected to a Trello card, or a new section in the settings tab to manage the Trello connection. But it depends on whether there is any interest in this 🙂 Links
      Repository on Github Complete module documentation (getting started, configuration & API documentation) TrelloWire in the modules directory Module configuration

    • 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-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 bernhard
      #######################
      Please use the new RockFinder2
      #######################
      WHY?
      This module was built to fill the gap between simple $pages->find() operations and complex SQL queries.
      The problem with $pages->find() is that it loads all pages into memory and that can be a problem when querying multiple thousands of pages. Even $pages->findMany() loads all pages into memory and therefore is a lot slower than regular SQL.
      The problem with SQL on the other hand is, that the queries are quite complex to build. All fields are separate tables, some repeatable fields use multiple rows for their content that belong to only one single page, you always need to check for the page status (which is not necessary on regular find() operations and therefore nobody is used to that).
      In short: It is far too much work to efficiently and easily get an array of data based on PW pages and fields and I need that a lot for my RockGrid module to build all kinds of tabular data.

      Basic Usage

       
      Docs & Download
      https://modules.processwire.com/modules/rock-finder/
      https://github.com/BernhardBaumrock/RockFinder
       
      Changelog
      180817, v1.0.6, support for joining multiple finders 180810, v1.0.5, basic support for options fields 180528, v1.0.4, add custom select statement option 180516, change sql query method, bump version to 1.0.0 180515, multilang bugfix 180513, beta release <180513, preview/discussion took place here: https://processwire.com/talk/topic/18983-rocksqlfinder-highly-efficient-and-flexible-sql-finder-module/
    • By MoritzLost
      Process Cache Control
      This module 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) Clear the ProCache page render cache (if your site is using ProCache) 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.
      Plans for improvements
      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 CHANGELOG in the repository Screenshots


    • By Macrura
      PrevNextTabs Module
      Github: https://github.com/outflux3/PrevNextTabs
      Processwire helper modules for adding page navigation within the editor.
      Overview
      This is a very simple module that adds Previous and Next links inline with the tabs on the page editor. Hovering over the tab shows the title of the previous or next page (using the admin's built in jqueryUI tooltips.)
      Usage
      This module is typically used during development where you or your editors need to traverse through pages for the purpose of proofing, flagging and/or commenting. Rather than returning to the page tree or lister, they can navigate with these links.
      Warnings
      If you are using PW version 2.6.1 or later, the system will prevent you from leaving the page if you have unsaved edits.
      For earlier versions, to avoid accidentally losing changes made to a page that might occur if a user accidentally clicks on one of these, make sure to have the Form Save Reminder module installed.
      http://modules.processwire.com/modules/prev-next-tabs/
×
×
  • Create New...