Jump to content

AdminOnSteroids


tpr

Recommended Posts

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

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

 

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

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

Link to comment
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
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 LuisM
      Symprowire is a PHP MVC Framework based and built on Symfony using ProcessWire 3.x as DBAL and Service-Provider
      It acts as a Drop-In Replacement Module to handle the Request/Response outside the ProcessWire Admin. Even tough Symfony or any other mature MVC Framework could be intimidating at first, Symprowire tries to abstract Configuration and Symfony Internals away as much as possible to give you a quick start and lift the heavy work for you.
      The main Goal is to give an easy path to follow an MVC Approach during development with ProcessWire and open up the available eco-system.
      You can find the GitHub Repo and more Information here: https://github.com/Luis85/symprowire
      Documentation
      The Symprowire Wiki https://github.com/Luis85/symprowire/wiki How to create a simple Blog with Symprowire https://github.com/Luis85/symprowire/wiki/Symprowire-Blog-Tutorial Last Update
      16.07.2021 // RC 1 v0.6.0 centralized ProcessWire access trough out the Application by wrapping to a Service https://github.com/Luis85/symprowire/releases/tag/v0.6.0-rc-1 Requirements
      PHP ^7.4 Fresh ProcessWire ^3.0.181 with a Blank Profile Composer 2 (v1 should work, not recommended) The usual Symfony Requirements Features
      Twig Dependency Injection Monolog for Symprowire Support for .env YAML Configuration Symfony Console and Console Commands Symfony Webprofiler Full ProcessWire access inside your Controller and Services Webpack Encore support Caveats
      Symfony is no small Framework and will come with a price in terms of Memory Usage and added Overhead. To give you a taste I installed Tracy Debugger alongside to compare ProcessWire profiling with the included Symfony Webprofiler

      So in a fresh install Symprowire would atleast add another 2MB of Memory usage and around 40ms in response time, should be less in production due to the added overhead of the Webprofiler in dev env
       
    • 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. 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 an issue that may not have a resolution as 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.
      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 today.
      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 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.

      Detailed records
      View mode "Detailed records" 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.

      Cached visitor records
      View modes other than "Detailed records" are cached visitor counts which will be collected on a daily basis from the detailed records. This procedure ensures a faster display even with a large number of data records. Another advantage is that the detailed records can be deleted while the cache remains. The cache can be updated manually or automatically in a specified time period. Multiple visits from the same IP address on the same day are counted as a single visitor.

      Upgrade from older versions
      Cached visitor counts is new in version 1.0.8. If you just upgraded from an older version you might expire a delay or even an error 500 if you display cached visitor counts. The reason for this is that the cache has to be created from the records. This can take longer if your database contains many records. Sometimes it might hit the maximally execution time. Don't worry about that and keep reloading the page until the cache is completely created.
      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 (-).

      New in version 1.1.0
      A new feature comes with version 1.1.0 which offers to record user names of loggedin visitors. Just activate "Record user names" and "Record loggedin user" in the module settings.
      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.
    • By clsource
      Inertia Adapter ProcessWire Module
      Hello! Long time no see.
      I created this module so you can use Inertia.js (https://inertiajs.com/) with ProcessWire.
      Description
      Inertia allows you to create fully client-side rendered, single-page apps, without much of the complexity that comes with modern SPAs. It does this by leveraging existing server-side frameworks.
      Inertia isn’t a framework, nor is it a replacement to your existing server-side or client-side frameworks. Rather, it’s designed to work with them. Think of Inertia as glue that connects the two. Inertia comes with three official client-side adapters (React, Vue, and Svelte).
      This is an adapter for ProcessWire. Inertia replaces PHP views altogether by returning JavaScript components from controller actions. Those components can be built with your frontend framework of choice.
      Links
      - https://github.com/joyofpw/inertia
      - https://github.com/joyofpw/inertia-svelte-mix-pw
      - https://inertiajs.com/
      Screenshots


       
    • By sms77io
      Hi all,
      we made a small module for sending SMS via Sms77.io. It supports sending to one and multiple users.
      You can download it from GitHub and follow the instructions on how to install it - it is quite easy. An API key is required for sending, get yours for free @ Sms77 and receive 0,50 €.
      Hope this helps somebody and we are open for improvement suggestions!
       
      Best regards
      André
×
×
  • Create New...