Jump to content
tpr

AdminOnSteroids

Recommended Posts

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

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites

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.

 

Bildschirmfoto 6.png

... or the tabs could be moved down?

Bildschirmfoto 7.png

 

  • Like 1

Share this post


Link to post
Share on other sites

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

aos_default-tabs.png

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.

Share this post


Link to post
Share on other sites
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 :-)

  • Like 1

Share this post


Link to post
Share on other sites

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 :)

  • Like 4

Share this post


Link to post
Share on other sites

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 by ceberlin
addition

Share this post


Link to post
Share on other sites
9 hours ago, ceberlin said:

Prev/Next Tabs module

Such features would be wlecome in AOS too :)

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

anybody also having this issue?

2016-08-20 17_23_26-Modules • ProcessWire • mustangs2016.dev.png

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

2016-08-20 17_25_37-Program Manager.png

i like the centered login :)

Share this post


Link to post
Share on other sites

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

  • Like 2

Share this post


Link to post
Share on other sites

Hello tpr,

here is a new z-index issue :-[

Screenshot_11.jpg

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

Share this post


Link to post
Share on other sites

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.

aos_downloadAsset-01.png

aos_downloadAsset-02.png

  • Like 2

Share this post


Link to post
Share on other sites
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 :)

Share this post


Link to post
Share on other sites

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

  • Like 2

Share this post


Link to post
Share on other sites
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.

  • Like 1

Share this post


Link to post
Share on other sites

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

  • Like 2

Share this post


Link to post
Share on other sites

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 :)

  • Like 1

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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

flicker.gif

  • Like 1

Share this post


Link to post
Share on other sites

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.

  • Like 1

Share this post


Link to post
Share on other sites

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.

 

  • Like 3

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 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-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 Process refunds and send customer notifications 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 (alpha version only available via GitHub) 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 d'Hinnisdaël
      Happy new year, everybody 🥬
      I've been sitting on this Dashboard module I made for a client and finally came around to cleaning it up and releasing it to the wider public. This is how it looks.
      ProcessWire Dashboard

      If anyone is interested in trying this out, please go ahead! I'd love to get some feedback on it. If this proves useful and survives some real-world testing, I'll add this to the module directory.
      Download
      You can find the latest release on Github.
      Documentation
      Check out the documentation to get started. This is where you'll find information about included panel types and configuration options.
      Custom Panels
      My goal was to make it really simple to create custom panels. The easiest way to do that is to use the panel type template and have it render a file in your templates folder. This might be enough for 80% of all use cases. For anything more complex (FormBuilder submissions? Comments? Live chat?), you can add new panel types by creating modules that extend the DashboardPanel base class. Check out the documentation on custom panels or take a look at the HelloWorld panel to get started. I'm happy to merge any user-created modules into the main repo if they might be useful to more than a few people.
       Disclaimer
      This is a pre-release version. Please treat it as such — don't install it on production sites. Just making sure 🍇
      Roadmap
      These are the things I'm looking to implement myself at some point. The wishlist is a lot longer, but those are the 80/20 items that I probably won't regret spending time on.
      Improve documentation & add examples ⚙️ Panel types Google Analytics ⚙️ Add new page  🔥 Drafts 🔥 At a glance / Page counter 404s  Layout options Render multiple tabs per panel panel groups with heading and spacing between ✅ panel wrappers as grid item (e.g. stacked notices) ✅ Admin themes support AdminThemeReno and AdminThemeDefault ✅ Shortcuts panel add a table layout with icon, title & summary ✅ Chart panel add default styles for common chart types ✅ load chart data from JS file (currently passed as PHP array) Collection panel support image columns ✅ add buttons: view all & add new ✅
    • By Robin S
      This module is inspired by and similar to the Template Stubs module. The author of that module has not been active in the PW community for several years now and parts of the code for that module didn't make sense to me, so I decided to create my own module. Auto Template Stubs has only been tested with PhpStorm because that is the IDE that I use.
      Auto Template Stubs
      Automatically creates stub files for templates when fields or fieldgroups are saved.
      Stub files are useful if you are using an IDE (e.g. PhpStorm) that provides code assistance - the stub files let the IDE know what fields exist in each template and what data type each field returns. Depending on your IDE's features you get benefits such as code completion for field names as you type, type inference, inspection, documentation, etc.
      Installation
      Install the Auto Template Stubs module.
      Configuration
      You can change the class name prefix setting in the module config if you like. It's good to use a class name prefix because it reduces the chance that the class name will clash with an existing class name.
      The directory path used to store the stub files is configurable.
      There is a checkbox to manually trigger the regeneration of all stub files if needed.
      Usage
      Add a line near the top of each of your template files to tell your IDE what stub class name to associate with the $page variable within the template file. For example, with the default class name prefix you would add the following line at the top of the home.php template file:
      /** @var tpl_home $page */ Now enjoy code completion, etc, in your IDE.

      Adding data types for non-core Fieldtype modules
      The module includes the data types returned by all the core Fieldtype modules. If you want to add data types returned by one or more non-core Fieldtype modules then you can hook the AutoTemplateStubs::getReturnTypes() method. For example, in /site/ready.php:
      // Add data types for some non-core Fieldtype modules $wire->addHookAfter('AutoTemplateStubs::getReturnTypes', function(HookEvent $event) { $extra_types = [ 'FieldtypeDecimal' => 'string', 'FieldtypeLeafletMapMarker' => 'LeafletMapMarker', 'FieldtypeRepeaterMatrix' => 'RepeaterMatrixPageArray', 'FieldtypeTable' => 'TableRows', ]; $event->return = $event->return + $extra_types; }); Credits
      Inspired by and much credit to the Template Stubs module by mindplay.dk.
       
      https://github.com/Toutouwai/AutoTemplateStubs
      https://modules.processwire.com/modules/auto-template-stubs/
    • By Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.60
      Composer: rockett/jumplinks
      ⚠️ NOTICE: 1.5.60 is an important security patch-release for an XSS vulnerability discovered by @phlp. It's HIGHLY RECOMMENDED that all Jumplinks users update to the latest version as soon as possible.
      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! 🙂
    • By Robin S
      Add Image URLs
      Allows images/files to be added to Image/File fields by pasting URLs.

      Usage
      Install the Add Image URLs module.
      A "Paste URLs" button will be added to all image and file fields. Use the button to show a textarea where URLs may be pasted, one per line. Images/files are added when the page is saved.
       
      https://github.com/Toutouwai/AddImageUrls
      https://modules.processwire.com/modules/add-image-urls/
×
×
  • Create New...