Jump to content

AdminOnSteroids


tpr

Recommended Posts

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.

Link to comment
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
Link to comment
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.

Link to comment
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
Link to comment
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
Link to comment
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.

Link to comment
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
Link to comment
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

Link to comment
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
Link to comment
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 :)

Link to comment
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
Link to comment
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
Link to comment
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.

Link to comment
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
Link to comment
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
Link to comment
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 tcnet
      This module implements the website live chat service from tawk.to. Actually the module doesn't have to do much. It just need to inserted a few lines of JavaScript just before the closing body tag </body> on each side. However, the module offers additional options to display the widget only on certain pages.
      Create an account
      Visit https://www.tawk.to and create an account. It's free! At some point you will reach a page where you can copy the required JavaScript-code.

      Open the module settings and paste the JavaScript-code into the field as shown below. Click "Submit" and that's all.

      Open the module settings
      The settings for this module are located int the menu Modules=>Configure=>LiveChatTawkTo.

       
    • By tcnet
      Session Viewer is a module for ProcessWire to list session files and display session data. This module is helpful to display the session data of a specific session or to kick out a logged in user by simply delete his session file. After installation the module is available in the Setup menu.

      The following conditions must be met for the module to work properly:
      Session files
      Session data must be stored in session files, which is the default way in ProcessWire. Sessions stored in the database are not supported by this module. The path to the directory where the session files are stored must be declared in the ProcessWire configuration which is by default: site/assets/sessions.
      Serialize handler
      In order to transform session data easier back to a PHP array, the session data is stored serialized. PHP offers a way to declare a custom serialize handler. This module supports only the default serialize handlers: php, php_binary and php_serialize. WDDX was dropped in PHP 7.4.0 and is therefore not supported by this module as well as any other custom serialize handler. Which serialize handler is actually used you can find out in the module configuration which is available under Modules=>Configure=>SessionViewer.

      Session data
      The session data can be displayed in two different ways. PHP's default output for arrays print_r() or by default for this module nice_r() offered on github: https://github.com/uuf6429/nice_r. There is a setting in the module configuration if someone prefers print_r(). Apart from the better handling and overview of the folded session data the output of nice_r() looks indeed nicer.

      Links
      ProcessWire module directory
      github.com
    • By Robin S
      Repeater Easy Sort
      Adds a compact "easy-sort" mode to Repeater and Repeater Matrix, making those fields easier to sort when there are a large number of items.
      The module also enhances Repeater Matrix by allowing a colour to be set for each matrix type. This colour is used in the item headers and in the "add new" links, to help visually distinguish different matrix types in the inputfield.
      Screencasts
      A Repeater field

      A Repeater Matrix field with custom header colours

      Easy-sort mode
      Each Repeater/Matrix item gets an double-arrow icon in the item header. Click this icon to enter easy-sort mode.
      While in easy-sort mode:
      The items will reduce in width so that more items can be shown on the screen at once. The minimum width is configurable in the field settings. Any items that were in an open state are collapsed, but when you exit easy-sort mode the previously open items will be reopened. You can drag an item left/right/up/down to sort it within the items. The item that you clicked the icon for is shown with a black background. This makes it easier to find the item you want to move in easy-sort mode. You can click an item header to open the item. An "Exit easy-sort mode" button appears at the bottom of the inputfield. Configuration
      In the field settings for Repeater and Repeater Matrix fields you can define a minimum width in pixels for items in easy-sort mode. While in easy-sort mode the items will be sized to neatly fill the available width on any screen size but will never be narrower than the width you set here.
      In the field settings for Repeater Matrix you can define a custom header colour for each matrix type using an HTML "color" type input. The default colour for this type of input is black, so when black is selected in the input it means that no custom colour will be applied to the header.
      Exclusions
      The easy-sort mode is only possible on Repeater/Matrix fields that do not use the "item depth" option.
       
      https://github.com/Toutouwai/RepeaterEasySort
      https://processwire.com/modules/repeater-easy-sort/
    • By FireWire
      Hello community!

      I want to share a new module I've been working on that I think could be a big boost for multi-language ProcessWire sites.

      Some background, I was looking for a way for our company website to be efficiently translated as working with human translators was pretty laborious and a lack of updating content created a divergence between languages. I, and several other devs here, have talked about translation integrations and have recognized the power that DeepL has. DeepL is an AI deep learning powered service that delivers translation quality beyond any automated service available. After access to the API was opened up to the US, I built Fluency, a DeepL translation integration for ProcessWire.
      Fluency brings automated translation to every multi-language field in the admin, and also provides a translation tool allowing the user to translate their text to any language without it being inside a template's field. With Fluency you can:
      Translate any plain textarea or text input Translate any CKEditor content (yes, with markup) Translate page names for fully localized URLs on every page Translate your in-template translation function wrapped strings Translate modules Fluency is free, and now so is DeepL
      Since this module was first built DeepL has introduced free Developer accounts that allow anyone to start using Fluency at zero cost and beginning with the version 0.3.0 release Fluency now supports free DeepL accounts. As of June 2021 DeepL supports translation to 26 languages and continues to offer more.
      Installation and usage is completely plug and play. Whether you're building a new multi-language site, need to update a site to multi-language, or simply want to stop manually translating a site and make any language a one-click deal, it could not be easier to do it. Fluency works by having you match the languages configured in ProcessWire to DeepL's. You can have your site translating to any or all of the languages DeepL translates to in minutes (quite literally).
      Let's break out the screenshots...
      When the default language tab is shown, a message is displayed to let users know that translation is available. Clicking on each tab shows a link that says "Translate from English". Clicking it shows an animated overlay with the word "Translating..." cycling through each language and a light gradient shift. Have a CKEditor field? All good. Fluency will translated it and use DeepL's ability to translate text within HTML tags. CKEditor fields can be translated as easily and accurately as text/textarea fields.

      Repeaters and AJAX created fields also have translation enabled thanks to a JavaScript MutationObserver that searches for multi-language fields and adds translation as they're inserted into the DOM. If there's a multi-language field on the page, it will have translation added.

      Same goes for image description fields. Multi-language SEO friendly images are good to go.

      Creating a new page from one of your templates? Translate your title, and also translate your page name for native language URLs. (Not available for Russian, Chinese, or Japanese languages due to URL limitations). These can be changed in the "Settings" tab for any page as well so whether you're translating new pages or existing pages, you control the URLs everywhere.

      Language configuration pages are no different. Translate the names of your languages and search for both Site Translation Files (including all of your modules)

      Translate all of the static text in your templates as well. Notice that the placeholders are retained. DeepL is pretty good at recognizing and keeping non-translatable strings like that. If it is changed, it's easy to fix manually.

      Fluency adds a "Translate" item to the CMS header. When clicked this opens up a modal with a full translation tool that lets the user translate any language to any language. No need to leave the admin if you need to translate content from a secondary language back to the default ProcessWire language. There is also a button to get the current API usage statistics. DeepL account owners can set billing limitations via character count to control costs. This may help larger sites or sites being retrofitted keep an eye on their usage. Fluency can be used by users having roles given the fluency-translate permission.

      It couldn't be easier to add Fluency to your new or existing website. Simply add your API key and you're shown what languages are currently available for translation from/to as provided by DeepL. This list and all configuration options are taken live from the API so when DeepL releases new languages you can add them to your site without any work. No module updates, just an easy configuration. Just match the language you configured in ProcessWire to the DeepL language you want it to be associated with and you're done. Fluency also allows you to create a list of words/phrases that will not be translated which can prevent items such as brands and company names from being translated when they shouldn't

       
      Limitations:
      No "translate page" - Translating multiple fields can be done by clicking multiple translation links on multiple fields at once but engineering a "one click page translate" is not feasible from a user experience standpoint. The time it takes to translate one field can be a second or two, but cumulatively that may take much longer (CKEditor fields are slower than plain text fields). There may be a workaround in the future but it isn't currently on the roadmap. See a solution below... No "translate site" - Same thing goes for translating an entire website at once. It would be great, but it would be a very intense process and take a very (very) long time. There may be a workaround in the future but it isn't on the roadmap. No current support for Inline CKEditor fields - Handling for CKEditor on-demand hasn't been implemented yet, this is planned for a future release though and can be done. I just forgot about it because I've never really used that feature personally.. Alpha release - This module is in alpha. Releases should be stable and usable, but there may be edge case issues. Test the module thoroughly and please report any bugs via a Github issue on the repository or respond here. Please note that the browser plugin for Grammarly conflicts with Fluency (as it does with many web applications). To address this issue it is recommended that you disable Grammarly when using Fluency, or open the admin to edit pages in a private window where Grammarly may not be loaded. This is a long-standing issue in the larger web development community and creating a workaround may not be possible. If you have insight as to how this may be solved please visit the Github page and file a bugfix ticket.
      Enhancements
      Translate All Fields On A Page
      An exciting companion module has been written by @robert which extends the functionality of Fluency to translate all fields on a page at once. The module has several useful features that can make Fluency even more useful and can come in handy for translating existing content more quickly. I recommend reading his comments for details on how it works and input on best practices later in this thread.
      Get the module at the Github repo: https://github.com/robertweiss/ProcessTranslatePage
      Requirements:
      ProcessWire  3.0+ UIKit Admin Theme That's Fluency in a nutshell. A core effort in this module is to create it so that there is nothing DeepL related hard-coded in that would require updating it when DeepL offers new languages. I would like this to be a future-friendly module that doesn't require developer work to keep it up-to-date.
      The Module Is Free
      This is my first real module and I want to give it back to the community as thanks. This is the best CMS I've worked with (thank you Ryan & contributors) and a great community (thank you dear reader).
      DeepL Developer Accounts
      In addition to paid Pro Developer accounts, DeepL now offers no-cost free accounts. Now all ProcessWire developers and users can use Fluency at no cost. Learn more about free and paid accounts by visiting the DeepL website. Sign up for a Developer account, get an API key, and start using Fluency.
      Download & Feedback
      Download the latest version here
      https://github.com/SkyLundy/Fluency-Translation/archive/main.zip
      Github repository:
      https://github.com/SkyLundy/Fluency-Translation
      File issues and feature requests here (your feedback and testing is greatly appreciated):
      https://github.com/SkyLundy/Fluency-Translation/issues
       
      Thank you! ¡Gracias! Ich danke Ihnen! Merci! Obrigado! Grazie! Dank u wel! Dziękuję! Спасибо! ありがとうございます! 谢谢你!

    • By kixe
      Field that stores one or more references to ProcessWire pages with additional data in field context.
      Values are editable via page edit modal of the referenced page provided from the field if module AdminPageFieldEditLinks is installed and "Enable link to create new pages?" is checked in field settings.
      Requirements: AdminPageFieldEditLinks >= 3.1.4
      https://github.com/kixe/FieldtypePageContextData
      https://processwire.com/modules/fieldtype-page-context-data/
      Use case example:
      The planning of the Tonmeistertagung in the CCD (Congress Center Düsseldorf) from November 3rd, 2021 to November 6th, 2021 is in the finalization phase.
      The conference consists of a conference part and an exhibition. The planning is done via a separate frontendless PW instance. There, all companies (pages) that are active at various events are kept in a pool. Changes (address, logo) can always be done there. For the exhibition of the current conference in November, the exhibitor-companies (pages) are selected via a page reference field. A stand number must now be assigned to each selected company (page). We had originally solved this using the Profield FieldtypeTable. However, this had the disadvantage that each entry again made all companies available for selection and did not recognize which were already selected in a previous table row. The new field type now allows the value (company's stand number) to be assigned to a Company (page) in context to a specific Pagefield living in a specific page.
      https://tonmeistertagung.com/en/exhibitors/exhibition/
       
×
×
  • Create New...