Jump to content



Recommended Posts

That's something I've already thought of but the way I tried to make it work failed and there were other things to do :) I'm not sure this module is the best place to make admin theme corrections, but for a temporary solution it could do.

  • Like 1
Link to comment
Share on other sites

very cool tpr!

feature request: an option to show the save options instantly on button hover. i find it really annoying to have to click on this little chevron to show the popup and then have to click again on the right option. i'm still missing the very quick "save+new" and "save+close" from joomla  :-X

offtopic: also thanks for the hint to netteforms - my project needs more time than i thought but it is getting more and more awesome :)


Link to comment
Share on other sites

Movie time!

These are two tweaks: always visible sidebar items and fixed header/sidebar. There are still some details to polish but seems useful.


  • Like 4
Link to comment
Share on other sites

feature request: an option to show the save options instantly on button hover.

I would prefer these extra buttons always visible. Waiting for the hover will cause frustration sooner or later :) Perhaps adding them below the main button? 

  • Like 1
Link to comment
Share on other sites

what i've also came across several times is when on mobile and you have a pagetable and you want to scroll down, if you tap on a pagetable item it will trigger the pagetable sort. it would be great to disable table sorting on mobile. or show just a sort symbol and allow sorting only on this icon.


Link to comment
Share on other sites

I would prefer these extra buttons always visible. Waiting for the hover will cause frustration sooner or later :) Perhaps adding them below the main button? 

in this case i would prefer them to be rendered beside in one row (inline)

Link to comment
Share on other sites

v003 is uploaded with some "before-the-weekend" Reno theme updates:

  • Make header sticky: stick the header to the top of the browser window so it stays in place when scrolling down
  • Make sidebar sticky: stick the sidebar to the top to make it always visible
  • Auto hide sidebar on left: auto hide the sidebar so it's accessible by moving the mouse to the left side of the screen
  • Always show sidebar items (disable accordion): make sidebar submenus more compact and do not hide them
  • Place header button next to the main title: moves the top (cloned) main button next to the title to make it easier to reach
  • Move notice close buttons to the left: put the close button of the notice message to the left for easier access
  • Like 3
Link to comment
Share on other sites

don't know how your module is organized (deadline coming), but throwing in an idea:

maybe we could have a "custom" folder, where we can put in our own code snippets and your module will make them visible for toggling on/off. 

for example:

/custom/makeButtonsBigger.js would result in some custom code that makes admin buttons bigger and a checkbox in your module. that way we could build our own repository of admin tweaks, put them on github or the like and on every new pw-install we would just have to do a git clone and tick some checkboxes.

what do you think?

this is quite similar to admincustomfiles but i never found it really easy to use so i don't really use it a lot. maybe we could have some kind of syntax in thos files to restrict it to a selector and show some better descriptions in your module/panel

/* custom admin tweak example
 * #summary
 * this is a great summary
 * with lots of content
 * #pageselector
 * id>10
 * #editedpageselector
 * template=example


#editedpageselector would refer to the currently edited page in processpageedit, whereas #pageselector would refer to the current admin page

any thoughts on this?

  • Like 1
Link to comment
Share on other sites

Didn't try the module (great name btw) yet, but how about making header sticky in the default admin theme? after-the-weekend, of course :-)

Check the latest commit (v004). There are other fixes as well for the admin themes, eg. do not apply some changes to modal contents, plus only add body classes to the proper admin themes.

maybe we could have a "custom" folder, where we can put in our own code snippets and your module will make them visible for toggling on/off. 

This would be surely possible but I need some time to fully understand it :) At first I'll concentrate on the "basics".

  • Like 1
Link to comment
Share on other sites

v006 is up - there are some new Reno theme tweaks plus LoadCollapsedModuleInfos. This auto-collapses module info fields on module configuration pages, saving space. 

  • Like 3
Link to comment
Share on other sites

v007 is up, with a Reno tweak that removes perhaps the biggest frustration the sidebar causes - the inability to single-click on the header links to navigate.

The module is featured in PW Weekly Nr 107, thanks!

Since the module is under rapid development it's likely that new features will be added before you even get to this post, which is why we won't even try to include a full list of features here.

So true, there's a lot of things awaiting to be fixed :)

  • Like 1
Link to comment
Share on other sites

v008 is committed to GitHub and it enables showing the Save dropdown menu on hover instead of on click. The only way I found to achieve this is adding a CSS class to the dropwdown which seems to work fine with the exception of Module config pages. Anyway, it covers 99% of the usage scenarios I think.

More agressive modifications were dropped because the markup wasn't generated the way I initially thought and it would be hard to solve.

  • Like 1
Link to comment
Share on other sites

v009 comes with a small feature update: ctrl+click on a language tab will activate all the language tabs of the same language. This is great for switching the current admin page fields to another language, eg. for checking contents of multiple fields at once.

  • Like 2
Link to comment
Share on other sites

The latest update (v010) can remove the masthead from the Reno theme. This is available only if sticky header is on. In fact this feature uses another approach for the sticky header because only the main content is scrollable, which perhaps makes it easier to see whether the page is scrolled down or not.

For the Reno theme there is a new setting "AlwaysShowSearch".

Other dropdown buttons are now also supported in the HoverSaveDropdown tweak. Remind me next time not trying to modify a cloned button instance because it won't work :)

There were numerous tweaks made to the admin configuration screen. Nested checkboxes now can't be modified if their parents are not checked, and also some space were saved by playing with field/fieldset options.


  • Like 4
Link to comment
Share on other sites

Hi @tpr,

thanks for making this fine tool for us. Is it for PW 2.7 too, or only for PW 3.x?

I cannot see a "required" property in the getModuleInfo. In the modules header comment it states ProcessWire 3.x, but then I cannnot see a namespace declaration in the file. This all makes me abit unsure, therefor I ask here. Sorry!

  • Like 2
Link to comment
Share on other sites

It seems that there are too many little thing changed from v3 which prevents certain features to work on PW v2, at least this is the case with 2.6. There are also some features that are missing from v2 that this module tries to modify, e.g long click duration.

I could breathe life into most of the submodules with little changes but I tend to support v3 only. There's a Hungarian saying "who looks backwards goes ass front to the future" and I believe in it :)

There are some unpublished updates to the module, eg fixed CKEditor toolbar and page preview link next to title. And also there are some bugs still awaiting to eliminate so I'll keep it in the shadows for a while :)


  • Like 2
Link to comment
Share on other sites

i think that would be a perfect fit for your module: https://processwire.com/talk/topic/13419-delete-a-lot-of-pics-at-once

something like an additional trash icon that, when clicked sets all images to deleted-state:


maybe you could also include this one into that update ;)



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

      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.
      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
      Github repository:
      File issues and feature requests here (your feedback and testing is greatly appreciated):
      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.
      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.
      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.
      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.
      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.
      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.
      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.
      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.
      - https://github.com/joyofpw/inertia
      - https://github.com/joyofpw/inertia-svelte-mix-pw
      - https://inertiajs.com/

    • 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
  • Create New...