Module AdminOnSteroids

[tpr]

The default theme wouldn't be nicer even if it had such login page Do you need that?

[ceberlin]

Quote

The default theme wouldn't be nicer even if it had such login page Do you need that?

Actually I find the default admin-page with the multi-hierarchy popup submenus a little bit quicker to use.
So I leave the default for the admins and use the Reno theme (with full beauty power) for the editors.

But with the AdminOnSteroids is getting better every day, that view might change.

b.t.w.  I wonder why ASMtweak "move delete button to the left" is the default setting. The trash is now very close to the dragging handle, where selections can get removed easily inadvertently. That can pass unnoticed if ASM lists are very long, I think.

[ceberlin]

I am using the default theme and want to send a small feedback.

a) if I select "sticky header" the tabs have not background any more (they float freely). I thought they where easier to read before. Why not having the background from the sticky header also there (as it was before) or a lighter variant of the background?

Or a "pills" menu design could look fancy there - opposite to tabs they look nice when floating.

b) I find the color and  place for the description and hints tooltip hard to find, but I want editors to take that information seriously. I switched that feature of but wanted to send a feedback anyway.

 

... or the tabs could be moved down?

 

[tpr]

Thanks for the feedback! I don't see the issue with tabs, they doesn't have the gap at the bottom here:

Are you sure it's not cache? I checked with Chrome-Firefox too.

As for the tabs background, AOS doesn't "know" the colors of the theme, it just fixes things here or there with an additional CSS. So making bigger adjustments that would require bigger changes would be too error-prone (like making pills from tabs). The only colors I use is white and (shades of) black, and I use "inherit" where it's suitable. Otherwise theme colors would go out of control, especially if one sets a different theme color set (at the theme's module settings).

AsmTweaks delete icon: well I haven't thought of this before but it makes sense. I have never deleted an asmField accidentally, and probably never moved any by dragging at the "drag" icon, I usually start somewhere in the middle  Anyways, I've removed it from the default settings. Sometimes it's hard to decide which way to go: support power users or stay on the safer side

I agree that tooltips/description icons are hard to find this way, but I couldn't find a better placement, and it's for power users so they usually doesn't need them. That's why it has an option to disable for non-superusers.

[matjazp]

4 hours ago, tpr said:

The default theme wouldn't be nicer even if it had such login page Do you need that?

It would

[tpr]

Actually you're right  Just tweaked AOS so both themes will have centered login. Say hello to the second checkbox in AOS for the default theme

Edit: download v050 to log in centered

[ceberlin]

that's interesting why I see the default admin page differently.

OK, I see, the gap is coming from the "Prev/Next Tabs module (which is normally another of those cool admin additions). Those "prev"/"next" tabs have a css float-right, which is causing the gap here.

The gap goes away if the UL (tabs container) has overflow hidden.

Edited August 19, 2016 by ceberlin
addition

[szabesz]

9 hours ago, ceberlin said:

Prev/Next Tabs module

Such features would be wlecome in AOS too

[tpr]

Thanks for figuring this out @ceberlin! I've set overflow: hidden as you suggested, haven't found a better way. This will be included in the next update.

@szabesz

I thought adding such feature too but I wouldn't like to re-create existing modules, especially if I don't have something in mind to improve. In case of @bernhard's Pagelist unselect module I had some UI additions and a "restore" feature, that's why I thought it would deserve a chance. In this case (PrevNextTabs) I thought adding a big right-left sticky arrows (like in sliders) but I'm not sure this would be better than the existing module. Anyway, if you have a better idea where should these prev-next links go, please share.

[bernhard]

anybody also having this issue?

i think the logo should also be centered. what do you think?

i like the centered login

[tpr]

@bernhard thanks, I've fixed the submenu gap in the main nav.

I also managed to fix the "hoverSaveDropdown" issue (flicker on hover). It's only CSS and I have to test a little more but it's promising. The solution is to hide the "dropdown" part of the button and add the down arrow with :after. Plus I had to add pointer-events: none to the span inside the buttons as they also caused flickering. 

I underestimated this issue because it wasn't as noticable in the Reno theme as in the default. Now it seems fine in both of them.

As for the centered logo in the login page: I'm not sure about it. I like that it sits in the corner but if there are others who vote for it, then let it be.

[Juergen]

Hello tpr,

here is a new z-index issue

On th right side - the dropdown of the usermenu will be overlapped by the PW messages. Not a big problem. You can click them away, but if you have time....

Data: PW 3.0.30, Reno Theme, AdminOnSteroids 0.5.1

Best regards from the z-index man

[tpr]

Thanks @Juergen, this should be fixed in v052.

There's a new feature to FileFieldTweaks (named FileFieldToolbar before v052) that allows downloading assets - images or files. To keep things simple I've used the "download" HTML5 attribute which doesn't work in IE, at least in IE11. I don't plan to fix this because the download link will open in a new window if it's unsupported so it's still usable.

[bernhard]

On 20.8.2016 at 10:26 PM, tpr said:

As for the centered logo in the login page: I'm not sure about it. I like that it sits in the corner but if there are others who vote for it, then let it be.

then i vote for a checkbox: "center logo on login-page"

just checked the new version and the fixes seem to work, thank you

[ceberlin]

Maybe obvious, but I just realized that a checkbox field without a headline does not show it's convenient field-edit popups.

[tpr]

5 hours ago, ceberlin said:

Maybe obvious, but I just realized that a checkbox field without a headline does not show it's convenient field-edit popups.

Thanks, good spot. The label in this case is hidden so the tooltip won't be shown (though it's already there). I'll find a way to fix.

