Jump to content

FrontendUser: login, logout and register users / members


pwFoo

Recommended Posts

Hi,

You could check the url param to render the login / register form OR the password reset content?

I don't use register and login at the same page. I use different pages and urls like /login and /register.

Forgot Password is just the core module. You also could disable the integration and implement / load it with custom code.

Link to comment
Share on other sites

  • 3 weeks later...

Hi pwFoo,

I think I have discovered a small part for improvement towards the user.

Currently, when a user chooses a username containing umlauts and/or mixed case (like: MötörCode), the first email will display the username as given, since it was sanitized by "text" only.

in the next step, the username in the session (which still has umlauts and mixed case chars) will be put inside the username field.

If the user now chooses a password and submits, this name will be sanitized by "pageName" - which in the above example will result in "mtrcode".

This username is correctly displayed in the second and final E-Mail.

Since PW stores username as a page pagename is correct, but I think it should be displayed as such in the first email as well.

And I would propose to use sanitizer "pageNameTranslate", since then the above would result in "moetoercode".

Regarding the first email, I think FrontendUserRegisterEmailValidation.module line 90:

wire('session')->set('registerUsername', $form->fhValue('username', 'text'));

changed to

wire('session')->set('registerUsername', $form->fhValue('username', 'pageNameTranslate'));

would do.

For the second part, I've hooked into before save,

$fu->addHookBefore('save',function($event){
        $event->object->userObj->name = $event->object->form->fhValue('username','pageNameTranslate');
    });

but I'm not sure where this would be covered best in the module's process.

Let me know what you think, unsure about the "username" part, since maybe it would be of greater flexibility to have a "nickname" field (which can keep up and lowercase and umlauts), independently from the "name" field - but even then "pageNameTranslate" would make for better page names in the backend for umlauterists. :-)

EDIT

ah, I just re-read the documentation on bitbucket, and in the plugin section I see you have covered the nick name case. Nice! :-)

Cheers,

Tom

  • Like 1
Link to comment
Share on other sites

  • 4 weeks later...

Hey Guys,

I just installed the module and it seems to work since it's actually outputting a register form, but I don't have any styling to go with it?

The .css files in the modules directory are all but empty, just like the .js files, I also redownloaded the master file outside of processwire

and it doesn't contain any styling either. I read that It's possible to overwrite the styling by putting files with the same names as the ones

in the modules directory in templates/FrontendUser,  but the originals are pretty much empty, so what is there to overwrite?

Also, I can't find where I could change sentences like:

"Password must be at least 6 characters and have at least 1 letter and 1 digit. Password may not have whitespace."

Can anybody help me out?

thanx! :)

Bram

Link to comment
Share on other sites

Hello,

module uses the PW form api and isn't styled:

https://processwire.com/talk/topic/2089-create-simple-forms-using-api/

https://processwire.com/talk/topic/6184-form-and-css/

Just overwrite the (emtpy) style and script files ;)

Link to the documentation:

Styles, scripts & templates

The error message is defined by the form api / inputfield. You can overwrite it too.

https://processwire.com/talk/topic/4659-customizing-error-messages-for-inputfields/

Regards

  • Like 1
Link to comment
Share on other sites

Hi pwFoo,

Thanks for your reply! I checked out Soma's code and I understand it for the most part, but I find it hard to

translate the pieces of code for FrontEndUser to his examples since I don't know whether to use the same

code, or change $form to $fu and so on... So i was hoping you could help me out abit.

I implemented a register form already, and styled it myself O:)

I'm redirecting that form to /profile when its submitted succesfully. 

Now it does create a new user with the right attributed ( a role ) but

it doens't log the user in. And I don't know how to set this up.

Also it would be nice to send the new User a small confirmation email 

with his email and password. Is there any change you could point me

in the right direction for this? I would greatly appreciate any help with this :)

Thanx!

Bram

Link to comment
Share on other sites

