Jump to content



Recommended Posts

Module to handle frontend user login / logout.

Also should work with Persistent login for users (mode: automatically) out of the box


  • 0.3.1




Module isn't available anymore, but it's planed to replace FrontendUserLogin and FrontendUserRegister with the new FrontendUser module which is not released yet.

A new support topic will be created after FrontendUser module is added to the PW module repo.

FrontendUser module

Edited by pwFoo
  • Like 7
Link to comment
Share on other sites

  • 1 month later...

Released version 0.1.0

  • minor changes
  • updated compatibility to FormHelper 0.3.2
  • moved render() out of the login() method to make the form changeable via public FormHelper class variable $this->fh->...
  • username sanitized by FormHelper (sanitizer set in username field array)

I would like to make the module flexible and extendable, but at the moment no addons / plugins implemented...

Link to comment
Share on other sites

  • 1 month later...

New branch with removed FormHelper dependency. Instead it uses the new form api array input support.

Works in my local test environment. Simple frontend login module with error handling.

After some time playing with JavaScript / ajax I should finish some basic modules *g*

Link to comment
Share on other sites

  • 1 month later...

FrontendUserLogin 0.3 released (dev / unstable)

Updated initial post. Tests and feedback welcome! :)

  • FormHelper dependency is removed
  • should work with Persistent login for users  (mode: automatically) out of the box
  • simple error handling (login failed, LoginThrottle, missing required value)

  • Strings translatable by using $this->_()

  • code optimized and some hookable methods removed (use PW Session methods instead!)
  • hookable methods to modify form fields and form process / validation. Also to extend module with plugins / addons.


  • Change password field type to password (at the moment isn't supported by PW?!)
  • Remove (optional) field labels (seems not working after field is added to the form object?!)
  • maybe a default style and optional add custom css / js code
  • Change integration of Persistent login for users via plugin module (add Remember me checkbox and trigger PersistLogin manual mode)
  • Forgot Password core module integration?
Edited by pwFoo
Link to comment
Share on other sites

Login module should work, but the form is unstyled.

A plugin is a module with attach / detach during install / uninstall to the parent module.

Demo plugins (minimal tested!) are

  • persistLogin module integration (manual mode, remember me checkbox)
  • ProcessForgotPassword (core module) integration


Edited by pwFoo
Link to comment
Share on other sites

  • 1 month later...

I have a local testing version with field callbacks ("prepare" before added to form and "process" after form "basic" process) and preLogin / postLogin callbacks

Possible usage:

// Integrate LoginPersist module (manual mode) after sucessfully logged in
$callback['postLogin'] = function ($fulObj) {
    if ($fulObj->attr('result')) {

// optional login with email address instead of an username... (could also be done as username form field callback "process"! Just an example!!!)
$callback['preLogin'] = function ($fulObj) {
// callback defined outside the module class, so $this and private class attributes won't work!
// module object hand over as function param. Get / set attributes with the attr() method.
$email = $fulObj->attr('form')->get('username')->value;
$userObj = wire('users')->get("email={$email}");
if ($userObj instanceof User) $fulObj->attr('user', $userObj->name);

// login call with optional callback
echo $ful->login("{$config->urls->root}login", $callback)->render();

Internal field process callback (sanitize input value)

 * Username form field
 * @return object Username field
protected function fieldUsername() {
    $field = $this->modules->get('InputfieldText');
    $field->label = $this->_('Username');
    $field->attr('id+name', 'username');
    $field->required = 1;
    // Set a "callbackProcess" to sanitize the input value or a "callbackPrepare" executed just before the field will be added to the form
    $field->fulOption = array(
        'callbackProcess' => function ($field) {
//      'callbackProcess' => function ($field, $obj) { // to get module object also outside the module class use an additional param
            // callback defined inside the module class and $this will work here. Also wire() could be used
            $this->user = wire('sanitizer')->username($field->value);
        'callbackPrepare' => function ($field) {
            // Your code here... will be executed before field added to form
    return $field;

What do you think about the change and usage of dynamic functions as callbacks?

Link to comment
Share on other sites

  • 3 weeks later...

Latest update to my local testing branch...

  • Moved totally from custom callbacks to PW hooks (core and module own hookable methods)
  • Have a working minimal FrontendUserLogin and FrontendUserRegister module.
  • Added FormHelper dependency again (instead of a extended wrapper FormHelper is changed to extend InputfieldForm object)

FrontendUserLogin / FrontendUserRegister (simple use)

// login
echo $modules->get('FrontendUserLogin')->render($redirectAfterLogin);

// register
echo $modules->get('FrontendUserRegister')->render($redirectAfterRegister);

The method render() is a shortcut. Long form with chance to modify parameters, form, ... 


How to add plugins?

After $fu->form() define the plugin field and needed processing validation code as a PW hook

RememberMe plugin to integrate LoginPersist module

    // RememberMe field / persistLogin integration
    $remember = $modules->get('InputfieldCheckboxes');
    $remember->name = 'persist';
    $remember->attr('id+name', 'persist');
    $remember->skipLabel = 4;
    $remember->addoption('persist', 'Remember me?');
    $remember->addHookAfter('processInput', function($event) {
        $field = $event->object;
        if (isset($field->value[0]) && $field->value[0] === 'persist') {
            wire()->addHookAfter('Session::login', function($event) {

Or an integration of core module ProcessForgotPassword

    // ForgotPassword integration
    $forgot = $modules->get('InputfieldMarkup');
    $forgot->value = "<a href='{$page->url}?forgot=1'>{$this->_('Forgot password?')}</a>";
    if ($input->get->forgot) {
        function processForgot($event) {
            $event->return = wire('modules')->get('ProcessForgotPassword')->execute();
            $event->replace = true;
        $fu->addHookBefore('FrontendUserLogin::login', null, 'processForgot');

Login with email address instead of username?

    // Email login instead of username
    $fieldUser = $fu->attr('form')->get('username');
    $fieldUser->addHookBefore('FrontendUserLogin::auth', function($event) {
        $fu = $event->object;
        $email = $fu->attr('form')->fhValue('username', 'email');
        $loginUser = wire('users')->get("email={$email}");
        if ($loginUser instanceof User && !$loginUser->isGuest()) {
            $event->arguments(0, $loginUser->name);

You have added a nickname field to user template? The plugin to use the nickname (sanitized text instead of username) to login

    // Nickname login instead of username
    $fieldUser = $fu->attr('form')->get('username');
    $fieldUser->addHookBefore('FrontendUserLogin::auth', function($event) {
        $fu = $event->object;
        $nick = $fu->attr('form')->fhValue('username', 'text');
        $loginUser = wire('users')->get("nickname={$nick}");
        if ($loginUser instanceof User && !$loginUser->isGuest()) {
            $event->arguments(0, $loginUser->name);

The plugins are tested and working fine, but I don't know how to ship plugins. At the moment it's code inside the template login.php, but should be moved to a separate plugin file or the FrontendUserLogin module...

Any suggestions?

*Added nickname login plugin and fixed a nickname / email login bug*

Edited by pwFoo
  • Like 4
Link to comment
Share on other sites

Here is a FrontendUserLogin screenshot with additional fields (PersistLogin, ProcessForgotPassword integration) and a basic style (removed list style), Form fields without label and placeholder instead.


Default css / js can be added inside the module directory. Custom styles will be loaded from templates/FrontendUserLogin/FrontendUserLogin.<css|js>.

FormHelper dependency could be replaced, but in version 0.7+ FormHelper isn't that big and no need to copy & paste form handling to each module with forms or file upload (FrontendUserLogin, FrontendUserRegister, contact form, ...).

  • Like 1
Link to comment
Share on other sites

FrontendUserLogin module deletion requested, because it's an old and deprecated version.

Last posts here reference to a redesigned and not compatible new module / branch.

I have deleted this module from the directory, but you should consider removing the link from your first post and explain to users what the alternative is.

Link to comment
Share on other sites

  • 2 weeks later...
  • 2 weeks later...

FrontendUser module handles login, logout and user registration.

I moved the complex email validation plugin, ProcessForgotPassword and LoginPersist module integration into the FrontendUser module for testing.

If anyone would do some tests...

Repo: https://bitbucket.org/pwFoo/frontenduser/overview

Doku: https://bitbucket.org/pwFoo/frontenduser/wiki/Documentation

Current download for testing: https://bitbucket.org/pwFoo/frontenduser/get/master.zip

  • Like 2
Link to comment
Share on other sites

  • 2 weeks later...

hi pwFoo,

i'm toying around with your great register module. I have a php fatal error and since i'm not-so in-depth to php/versions/objectoriented stuff, would you mind and confirm or not if this may be caused by me being forced to use PW in a php 5.3 environment?
PW (2.58) in itself runs fine; but I noticed from the earlier notes in your module that it needed php >5.5 (?). Anyhow the error looks like $this (no pun intented):

Fatal error: Using $this when not in object context in /var/www/<snipsnap>/site/modules/FrontendUser/FrontendUser.module on line 252

which refers to this line

$username = $this->form->fhValue($field->name);

in here:

protected function usernameRegister() {
        $field = $this->modules->get('InputfieldText');
        $field->label = $this->_('Username');
        $field->attr('id+name', 'username');
        $field->required = 1;
        $field->fhSanitizer = 'username';
        $field->addHookAfter('processInput', function($event) {
            $field = $event->object;
            $username = $this->form->fhValue($field->name);
            if (empty($username))   return;
            elseif (wire('users')->count("name={$username}") == 0) {
                $this->userObj->name = $username;
            else {
                $field->error(__('Username already taken!'));  
        return $field;

many thx for the module :-)


Link to comment
Share on other sites

Hello Tom,

thank You for your feedback here!

It's a anonymous function problem / missing feature. I have to add a PHP 5.4 dependency or find a workaround. I missed that because I tested it with a PHP 5.5.24. 

Version Description 5.4.0 $this can be used in anonymous functions. 5.3.0 Anonymous functions become available.

See here: http://php.net/manual/en/functions.anonymous.php

That could be a workaround...

     * Username form field
     * @return InputfieldText Username field
    protected function usernameRegister() {
        $field = $this->modules->get('InputfieldText');
        $field->label = $this->_('Username');
        $field->attr('id+name', 'username');
        $field->required = 1;
        $field->fhSanitizer = 'username';

        // workaround PHP 5.3
        $fu = $this; 
        //$field->addHookAfter('processInput', function($event) {
        $field->addHookAfter('processInput', function($event) use ($fu) {
            $field = $event->object;
            // workaround PHP 5.3
            //$username = $this->form->fhValue($field->name);
            $username = $fu->attr('form')->fhValue($field->name);

            if (empty($username))   return;
            elseif (wire('users')->count("name={$username}") == 0) {
                // workaround PHP 5.3
                //$this->userObj->name = $username;
                $fu->attr('userObj')->name = $username;
            else {
                $field->error(__('Username already taken!'));  
        return $field;

I think some more changes like that have to be done to get it work with PHP 5.3

But I don't know if it make sense to make it PHP 5.3 compatible. But should be no problem if that's all...


Sorry for confusion of different topics *g*

The correct support topic is: https://processwire.com/talk/topic/9811-frontenduser-login-logout-and-register-users-members/

  • Like 1
Link to comment
Share on other sites

This topic is now closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By LuisM
      Symprowire is a PHP MVC Framework based and built on Symfony using ProcessWire 3.x as DBAL and Service-Provider
      It acts as a Drop-In Replacement Module to handle the Request/Response outside the ProcessWire Admin. Even tough Symfony or any other mature MVC Framework could be intimidating at first, Symprowire tries to abstract Configuration and Symfony Internals away as much as possible to give you a quick start and lift the heavy work for you.
      The main Goal is to give an easy path to follow an MVC Approach during development with ProcessWire and open up the available eco-system.
      You can find the GitHub Repo and more Information here: https://github.com/Luis85/symprowire
      The Symprowire Wiki https://github.com/Luis85/symprowire/wiki How to create a simple Blog with Symprowire https://github.com/Luis85/symprowire/wiki/Symprowire-Blog-Tutorial Last Update
      16.07.2021 // RC 1 v0.6.0 centralized ProcessWire access trough out the Application by wrapping to a Service https://github.com/Luis85/symprowire/releases/tag/v0.6.0-rc-1 Requirements
      PHP ^7.4 Fresh ProcessWire ^3.0.181 with a Blank Profile Composer 2 (v1 should work, not recommended) The usual Symfony Requirements Features
      Twig Dependency Injection Monolog for Symprowire Support for .env YAML Configuration Symfony Console and Console Commands Symfony Webprofiler Full ProcessWire access inside your Controller and Services Webpack Encore support Caveats
      Symfony is no small Framework and will come with a price in terms of Memory Usage and added Overhead. To give you a taste I installed Tracy Debugger alongside to compare ProcessWire profiling with the included Symfony Webprofiler

      So in a fresh install Symprowire would atleast add another 2MB of Memory usage and around 40ms in response time, should be less in production due to the added overhead of the Webprofiler in dev env
    • 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 tcnet
      PageViewStatistic for ProcessWire is a module to log page visits of the CMS. The records including some basic information like IP-address, browser, operating system, requested page and originate page. Please note that this module doesn't claim to be the best or most accurate.
      One of the biggest advantage is that this module doesn't require any external service like Google Analytics or similar. You don't have to modify your templates either. There is also no Javascript or image required.
      There is only one disadvantage. This module doesn't record visits if the browser loads the page from its browser cache. To prevent the browser from loading the page from its cache, add the following meta tags to the header of your page:
      <meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate" /> <meta http-equiv="Pragma" content="no-cache" /> <meta http-equiv="Expires" content="0" /> How to use
      The records can be accessed via the Setup-menu of the CMS backend. The first dropdown control changes the view mode.

      Detailed records
      View mode "Detailed records" shows all visits of the selected day individually with IP-address, browser, operating system, requested page and originate page. Click the update button to see new added records.

      Cached visitor records
      View modes other than "Detailed records" are cached visitor counts which will be collected on a daily basis from the detailed records. This procedure ensures a faster display even with a large number of data records. Another advantage is that the detailed records can be deleted while the cache remains. The cache can be updated manually or automatically in a specified time period. Multiple visits from the same IP address on the same day are counted as a single visitor.

      Upgrade from older versions
      Cached visitor counts is new in version 1.0.8. If you just upgraded from an older version you might expire a delay or even an error 500 if you display cached visitor counts. The reason for this is that the cache has to be created from the records. This can take longer if your database contains many records. Sometimes it might hit the maximally execution time. Don't worry about that and keep reloading the page until the cache is completely created.
      Special Feature
      PageViewStatistic for ProcessWire can record the time a visitor viewed the page. This feature is deactivated by default. To activate open the module configuration page and activate "Record view time". If activated you will find a new column "S." in the records which means the time of view in seconds. With every page request, a Javascript code is inserted directly after the <body> tag. Every time the visitor switches to another tab or closes the tab, this script reports the number of seconds the tab was visible. The initial page request is recorded only as a hyphen (-).

      New in version 1.1.0
      A new feature comes with version 1.1.0 which offers to record user names of loggedin visitors. Just activate "Record user names" and "Record loggedin user" in the module settings.
      You can access the module settings by clicking the Configuration button at the bottom of the records page. The settings page is also available in the menu: Modules->Configure->ProcessPageViewStat.
      This module uses the IP2Location database from: http://www.ip2location.com. This database is required to obtain the country from the IP address. IP2Location updates this database at the begin of every month. The settings of ProcessPageViewStat offers the ability to automatically download the database monthly. Please note, that automatically download will not work if your webspace doesn't allow allow_url_fopen.
      This module uses DragScroll. A JavaScript available from: http://github.com/asvd/dragscroll. Dragscroll adds the ability in view mode "Day" to drag the records horizontally with the mouse pointer.
      This module uses the PHP class parseUserAgentStringClass available from: http://www.toms-world.org/blog/parseuseragentstring/. This class is required to filter out the browser type and operating system from the server request.
    • By clsource
      Inertia Adapter ProcessWire Module
      Hello! Long time no see.
      I created this module so you can use Inertia.js (https://inertiajs.com/) with ProcessWire.
      Inertia allows you to create fully client-side rendered, single-page apps, without much of the complexity that comes with modern SPAs. It does this by leveraging existing server-side frameworks.
      Inertia isn’t a framework, nor is it a replacement to your existing server-side or client-side frameworks. Rather, it’s designed to work with them. Think of Inertia as glue that connects the two. Inertia comes with three official client-side adapters (React, Vue, and Svelte).
      This is an adapter for ProcessWire. Inertia replaces PHP views altogether by returning JavaScript components from controller actions. Those components can be built with your frontend framework of choice.
      - https://github.com/joyofpw/inertia
      - https://github.com/joyofpw/inertia-svelte-mix-pw
      - https://inertiajs.com/

    • By sms77io
      Hi all,
      we made a small module for sending SMS via Sms77.io. It supports sending to one and multiple users.
      You can download it from GitHub and follow the instructions on how to install it - it is quite easy. An API key is required for sending, get yours for free @ Sms77 and receive 0,50 €.
      Hope this helps somebody and we are open for improvement suggestions!
      Best regards
  • Create New...