@bernhard

Ok, I'll see - I think the checkbox would be too much in this case.

[tpr]

v053 fixes the issue with label-less checkboxes not having field edit tooltips (thanks @ceberlin!)

[bernhard]

hi tpr,

maybe if you find the time it would be awesome if you could fix/report/pull request the issue with the flickering dropdowns in admin as well as you just fixed that at buttons. maybe it's the same issue?

although i think that should be considered to be a bug and should not be something you need steroids for... maybe you can make an issue on github and talk to ryan what is the reason for it?

thank you

[tpr]

I may not understand this entirely - now the admin have button dropdowns that are shown on click, not on hover, and they don't seem to flicker here.
Or do you talk about other dropdowns?

The current fix in AOS is only a workaround and not really applicable elsewhere.

[bernhard]

sorry for being unclear i'm talking of the menu dropdowns. they flicker when entering with the mouse from the bottom:

[tpr]

I may found the culprit: the top positon of the dropdown is 46.5px. It's calculated by JS, but I guess it's safe to hardcode as 47px. Try adding this with devtools and see if it helps:

.topnav.ui-menu.dropdown-menu {
	top: 47px !important;
}

Works here in Chrome. In Firefox I couldn't see the flicker at all. In Chrome I see it very rarely, but if you zoom out the page it occurs more often.

[bernhard]

works! may you add an issue on github?

[tpr]

Done!

[bernhard]

found a little display glitch on collapsed fields (standard theme pw3):

[tpr]

Thanks, I haven't notice this because I have the ToolTips submodule always ON and that sets overflow: visible on the element. This will be fixed in the next release, which will be released a bit later because I have modified how HTML classes are added to the page. Now this happens entirely in the backend and not with JavaScript, which has several clear benefits, eg. much less DOM modification and because classes are present immediately, there's no need for the loader. I kinda liked the loader though but without it the admin feels faster. I have to check all settings again to see if everything is in place.

I'm also experimenting with a feature that allows selecting pages and add them to the sidebar/top nav. So far so good, I took the simplest route that requires a bit of JavaScript but I think it's OK in an admin. Otherwise I would have to add/remove pages on module install/uninstall but I wouldn't really like that way.