Recently Browsing 0 members
No registered users viewing this page.
Just wondering if someone with a bit more PW knowledge than me could give a run down of what this method actually does and how its achieved.
I get that it rebuilds image variations but based on what settings?
If I wanted to rebuild all the websites image variations but at say a reduced image quality can this be set somewhere globally that this method would take into account?
For some context I have built a fairly simple module to delete all the image variations connected to any FieldtypeImage which is being used on the website, for the most part this works quite well. As I was quite happy with how that turned out I figured I would give the module another option to rebuild the images also. So there would be a 'Remove' and 'Rebuild' button on the modules config page.
The idea being that I could use this tool to delete all the image variations, update some global settings then regenerate them all but currently it doesn't appear to do that.
I assume this is either because my codes borked or im misunderstanding something fundamental about how rebuildVariations() works.
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 30+ 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.