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 bernhard
      --- Please use RockFinder3 ---
    • By MoritzLost
      Cacheable Placeholders
      This module allows you to have pieces of dynamic content inside cached output. This aims to solve the common problem of having a mostly cacheable site, but with pieces of dynamic output here and there.  Consider this simple example, where you want to output a custom greeting to the current user:
      <h1>Good morning, <?= ucfirst($user->name) ?></h1> This snippet means you can't use the template cache (at least for logged-in users), because each user has a different name. Even if 99% of your output is static, you can only cache the pieces that you know won't include this personal greeting. A more common example would be CSRF tokens for HTML forms - those need to be unique by definition, so you can't cache the form wholesale.
      This module solves this problem by introducing cacheable placeholders - small placeholder tokens that get replaced during every request. The replacement is done inside a Page::render hook so it runs during every request, even if the response is served from the template cache. So you can use something like this:
      <h1>Good morning, {{{greeting}}}</h1> Replacement tokens are defined with a callback function that produces the appropriate output and added to the module through a simple hook:
      // site/ready.php wire()->addHookAfter('CachePlaceholders::getTokens', function (HookEvent $e) { $tokens = $e->return; $tokens['greeting'] = [ 'callback' => function (array $tokenData) { return ucfirst(wire('user')->name); } ]; $e->return = $tokens; }); Tokens can also include parameters that are parsed and passed to the callback function. There are more fully annotated examples and step-by-step instructions in the README on Github!
      Features
      A simple and fast token parser that calls the appropriate callback and runs automatically. Tokens may include multiple named or positional parameters, as well as multi-value parameters. A manual mode that allows you to replace tokens in custom pieces of cached content (useful if you're using the $cache API). Some built-in tokens for common use-cases: CSRF-Tokens, replacing values from superglobals and producing random hexadecimal strings. The token format is completely customizable, all delimiters can be changed to avoid collisions with existing tag parsers or template languages. Links
      Github Repository & documentation Module directory (pending approval) If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
    • By Craig
      I've been using Fathom Analytics for a while now and on a growing number of sites, so thought it was about time there was a PW module for it.
      WayFathomAnalytics
      WayFathomAnalytics is a group of modules which will allow you to view your Fathom Analytics dashboard in the PW admin panel and (optionally) automatically add and configure the tracking code on front-end pages.
      Links
      GitHub Readme & documentation Download Zip Modules directory Module settings screenshot What is Fathom Analytics?
      Fathom Analytics is a simple, privacy-focused website analytics tool for bloggers and businesses.

      Stop scrolling through pages of reports and collecting gobs of personal data about your visitors, both of which you probably don't need. Fathom is a simple and private website analytics platform that lets you focus on what's important: your business.
      Privacy focused Fast-loading dashboards, all data is on a single screen Easy to get what you need, no training required Unlimited email reports Private or public dashboard sharing Cookie notices not required (it doesn't use cookies or collect personal data) Displays: top content, top referrers, top goals and more
    • By daniels
      This is a lightweight alternative to other newsletter & newsletter-subscription modules.
      You can find the Module in the Modules directory and on Github
      It can subscribe, update, unsubscribe & delete a user in a list in Mailchimp with MailChimp API 3.0. It does not provide any forms or validation, so you can feel free to use your own. To protect your users, it does not save any user data in logs or sends them to an admin.
      This module fits your needs if you...
      ...use Mailchimp as your newsletter / email-automation tool ...want to let users subscribe to your newsletter on your website ...want to use your own form, validation and messages (with or without the wire forms) ...don't want any personal user data saved in any way in your ProcessWire environment (cf. EU data regulation terms) ...like to subscribe, update, unsubscribe or delete users to/from different lists ...like the Mailchimp UI for creating / sending / reviewing email campaigns *I have only tested it with PHP 7.x so far, so use on owners risk
      EDIT:
      Since 0.0.4, instructions and changelog can be found in the README only. You can find it here  🙂
      If you have questions or like to contribute, just post a reply or create an issue or pr on github, thanks!
    • By MoritzLost
      Sorry for the convoluted title. I have a problem with Process modules that define a custom page using the page key through getModuleInfo (as demonstrated in this excellent tutorial by @bernhard). Those pages are created automatically when the module is installed. The problem is that the title of the page only gets set in the current language. That's not a problem if the current language (language of the superuser who is installing the module) is the default language; if it isn't, the Process page is missing a title in the default language. This has the very awkward effect that a user using the backend in the default language (or any other language) will see an empty entry in the setup menu:

      This screenshot comes from my Cache Control module which includes a Process page. Now I realize the description sounds obscure, but for us it's a common setup: We a multiple bilingual sites where the default language is German and the second language is English. While the clients use the CMS in German, as a developer I prefer the English interface, so whenever I install a Process module I get this problem.
      As a module author, is there a way to handle this situation? I guess it would be possible to use post-installation hooks or create the pages manually, but I very much prefer the declarative approach. The page title is already translatable (through the __ function), but of course at the time of installation there is no translation, and as far as I'm aware it's not possible to ship translations with a module so they are used automatically. Could this situation be handled better in the core? I would prefer if the module installation process would always set the title of the Process page in the default language, instead of the language of the current user.
×
×
  • Create New...