You could use the email verification plugin (https://bitbucket.org/pwFoo/frontenduser/wiki/Documentation#markdown-header-register) or use PW hooks to add your own features (that's the way FrontendUser is built).

https://bitbucket.org/pwFoo/frontenduser/wiki/Register%20extensions%20and%20plugins

https://bitbucket.org/pwFoo/frontenduser/wiki/Login%20extensions%20and%20plugins

Send an email after user registration just use the PW addHookAfter (PW hooks) the method FrontendUser::save to send an email with WireMail.

All FrontendUser module messages should be translatable. For example ("$this->_()"):

    /**
     * Save the temp User object
     * @param User $user Temp User object to save
     * @return boolean Sucessful (true) saved or not (false)
     */
    protected function ___save($user) {
        if (empty($user->name) || empty($user->email) || $user->pass->hash == '') {
            return $this->_('Register process unexpected failed!');
        }
        if ($user->save()) {
            return true;
        }
        return $this->_('User registration failed!');
    }

Registered user won't logged in automatically, but you could add a hook to do it. addHookAfter FrontendUser::save and execute $this->session->login() or the FrontendUser method auth()

  • Like 3
Link to comment
Share on other sites

hi pwFoo!

Thanks for the reply! I've been dabbling around with it for hours but I can't get it to work  :huh:

why is this so fucking hard? :( :( I just want it to log in after registration and it simply doesn't.

$fu = $modules->get('FrontendUser');

// prepare register form
$fu->register();

// Default parameter
$fu->register(array('username', 'email', 'password'));

// De rol "ZZP" toevoegen aan gebruiker
$fu->addHookBefore('save', function($event) {
    $user = wire('fu')->userObj;
    $user->addRole('zzp');
});

// Login na succesvolle aanmelding
$fu->addHookAfter('save', function($event) {
	$this->session->login();	
});

// Additional email pre-register validation plugin (built-in)
//$fu->register(array('username', 'email', 'emailValidation', 'password'));

// Redirect destination:
$redirect = $pages->get('/zzp-ers/gegevens/')->url;

// process register / form submit
$fu->process($redirect);

// output register form
echo $fu->render();

This is de code i've been using and on the page "gegevens" I just show the username if logged in, and "You're not logged in" when

users aren't.

Could somebody please show me how to get this to work?

thanks!

Gr,

Bram

Link to comment
Share on other sites

// prepare register form
$fu->register();

// Default parameter
$fu->register(array('username', 'email', 'password'));

Remove one off the lines above. You prepare the form twice ;)

Take a look at the cheatsheet / API documentation. login()  need login credentials!

$session->login($name, $pass)

So you have to prepare username and password variables before you call login method.

Link to comment
Share on other sites

  • 2 weeks later...

Thanks for the hint in the right direction,

after a few hours of searching I finally found the right syntax somewhere in the forum.

I couldn't find this specific call anywhere in the documentation on FrontEndUser?

This is how I logged in my user after a successfull login:

// Login after succesfull registration
$fu->addHookAfter('save', function($event) {
    $user = $event->object->form->fhValue('username','text');
    $pass = $event->object->form->fhValue('password','text');
    $this->session->login($user, $pass);	
});

  • Like 1
Link to comment
Share on other sites

  • 3 weeks later...

Hi Guys,

I've been trying to translate the registration form to dutch and I've managed to do so with Username and Password.

But I don't know which field to call for the password description field. 

Does anybody know which field to point to to change this?

"Password must be at least 6 characters and have at least 1 letter and 1 digit. Password may not have whitespace."

$usernameField = $fu->form->get("username");
$usernameField->label = "Gebruikersnaam";

$passwordField = $fu->form->get("password");
$passwordField->label = "Wachtwoord";

Thanks! :)

Bram

Link to comment
Share on other sites

Before you can modify fields the login / register form have to be created first by execute $fu->login() method with or without optional parameters.

After that you should be able to get form / fields and modify as needed.

Link to comment
Share on other sites

hi pwFoo,

thanks for your reply. I have indeed executed the register en login forms, and they work perfectly fine, the only problem I have is that I don't know which field to target to be able to change the password description text. Would you happen to know which one that is?

Thanks :)

Bram

Link to comment
Share on other sites

Hi,

fields are just PW form api fields. should be something like

$usernameField = $fu->form->get("username");
$usernameField->description = "this is my description";

Take a look here: https://processwire.com/talk/topic/7903-add-description-to-form-field-object-method-missing/

