Recently Browsing 0 members
No registered users viewing this page.
Hi! I've created a small Inputfield module called InputfieldFloatRange which allows you to use an HTML5 <input type="range" ../> slider as an InputField. I needed something like this for a project where the client needs to be able to tweak this value more based on 'a feeling' than just entering a boring old number. Maybe more people can use this so I'm hereby releasing it into the wild.
What is it?
The missing range slider Inputfield for Processwire.
What does it do?
This module extends InputfieldFloat and allows you to use HTML5 range sliders for number fields in your templates.
It includes a visible and editable value field, to override/tweak the value if required.
Min/max values Precision (number of decimals) Steps (Read more) Manual override of the selected value (will still adhere to the rules above) Usage
Clone / zip repo Install FieldtypeFloatRange, this automatically installs the Inputfield Create new field of type `Float (range)` or convert an existing `Float`, `Integer` or `Text` field. To render the field's value simply echo `$page->field` Demo
A field with Min=0, Max=1, Step=0.2, Precision=2
Field with settings Min=0, Max=200, Step=0.25, Precision=2
Make the display-field's size configurable (will use the Input Size field setting) Hopefully become redundant If it's usable for others I'll add it to the Modules list
- Fix issue where setting the step value to an empty value created problem with validation
- Make the display-field optional
- Initial release
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. Field widths entered into the Template Field Widths inputfield are only applied if the Edit Template form is submitted with the Template Field Widths inputfield in an opened state. "Collapsed" is the recommended setting if you think you might also use core inputs for setting field widths in a template context. 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.
Tracy Debugger for ProcessWire
The ultimate “swiss army knife” debugging and development tool for the ProcessWire CMF/CMS
Integrates and extends Nette's Tracy debugging tool and adds 35+ custom tools designed for effective ProcessWire debugging and lightning fast development
The most comprehensive set of instructions and examples is available at: https://adrianbj.github.io/TracyDebugger
Modules Directory: http://modules.processwire.com/modules/tracy-debugger/
A big thanks to @tpr for introducing me to Tracy and for the idea for this module and for significant feedback, testing, and feature suggestions.
By Mike Rockett
Jumplinks for ProcessWire
Jumplinks is an enhanced version of the original ProcessRedirects by Antti Peisa.
The Process module manages your permanent and temporary redirects (we'll call these "jumplinks" from now on, unless in reference to redirects from another module), useful for when you're migrating over to ProcessWire from another system/platform. Each jumplink supports wildcards, shortening the time needed to create them.
Unlike similar modules for other platforms, wildcards in Jumplinks are much easier to work with, as Regular Expressions are not fully exposed. Instead, parameters wrapped in curly braces are used - these are described in the documentation.
Under Development: 2.0, to be powered by FastRoute
As of version 1.5.0, Jumplinks requires at least ProcessWire 2.6.1 to run.
View on GitLab
Download via the Modules Directory
Read the docs
The most prominent features include:
Basic jumplinks (from one fixed route to another) Parameter-based wildcards with "Smart" equivalents Mapping Collections (for converting ID-based routes to their named-equivalents without the need to create multiple jumplinks) Destination Selectors (for finding and redirecting to pages containing legacy location information) Timed Activation (activate and/or deactivate jumplinks at specific times) 404-Monitor (for creating jumplinks based on 404 hits) Additionally, the following features may come in handy:
Stale jumplink management Legacy domain support for slow migrations An importer (from CSV or ProcessRedirects) Feedback & Feature Requests
I’d love to know what you think of this module. Please provide some feedback on the module as a whole, or even regarding smaller things that make it whole. Also, please feel free to submit feature requests and their use-cases.
Note: Features requested so far have been added to the to-do list, and will be added to 2.0, and not the current dev/master branches.
Jumplinks is an open-source project, and is free to use. In fact, Jumplinks will always be open-source, and will always remain free to use. Forever. If you would like to support the development of Jumplinks, please consider making a small donation via PayPal.