Recently Browsing 0 members
No registered users viewing this page.
By Robin S
Pages At Bottom
Keeps selected pages at the bottom of their siblings.
A "bottom page" will stay at the bottom even if it is drag-sorted to a different location or another page is drag-sorted below it (after Page List is refreshed the bottom page will still be at the bottom).
Newly added sibling pages will not appear below a bottom page.
The module also prevents the API methods $pages->sort() and $pages->insertAfter() from affecting the position of bottom pages.
Note: the module only works when the sort setting for children on the parent page/template is "Manual drag-n-drop".
Because you want some pages to always be at the bottom of their siblings for one reason or another. And someone requested it. 🙂
Install the Pages At Bottom module.
Select one or more pages to keep at the bottom of their siblings.
Coming soon: sort bottom pages in Page List according to their sort order in the module config.
By Robin S
Another little admin helper module...
Template Field Widths
Adds a "Field widths" field to Edit Template that allows you to quickly set the widths of inputfields in the template.
When setting up a new template or trying out different field layouts I find it a bit slow and tedious to have to open each field individually in a modal just to set the width. This module speeds up the process.
Install the Template Field Widths module.
You can set the default presentation of the "Field widths" field to collapsed or open. You can choose Name or Label as the primary identifier shown for the field. The unchosen alternative will become the title attribute shown on hover. You can choose to show the original field width next to the template context field width.
Croppable Image 3
for PW 3.0.20+
Module Version 1.1.16
Sponsored by http://dreikon.de/, many thanks Timo & Niko!
You can get it in the modules directory!
Please refer to the readme on github for instructions.
Updating from prior versions:
Updating from Croppable Image 3 with versions prior to 1.1.7, please do this as a one time step:
In the PW Admin, go to side -> modules -> new, use "install via ClassName" and use CroppableImage3 for the Module Class Name. This will update your existing CroppableImage3 module sub directory, even if it is called a new install. After that, the module will be recogniced by the PW updater module, what makes it a lot easier on further updates.
For updating from the legacy Thumbnail / CropImage to CroppableImage3 read on here.
UPDATE: I have published a stable version of this module!
I'm working on a tiny textformatter module that searches the text for titles of other pages on your site and creates hyperlinks to them. I'm not sure if something like this exists already, but I haven't found anything in the module directory, so I wrote my own solution 🙂
It's not properly tested yet and is still missing some functionality I would like to implement, so at the moment it should be considered in BETA. Features include limiting the pages that will get searched by template, and adding a custom CSS class to the generated hyperlinks. As I'm writing this I noticed that it will probably include unpublished and hidden pages at the moment, so yeah ... it's still in development alright 😅
You can download the module from Github:
There's some more information in the readme as well.
Anyway, let me know what you think! I'm happy about any feedback, possible improvements or ideas on how to improve the module. Cheers.
Here I'm writing up about my first ProcessWire site, Reached.space, a blog and directory about shops which offer international shipping.
I'm from The GrayFly Group, which is the registered trade name for GrayFly Stationery, LLC, a limited liability company registered in the state of Kentucky, USA. You might ask, why is a stationery company creating websites?! Well, in a way both activities are very similar: both activities have the goal of getting written messages across in a pleasing manner to the reader.
With that out of the way, let's move on and explain what went on behind the scenes of the Reached.space site:
I used a free CSS-based template from W3CSS at https://www.w3schools.com/w3css/w3css_templates.asp , using mainly the "Architect" template as the basis and modifying it as needed.
The pagination feature of ProcessWire was very helpful here; I kept the home page to just two blogroll articles so that the reader was not overwhelmed, but upon pressing "more articles" the remainder of the blogroll is paginated with 4 articles to a page.
I made adjustments to my usage of the template to make it screen-reader-friendly. I used the Google Chrome extension to test out how the site would be handled with a screen reader.
Security is always important, so I was thrilled to find a great all-in-one-place security guide in the ProcessWire docs at https://processwire.com/docs/security/ - I simply went through the guide and did what it said, using it as a checklist.
As far as I'm aware, the only additional modules I used (that were not already activated by default in standard PW install) were the Upgrade and Upgrade Checker modules. The main reason for this was security considerations, but it was also an added convenience and peace of mind to have it check for updates every time I logged in.
However, I did use additional software that was not modules, as described below.
Other software - Simple HTML DOM
Here I was very fortunate to receive help from the ProcessWire community on the forum. Due to the site's monetization model being affiliate marketing, I wished to make all my external links nofollow and target _blank by default. User @Robin S was instrumental in showing me how to do this using Simple HTML DOM in the forum post https://processwire.com/talk/topic/17295-solved-how-to-make-external-links-nofollow-and-target-_blank-by-default-if-using-source-code-toggle-in-editor/
Other software - Google Analytics cookie manager
My site requirements for GDPR were specific enough that I felt I would rather develop my own code to handle Google Analytics tracking, which I'll describe here. I wanted to be certain GA tracking was disabled by default requiring opt-in, instead of opt-out. I also included in the Cookie Manager some written info about third party cookies (these are placed when clicking on affiliate links) and how the user can avoid such tracking (turn off third party cookies in their browser settings).
I also disabled front-end PW cookies as described here: https://processwire.com/talk/topic/15270-session-storage-and-lifetime/
Google Analytics cookie settings
Efficiency - optimizing 404s
I used the guide at https://processwire.com/blog/posts/optimizing-404s-in-processwire/ to sinkhole bot-driven 404 requests to a static 404 file.
Back office pic
Below is an image of how ProcessWire allows helpful field descriptions and displays them when used in templates, so that when I come to actually use or enter content in fields I created months ago, I know what the ramifications are. Very helpful. Also, when using the back office I found the Reno admin theme to be very pleasing, efficient, and easy to use.