There are many great posts about PW form api here in the forums. Also link to Soma's post again ;)

https://processwire.com/talk/topic/2089-create-simple-forms-using-api/

Link to comment
Share on other sites

Yes! SOLVED

This is what I was looking for, quite obvious! But thanks alot :)

// update password field attributes in a login or registration form

$passwordField = $fu->form->get("password");
$passwordField->label = "New password label";
$passwordField->description = "Password description";
  • Like 1
Link to comment
Share on other sites

  • 2 weeks later...

I've to write a little love letter!

I just play the whole day with your modules and i've to say that i'm very very overtaken by your simple modules with a real big benefit to rule API forms and user managment things!

Thumbs up for your input on this topic!

Until now, all i've done worked and i will use this for my first bigger community project website (about several hundred frontend users) and will report how fu() will work.

But this modules follow PW basic rules - simple - easy to use so i don't see any rough edges...;)

Just wanna say a real big thank you and make the suggestion to put the modules from "alpha" state to "beta" ...since many things are fixed the last few months and i think theese modules are indeed in production use...

Best Regards mr-fan

  • Like 3
Link to comment
Share on other sites

Thanks!  :D

FormHelper and FrontendUser are my first PHP modules. Written with a really basic knowledge of PHP and also PW (just after my first steps with it ;) ). That's why the first approach ignored the PW hooks and used custom code for that...

I learned how to use the power of the PW API and PW hooks. I surprised about the powerful and simple module creation with the PW API and PW hooks!

At the moment I moved to some other topics (Linux, Docker, change IDE,  ...). But I'll come back to PW soon, because I love PW and also the awesome community here!

  • Like 6
Link to comment
Share on other sites

How do I check whether the user who wants to register has entered a username that does not contain accents, spaces, and any other characters that are not allowed? Can it be achieved server-side with a hook, or do we have to use something like "InputfieldPageName.js" from the core on the frontend?

The issue I'm having is that if someone for example enters a space in his or her username, it will be converted into a dash (which they wouldn't realize unless we indicate it to them specifically), and they wouldn't understand why they can't log in after registering.

Link to comment
Share on other sites

  • 2 weeks later...

Oh i forgot one little problem...you mentioned....https://processwire.com/talk/topic/9811-frontenduser-login-logout-and-register-users-members/page-6#entry108578

i changed the module that the registration with emailverification works again:

// Load the plain / html email templates
$emailContentHtml =
'<html>
	<body>
		<p>'.$vars['content'].'</p>
		<!-- empty line and comment only lines works as a linebreak with plain emails -->
		<p>Internetseite: <strong>'.wire('config')->httpHost.'</strong></p>

		<p>Benutzername: <strong>'.$vars['username'].'</strong><br />
		Email Adresse: <strong>'.$vars['email'].'</strong></p>

		<p>Freischaltcode: <strong>'.$vars['token'].'</strong></p>

		<p>Link zur Registrierung:<br />
		<strong>'.$vars['url'].'</strong></p>
	</body>
</html>';

so the mailbody is generated directly in the module and not loaded via render->template - i think there is a little change in the 3.x render methode...so it doesn't work?

@pwFoo i'm glad to help here since i use this module for a bigger project and dig deep into - for now i've a little deadline but after it i could provide some snippets and detailed examples of usage...

Best regards mr-fan

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • 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
      Documentation
      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

       
      Limitations:
      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.
      Requirements:
      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
      https://github.com/SkyLundy/Fluency-Translation/archive/main.zip
      Github repository:
      https://github.com/SkyLundy/Fluency-Translation
      File issues and feature requests here (your feedback and testing is greatly appreciated):
      https://github.com/SkyLundy/Fluency-Translation/issues
       
      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.
      Advantages
      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.
      Disadvantages
      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.
      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.
      IP2Location
      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.
      Dragscroll
      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.
      parseUserAgentStringClass
      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.
      Description
      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.
      Links
      - https://github.com/joyofpw/inertia
      - https://github.com/joyofpw/inertia-svelte-mix-pw
      - https://inertiajs.com/
      Screenshots


       
    • 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
      André
×
×
  • Create New...