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

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

2016-08-27 12_39_00-Edit Page_ Test mit Handy • mustangs2016.dev.png

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

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 David Karich
      ProcessWire InputfieldRepeaterMatrixDuplicate
      Thanks to the great ProModule "RepeaterMatrix" I have the possibility to create complex repeater items. With it I have created a quite powerful page builder. Many different content modules, with many more possible design options. The RepeaterMatrix module supports the cloning of items, but only within the same page. Now I often have the case that very design-intensive pages and items are created. If you want to use a content module on a different page (e.g. in the same design), you have to rebuild each item manually every time.
      This module extends the commercial ProModule "RepeaterMatrix" by the function to duplicate repeater items from one page to another page. The condition is that the target field is the same matrix field from which the item is duplicated. This module is currently understood as proof of concept. There are a few limitations that need to be considered. The intention of the module is that this functionality is integrated into the core of RepeaterMatrix and does not require an extra module.
      Check out the screencast
      What the module can do
      Duplicate multible repeater items from one page to another No matter how complex the item is Full support for file and image fields Multilingual support Support of Min and Max settings Live synchronization of clipboard between multiple browser tabs. Copy an item and simply switch the browser tab to the target page and you will immediately see the past button Support of multiple RepeaterMatrix fields on one page Configurable which roles and fields are excluded Configurable dialogs for copy and paste Duplicated items are automatically pasted to the end of the target field and set to hidden status so that changes are not directly published Automatic clipboard update when other items are picked Automatically removes old clipboard data if it is not pasted within 6 hours Delete clipboard itself by clicking the selected item again Benefit: unbelievably fast workflow and content replication What the module can't do
      Before an item can be duplicated in its current version, the source page must be saved. This means that if you make changes to an item and copy this, the old saved state will be duplicated Dynamic loading is currently not possible. Means no AJAX. When pasting, the target page is saved completely No support for nested repeater items. Currently only first level items can be duplicated. Means a repeater field in a repeater field cannot be duplicated. Workaround: simply duplicate the parent item Dynamic reloading and adding of repeater items cannot be registered. Several interfaces and events from the core are missing. The initialization occurs only once after the page load event Changelog
      2.0.0
      Feature: Copy multiple items at once! The fundament for copying multiple items was created by @Autofahrn - THX! Feature: Optionally you can disable the copy and/or paste dialog Bug fix: A fix suggestion when additional and normal repeater fields are present was contributed by @joshua - THX! 1.0.4
      Bug fix: Various bug fixes and improvements in live synchronization Bug fix: Items are no longer inserted when the normal save button is clicked. Only when the past button is explicitly clicked Feature: Support of multiple repeater fields in one page Feature: Support of repeater Min/Max settings Feature: Configurable roles and fields Enhancement: Improved clipboard management Enhancement: Documentation improvement Enhancement: Corrected few typos #1 1.0.3
      Feature: Live synchronization Enhancement: Load the module only in the backend Enhancement: Documentation improvement 1.0.2
      Bug fix: Various bug fixes and improvements in JS functions Enhancement: Documentation improvement Enhancement: Corrected few typos 1.0.1
      Bug fix: Various bug fixes and improvements in the duplication process 1.0.0
      Initial release Support this module
      If this module is useful for you, I am very thankful for your small donation: Donate 5,- Euro (via PayPal – or an amount of your choice. Thank you!)
      Download this module (Version 2.0.0)
      > Github: https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate
      > PW module directory: https://modules.processwire.com/modules/inputfield-repeater-matrix-duplicate/
      > Old stable version (1.0.4): https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate/releases/tag/1.0.4
    • By Robin S
      A new module that hasn't had a lot of testing yet. Please do your own testing before deploying on any production website.
      Custom Paths
      Allows any page to have a custom path/URL.
      Note: Custom Paths is incompatible with the core LanguageSupportPageNames module. I have no experience working with LanguageSupportPageNames or multi-language sites in general so I'm not in a position to work out if a fix is possible. If anyone with multi-language experience can contribute a fix it would be much appreciated!
      Screenshot

      Usage
      The module creates a field named custom_path on install. Add the custom_path field to the template of any page you want to set a custom path for. Whatever path is entered into this field determines the path and URL of the page ($page->path and $page->url). Page numbers and URL segments are supported if these are enabled for the template, and previous custom paths are managed by PagePathHistory if that module is installed.
      The custom_path field appears on the Settings tab in Page Edit by default but there is an option in the module configuration to disable this if you want to position the field among the other template fields.
      If the custom_path field is populated for a page it should be a path that is relative to the site root and that starts with a forward slash. The module prevents the same custom path being set for more than one page.
      The custom_path value takes precedence over any ProcessWire path. You can even override the Home page by setting a custom path of "/" for a page.
      It is highly recommended to set access controls on the custom_path field so that only privileged roles can edit it: superuser-only is recommended.
      It is up to the user to set and maintain suitable custom paths for any pages where the module is in use. Make sure your custom paths are compatible with ProcessWire's $config and .htaccess settings, and if you are basing the custom path on the names of parent pages you will probably want to have a strategy for updating custom paths if parent pages are renamed or moved.
      Example hooks to Pages::saveReady
      You might want to use a Pages::saveReady hook to automatically set the custom path for some pages. Below are a couple of examples.
      1. In this example the start of the custom path is fixed but the end of the path will update dynamically according to the name of the page:
      $pages->addHookAfter('saveReady', function(HookEvent $event) { $page = $event->arguments(0); if($page->template == 'my_template') { $page->custom_path = "/some-custom/path-segments/$page->name/"; } }); 2. The Custom Paths module adds a new Page::realPath method/property that can be used to get the "real" ProcessWire path to a page that might have a custom path set. In this example the custom path for news items is derived from the real ProcessWire path but a parent named "news-items" is removed:
      $pages->addHookAfter('saveReady', function(HookEvent $event) { $page = $event->arguments(0); if($page->template == 'news_item') { $page->custom_path = str_replace('/news-items/', '/', $page->realPath); } }); Caveats
      The custom paths will be used automatically for links created in CKEditor fields, but if you have the "link abstraction" option enabled for CKEditor fields (Details > Markup/HTML (Content Type) > HTML Options) then you will see notices from MarkupQA warning you that it is unable to resolve the links.
      Installation
      Install the Custom Paths module.
      Uninstallation
      The custom_path field is not automatically deleted when the module is uninstalled. You can delete it manually if the field is no longer needed.
       
      https://github.com/Toutouwai/CustomPaths
      https://modules.processwire.com/modules/custom-paths/
    • By teppo
      Hey folks!
      I'm happy to finally introduce a project I've been working on for quite a while now: it's called Wireframe, and it is an output framework for ProcessWire.
      Note that I'm posting this in the module development area, maily because this project is still in rather early stage. I've built a couple of sites with it myself, and parts of the codebase have been powering some pretty big and complex sites for many years now, but this should still be considered a soft launch 🙂
      --
      Long story short, Wireframe is a module that provides the "backbone" for building sites (and apps) with ProcessWire using an MVC (or perhaps MVVM... one of those three or four letter acronyms anyway) inspired methodology. You could say that it's an output strategy, but I prefer the term "output framework", since in my mind the word "strategy" means something less tangible. A way of doing things, rather than a tool that actually does things.
      Wireframe (the module) provides a basic implementation for some familiar MVC concepts, such as Controllers and a View layer – the latter of which consists of layouts, partials, and template-specific views. There's no "model" layer, since in this context ProcessWire is the model. As a module Wireframe is actually quite simple – not even nearly the biggest one I've built – but there's still quite a bit of stuff to "get", so I've put together a demo & documentation site for it at https://wireframe-framework.com/.
      In addition to the core module, I'm also working on a couple of site profiles based on it. My current idea is actually to keep the module very light-weight, and implement most of the "opinionated" stuff in site profiles and/or companion modules. For an example MarkupMenu (which I released a while ago) was developed as one of those "companion modules" when I needed a menu module to use on the site profiles.
      Currently there are two public site profiles based on Wireframe:
      site-wireframe-docs is the demo&docs site mentioned above, just with placeholder content replaced with placeholder content. It's not a particularly complex site, but I believe it's still a pretty nice way to dig into the Wireframe module. site-wireframe-boilerplate is a boilerplate (or starter) site profile based on the docs site. This is still very much a work in progress, but essentially I'm trying to build a flexible yet full-featured starter profile you can just grab and start building upon. There will be a proper build process for resources, it will include most of the basic features one tends to need from site to site, etc. --
      Requirements and getting started:
      Wireframe can be installed just like any ProcessWire module. Just clone or download it to your site/modules/ directory and install. It doesn't, though, do a whole lot of stuff on itself – please check out the documentation site for a step-by-step guide on setting up the directory structure, adding the "bootstrap file", etc. You may find it easier to install one of the site profiles mentioned above, but note that this process involves the use of Composer. In the case of the site profiles you can install ProcessWire as usual and download or clone the site profile directory into your setup, but after that you should run "composer install" to get all the dependencies – including the Wireframe module – in place. Hard requirements for Wireframe are ProcessWire 3.0.112 and PHP 7.1+. The codebase is authored with current PHP versions in mind, and while running it on 7.0 may be possible, anything below that definitely won't work. A feature I added just today to the Wireframe module is that in case ProcessWire has write access to your site/templates/ directory, you can use the module settings screen to create the expected directories automatically. Currently that's all, and the module won't – for an example – create Controllers or layouts for you, so you should check out the site profiles for examples on these. (I'm probably going to include some additional helper features in the near future.)
      --
      This project is loosely based on an earlier project called pw-mvc, i.e. the main concepts (such as Controllers and the View layer) are very similar. That being said, Wireframe is a major upgrade in terms of both functionality and architecture: namespaces and autoloader support are now baked in, the codebase requires PHP 7, Controllers are classes extending \Wireframe\Controller (instead of regular "flat" PHP files), implementation based on a module instead of a collection of drop-in files, etc.
      While Wireframe is indeed still in a relatively early stage (0.3.0 was launched today, in case version numbers matter) for the most part I'm happy with the way it works, and likely won't change it too drastically anytime soon – so feel free to give it a try, and if you do, please let me know how it went. I will continue building upon this project, and I am also constantly working on various side projects, such as the site profiles and a few unannounced helper modules.
      I should probably add that while Wireframe is not hard to use, it is more geared towards those interested in "software development" type methodology. With future updates to the module, the site profiles, and the docs I hope to lower the learning curve, but certain level of "developer focus" will remain. Although of course the optimal outcome would be if I could use this project to lure more folks towards that end of the spectrum... 🙂
      --
      Please let me know what you think – and thanks in advance!
    • By tcnet
      PageViewStatistic for ProcessWire is a module to log page visits of the CMS. The records including some basic information like IP-address, browser, operating system, requested page and originate page. Please note that this module doesn't claim to be the best or most accurate.
      Advantages
      One of the biggest advantage is that this module doesn't require any external service like Google Analytics or similar. You don't have to modify your templates either. There is also no JavaScript or image required.
      Disadvantages
      There is only one disadvantage. This module doesn't record visits if the browser loads the page from its browser cache. To prevent the browser from loading the page from its cache, add the following meta tags to the header of your page:
      <meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate" /> <meta http-equiv="Pragma" content="no-cache" /> <meta http-equiv="Expires" content="0" /> How to use
      The records can be accessed via the Setup-menu of the CMS backend. The first dropdown control changes the view mode. There are 4 different view modes.
      View mode "Day" shows all visits of the selected day individually with IP-address, browser, operating system, requested page and originate page. Click the update button to see new added records. View mode "Month" shows the total of all visitors per day from the first to the last day of the selected month. View mode "Year" shows the total of all visitors per month from the first to the last month of the selected year. View mode "Total" shows the total of all visitors per year for all recorded years. Please note that multiple visits from the same IP address within the selected period are counted as a single visitor.
      Settings
      You can access the module settings by clicking the Configuration button at the bottom of the records page. The settings page is also available in the menu: Modules->Configure->ProcessPageViewStat.
      IP2Location
      This module uses the IP2Location database from: http://www.ip2location.com. This database is required to obtain the country from the IP address. IP2Location updates this database at the begin of every month. The settings of ProcessPageViewStat offers the ability to automatically download the database monthly. Please note, that automatically download will not work if your webspace doesn't allow allow_url_fopen.
      Dragscroll
      This module uses DragScroll. A JavaScript available from: http://github.com/asvd/dragscroll. Dragscroll adds the ability in view mode "Day" to drag the records horizontally with the mouse pointer.
      parseUserAgentStringClass
      This module uses the PHP class parseUserAgentStringClass available from: http://www.toms-world.org/blog/parseuseragentstring/. This class is required to filter out the browser type and operating system from the server request.
      Special Feature
      PageViewStatistic for ProcessWire can record the time a visitor viewed the page. This feature is deactivated by default. To activate open the module configuration page and activate "Record view time". If activated you will find a new column "S." in the records which means the time of view in seconds. With every page request, a Javascript code is inserted directly after the <body> tag. Every time the visitor switches to another tab or closes the tab, this script reports the number of seconds the tab was visible. The initial page request is recorded only as a hyphen (-).
       
    • By MoritzLost
      This module allows you to integrate hCaptcha bot / spam protection into ProcessWire forms. hCaptcha is a great alternative to Google ReCaptcha, especially if you are in the EU and need to comply with privacy regulations.

      The development of this module is sponsored by schwarzdesign.
      The module is built as an Inputfield, allowing you to integrate it into any ProcessWire form you want. It's primarily intended for frontend forms and can be added to Form Builder forms for automatic spam protection. There's a step-by-step guide for adding the hCaptcha widget to Form Builder forms in the README, as well as instructions for API usage.
      Features
      Inputfield that displays an hCaptcha widget in ProcessWire forms. The inputfield verifies the hCaptcha response upon submission, and adds a field error if it is invalid. All hCaptcha configuration options for the widget (theme, display size etc) can be changed through the inputfield configuration, as well as programmatically. hCaptcha script options can be changed through a hook. Error messages can be translated through ProcessWire's site translations. hCaptcha secret keys and site-keys can be set for each individual inputfield or globally in your config.php. Error codes and failures are logged to help you find configuration errors. Please check the README for setup instructions.
      Links
      Github Repository and documentation InputfieldHCaptcha in the module directory Screenshots (configuration)

      Screenshots (hCaptcha widget)

       
       

       
×
×
  • Create New...