Jump to content

Recommended Posts

As I see there's no way to get the actual link of those links. Maybe hooking to breadcrumbs and set the links to data attribute could work though.

Link to post
Share on other sites

you have the actual link of the current page:


i think it should be possible to just remove the last part of the url for every parent?


Link to post
Share on other sites

Good idea. I can't think of any drawbacks that could happen, but maybe I'm wrong.

To avoid the clutter, I would do it on ctrl+click instead any visual icon or something. What do you think about it?

Plus alt+click for edit for example, that's something I have already planned.

  • Like 1
Link to post
Share on other sites

my vote goes for

view: icon
edit: ctrl+click


only drawback of my method would be if somebody is rewriting urls somehow... maybe also on multisite environments? but at least they have the option to switch it OFF ;)

  • Like 1
Link to post
Share on other sites

My vote is: 

  • long click for view
  • ctrl+click to edit

or reversed :) Icons would make too much mess.

Btw, I most of the time can't get the long-click work in Chrome 51 (the built-in Edit/View feature). I works 1 times out of 10 or 20. In Firefox seems to work fine.

Link to post
Share on other sites

Update: looks like it's SlimJet browser only, in Chrome longclicks seem OK.

I got the longclick to work, now I need a similar bright idea how to get the edit link ("/edit/?id=XXX"). Perhaps I need to add all the parents' IDs to an inline JS and get it from there.

  • Like 1
Link to post
Share on other sites

v035 adds the abovementioned breadcrumb tweaks:

  • long-click on breadcrumb item to view page in frontend
  • ctrl+click to edit breadcrumb page

It's relatively buried under the "Hotkeys" submodule but I think it fits there. 

I'm open to ideas on different implementation of this feature but I woud like to keep the current "minimal" style (eg. better not using icons or hover menu).

  • Like 1
Link to post
Share on other sites

I'll see, thanks. I think a confirm (yes-no) dialog would be of more help here. Strictly forbidding to save the page may result in data lost if the upload never finishes (so you can't save the page itself at all).

  • Like 2
Link to post
Share on other sites

@tpr Good evening :)  While tinkering with the settings it occurred to me that it would be nice to be able to adjust the height of the rows of the Pages tree. The Reno theme uses this:

.content .PageList .PageListItem {
    border-bottom: 1px solid #e6ebf1;
    padding-top: 0.6 em;
    padding-bottom: 0.6 em;
    line-height: 1.3em;

Top/bottom padding with 0.3 em is quite usable too. Something like the "LongClickDuraton" inputbox would be nice to have to adjust this one too.

What do you think?

Link to post
Share on other sites

I have tried to improve the page list but I have to admit it's close to perfect as it is (at least for me). I see that this tweak could save some space but I'll wait until other page list related needs arise.

  • Like 2
Link to post
Share on other sites

The Page tree is a strange beast :) It works and it's usable but still... Anyway, thanks for putting my feature request on your todo list. I just want to save some scrolling. The Page tree of the Default Theme is more compact and I like it that way.

Link to post
Share on other sites


I use Soma's Page List Image Label module often and I think it would be nice having this feature inside AOS. While at it, I'll implement your request, it'll be named as "Compact page list" or similar. I think there's no need to make it customizable.

  • Like 1
Link to post
Share on other sites

Thanx in advance! Are you planning to make it adjustable on the fly? I mean not just in the module's settings (preferred default), but right on the page of the page list too. If we can stick to one setting only, then it is not so versatile.

Link to post
Share on other sites

You mean the page thumbs? There will be one global default (image field name), or template-field pairs for those who need more. Plus a setting for square thumbs, and that's all.

I think these settings are easier to use because you can set everything at one place (module settings).

Link to post
Share on other sites

I think I'll go with this syntax for the page thumbs:

	"featured_image": "template=wine|basic-page, children.count=0, parent!=1",
	"bg_image": ""

The idea is to use different fields (eg. "featured_image") and filter them with selectors. The first matching selector will be used. In this example featured_image is used on matching pages, and bg_image elsewhere.

I may modify the syntax to something that is easier to use. If only a string is entered, it will be treated as a global field to use on all pages.

  • Like 2
Link to post
Share on other sites
8 hours ago, tpr said:

You mean the page thumbs?

Sorry, I was on mobile, and could not spend too much time on my reply. Actually, I was talking about the thumbnail list vs the simple but compact list I requested. If I understand you correctly, we are talking about two different representation of the same list (tree). One with image thumbs, the other one is without the thumbs. Of course, you can use small top/bottom padding regardless of the presence of the thumbnail images, making the list compact no matther what. It just won't be too "compact" with the otherwise optional thumbnails, right?

Link to post
Share on other sites

