Leaderboard

Thx ? Here you go: https://github.com/BernhardBaumrock/RockMigrations/releases/tag/v0.0.26 I hope I'll get used to tagging and not forget about it in the future ?

This is really easy either via RM or via default API: $modules->get('TracyDebugger'); // or $rm->installModule('TracyDebugger'); I'm using a GIT setup with submodules. So all I have to do is git submodule update --init --recursive That way I always have my modules under control of GIT and can efficiently commit new changes from any project that I'm currently working on ? But I went ahead and added support for rockmigrations via composer: https://packagist.org/packages/baumrock/rockmigrations Would be interested to hear if everything works!

There’s a new modules directory on the ProcessWire site now up and running. In this post we’ll cover a few details about what’s changed and what’s new. While last week's post introduced the modules directory, this post (part 2) focuses on newly added features for module authors (just pushed live today)— https://processwire.com/blog/posts/new-processwire-modules-directory/

It's because, packagist automaticly creates versions of a package, so you can specify which version you want to install. Without tags you can only install dev-master version (current latest commit) which composer considers as development while tags considers as stable. With tags composer installs the latest tagged version if you don't specify any, but if there is none you have to explicitly specify dev-master if your composer json is not configured to accept it automatically. See my module https://github.com/uiii/ProcessWire-FieldtypePDF as example.

remove this comment : https://github.com/processwire/processwire/blob/master/htaccess.txt#L173

Hi @cyberderf, Welcome to the forum. It seems like a url rewrite problem. Please check the following: 1. Does .htacccess file exist in your web root folder. You need to rename the htaccess.txt file to .htaccess. 2. Check your apache conf file and see if mod_rewrite is enabled. Gideon

Thank you for quick reply! I will take a look at it. I see composer installation really useful because I've just specified all dependencies in composer.json file and don't have to commit modules into my site's source code. So, when I deploy the site to production the automated script easily install all dependecies. All I have to do manually is to install the modules via admin (maybe this could be automated as well) or refresh if they are already installed. I've even created a "wrapper" composer package for processwire (see https://github.com/uiii/processwire), which will install like a regular installation, or upgrade the existing. So my site's source code only contains the site folder (without modules) and composer.json (and composer.lock) and this is enough basis to setup the whole running site by single command: composer install

Hi @Lewis Newson There are two options: You can create custom inputfield based on InputfiedPassword, just rename it, corret render and processInput methods You can hook render and processInput methods and change it to what you need.

v0.2.0 released, which is a fairly major refactoring of the module with some new features. There are now dropdowns in ProcessTemplate and ProcessField that allow you to quickly jump from editing one template/field to another. There are config options to disable these new dropdowns if you don't want them for some reason, and options to exclude system templates/fields from the dropdowns. The update is available directly from GitHub but unfortunately I am locked out from editing this module in the directory (I've emailed @ryan about it) so v0.2.0 won't show up there until the next automatic update runs.

I realise it's been a while since this was posted (again: sorry!) but while some sort of email trigger might be an interesting future addition, at the moment what Adrian suggested is probably the fastest and easiest way to achieve this. That, or perhaps Field Change Notifier in case you prefer a GUI solution ?