Jump to content
tpr

AdminOnSteroids

Recommended Posts

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

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

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 adrian
      Tracy Debugger for ProcessWire
      The ultimate “swiss army knife” debugging and development tool for the ProcessWire CMF/CMS

       
      Integrates and extends Nette's Tracy debugging tool and adds 35+ custom tools designed for effective ProcessWire debugging and lightning fast development
      The most comprehensive set of instructions and examples is available at: https://adrianbj.github.io/TracyDebugger
      Modules Directory: http://modules.processwire.com/modules/tracy-debugger/
      Github: https://github.com/adrianbj/TracyDebugger
      A big thanks to @tpr for introducing me to Tracy and for the idea for this module and for significant feedback, testing, and feature suggestions.
    • By adrian
      This module allows you to automatically rename file (including image) uploads according to a configurable format
      This module lets you define as many rules as you need to determine how uploaded files will be named and you can have different rules for different pages, templates, fields, and file extensions, or one rule for all uploads. Renaming works for files uploaded via the admin interface and also via the API, including images added from remote URLs.   Github: https://github.com/adrianbj/CustomUploadNames
      Modules Directory: http://modules.processwire.com/modules/process-custom-upload-names/
      Renaming Rules
      The module config allows you to set an unlimited number of Rename Rules. You can define rules to specific fields, templates, pages, and file extensions. If a rule option is left blank, the rule with be applied to all fields/templates/pages/extensions. Leave Filename Format blank to prevent renaming for a specific field/template/page combo, overriding a more general rule. Rules are processed in order, so put more specific rules before more general ones. You can drag to change the order of rules as needed. The following variables can be used in the filename format: $page, $template, $field, and $file. For some of these (eg. $field->description), if they haven't been filled out and saved prior to uploading the image, renaming won't occur on upload, but will happen on page save (could be an issue if image has already been inserted into RTE/HTML field before page save). Some examples: $page->title mysite-{$template->name}-images $field->label $file->description {$page->name}-{$file->filesize}-kb prefix-[Y-m-d_H-i-s]-suffix (anything inside square brackets is is considered to be a PHP date format for the current date/time) randstring[n] (where n is the number of characters you want in the string) ### (custom number mask, eg. 001 if more than one image with same name on a page. This is an enhanced version of the automatic addition of numbers if required) If 'Rename on Save' is checked files will be renamed again each time a page is saved (admin or front-end via API). WARNING: this setting will break any direct links to the old filename, which is particularly relevant for images inserted into RTE/HTML fields. The Filename Format can be defined using plain text and PW $page variable, for example: mysite-{$page->path} You can preserve the uploaded filename for certain rules. This will allow you to set a general renaming rule for your entire site, but then add a rule for a specific page/template/field that does not rename the uploaded file. Just simply build the rule, but leave the Filename Format field empty. You can specify an optional character limit (to nearest whole word) for the length of the filename - useful if you are using $page->path, $path->name etc and have very long page names - eg. news articles, publication titles etc. NOTE - if you are using ProcessWire's webp features, be sure to use the useSrcExt because if you have jpg and png files on the same page and your rename rules result in the same name, you need to maintain the src extension so they are kept as separate files.
      $config->webpOptions = array(     'useSrcExt' => false, // Use source file extension in webp filename? (file.jpg.webp rather than file.webp) ); Acknowledgments
      The module config settings make use of code from Pete's EmailToPage module and the renaming function is based on this code from Ryan: http://processwire.com/talk/topic/3299-ability-to-define-convention-for-image-and-file-upload-names/?p=32623 (also see this post for his thoughts on file renaming and why it is the lazy way out - worth a read before deciding to use this module). 
       
       
      NOTE:
      This should not be needed on most sites, but I work with lots of sites that host PDFs and photos/vectors that are available for download and I have always renamed the files on upload because clients will often upload files with horrible meaningless filenames like:
      Final ReportV6 web version for John Feb 23.PDF

    • By Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.56
      Composer: rockett/jumplinks
      Jumplinks is an enhanced version of the original ProcessRedirects by Antti Peisa.
      The Process module manages your permanent and temporary redirects (we'll call these "jumplinks" from now on, unless in reference to redirects from another module), useful for when you're migrating over to ProcessWire from another system/platform. Each jumplink supports wildcards, shortening the time needed to create them.
      Unlike similar modules for other platforms, wildcards in Jumplinks are much easier to work with, as Regular Expressions are not fully exposed. Instead, parameters wrapped in curly braces are used - these are described in the documentation.
      Under Development: 2.0, to be powered by FastRoute
      As of version 1.5.0, Jumplinks requires at least ProcessWire 2.6.1 to run.
      View on GitLab
      Download via the Modules Directory
      Read the docs
      Features
      The most prominent features include:
      Basic jumplinks (from one fixed route to another) Parameter-based wildcards with "Smart" equivalents Mapping Collections (for converting ID-based routes to their named-equivalents without the need to create multiple jumplinks) Destination Selectors (for finding and redirecting to pages containing legacy location information) Timed Activation (activate and/or deactivate jumplinks at specific times) 404-Monitor (for creating jumplinks based on 404 hits) Additionally, the following features may come in handy:
      Stale jumplink management Legacy domain support for slow migrations An importer (from CSV or ProcessRedirects) Feedback & Feature Requests
      I’d love to know what you think of this module. Please provide some feedback on the module as a whole, or even regarding smaller things that make it whole. Also, please feel free to submit feature requests and their use-cases.
      Note: Features requested so far have been added to the to-do list, and will be added to 2.0, and not the current dev/master branches.
      Open Source

      Jumplinks is an open-source project, and is free to use. In fact, Jumplinks will always be open-source, and will always remain free to use. Forever. If you would like to support the development of Jumplinks, please consider making a small donation via PayPal.
      Enjoy! :)
×
×
  • Create New...