I'm afraid I'm lost somewhere in between :) I was talking about the existing page list but prepending a small thumbnails to the items, not a thumbnail-only page list (there's a module for that as I know). I don't plan to add the latter because that would require much modifications and it's not the purpose of AOS.

To make this pagelist compact with the thumbnails, I will see how usable it is with smaller thumbs but I'm not sure that would make much sense (thumbs were too small).

  • Like 2
Link to post
Share on other sites

I have discovered an z-index issue with the Leaflet module. It concerns the breadcrumbs and headline div.


As you can see the magnifying glass on the right and and the size changer on the left side overlap.

Adding the following z-index to the breadcrumbs and headline div solves the problem:

#breadcrumbs {z-index:11}
#headline {z-index:11}

A lower index than 11 will not work.

Best regards

  • Like 1
Link to post
Share on other sites

Thanks @Juergen (or z-index-man :)) Version 0.3.6 is uploaded which should fix it. The problem is that the leaflet field sets a z-index of 1000 so I decided to use much larger values.

@szabesz is also covered with the new "Set narrow pagelist items" to reduce row height for the main pagelist. It's Reno theme only so it can be found under the RenoTweaks submodule.

This update contains the "Pagelist thumbnails" feature. I'm sure this will have some iterations but I really like the "fieldname: selector" syntax to add thumbs, it's really flexible.

  • Like 3
Link to post
Share on other sites
8 minutes ago, tpr said:

@szabesz is also covered with the new "Set narrow pagelist items" to reduce row height for the main pagelist. It's Reno theme only so it can be found under the RenoTweaks submodule.

Thank you very much, Sir! Double like :)

Have a good night!

  • Like 1
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 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 monollonom
      (once again I was surprised to see a work of mine pop up in the newsletter, this time without even listing the module on PW modules website 😅. Thx @teppo !)
      Github: https://github.com/romaincazier/FieldtypeQRCode
      Modules directory: https://processwire.com/modules/fieldtype-qrcode/
      This is a simple module I made so a client could quickly grab a QR Code of the page's url in the admin.
      There's not much to it for now, but if need be you can output anything using a hook:
      $wire->addHookAfter("FieldtypeQRCode::getQRText", function($event) { $event->return = "Your custom text"; }) You can also output the QR code on your front-end by calling the field:
      echo $page->qr_code_field; The module uses the PHP library QR Code Generator by Kazuhiko Arase. When looking for a way to generate a QR Code in PW I came across @ryan's integration in his TFA module. I'm not very familiar with fieldtype/inputfield module development so I blindly followed @bernhard (great) tutorial and his BaseFieldtypeRuntime. At some point I'll take a deeper look to make a module on my own.
      Some ideas for improvements :
      add the ability to choose what to ouput : page's url / editUrl / file(s) / image(s) / ... allow to output multiple QR codes ?
    • By Chris Bennett
      Inspired by @bernhard's excellent work on the new customisable LESS CSS getting rolled into the core soon, I thought I would offer up the module for beta testing, if it is of interest to anyone.

      It takes a different approach to admin styling, basically using the Cascade part of CSS to over-ride default UiKit values.
      Values are stored in ModuleConfig Module creates a separate AdminThemeTweaker Folder at root, so it can link to AdminThemeTweaker.php as CSS AdminThemeTweaker.php reads the module values, constructs the CSS variables then includes the CSS framework Can be switched on and off with a click. Uninstall removes everything, thanks to bernhard's wonderful remove dir & contents function.
      It won't touch your core. It won't care if stuff is upgraded. You won't need to compile anything and you don't need to touch CSS unless you want to.

      It won't do much at all apart from read some values from your module config, work out the right CSS variables to use (auto contrast based on selected backgrounds) and throw it on your screen.
      You can configure a lot of stuff, leave it as it comes (dark and curvy), change two main colors (background and content background) or delve deep to configure custom margins, height of mastheads, and all manner of silly stuff I never use.

      Have been developing it for somewhere around 2 years now. It has been (and will continue to be) constantly tweaked over that time, as I click on something and find something else to do.
      That said, it is pretty solid and has been in constant use as my sole Admin styling option for all of those 2 years.

      If nothing else, it would be great if it can provide any assistance to @bernhard or other contributor's who may be looking to solve some of the quirkier UiKit behavior.
      Has (in my opinion) more robust and predictable handling of hidden Inputfields, data-colwidths and showIf wrappers.
      I am very keen to help out with that stuff in any way I can, though LESS (and any css frameworks/tools basically) are not my go.
      I love CSS variables and banging-rocks-together, no-dependency CSS you can write with notepad.


    • By opalepatrick
      I see old posts saying that repeaters are not the way to go in Custom Process Modules. If that is the case, when using forms (as I am trying to do) how would one tackle things like repeat contact fields where there can be multiple requirements for contact details with different parameters? (Like point of contact, director, etc) or even telephone numbers that have different uses?
      Just for background I am creating a process module that allows me to create types of financial applications in the admin area (no need to publish any of this, pure admin) that require a lot of personal or company information.
      Maybe I am thinking about this incorrectly?
    • By HMCB
      I ran across a reference to IftRunner module. The post was 6 years ago. I cant find it in available modules. Has it been pulled?
  • Create New...