pwFoo

FrontendUser: login, logout and register users / members

Recommended Posts

it was actually the same line; i can check more, but all i did was replace that line and then got the same exact error on the same line, but line 65, because of the added 2 lines

Share this post


Link to post
Share on other sites

I think empty() can't handle method calls and objects.

In the evening I'll take a look and fix it.

Thanks for feedback and testing!!! :)

Share this post


Link to post
Share on other sites

Hi pwFoo, I'm messing around with your module and it's great!

But now I'm trying to add custom fields to the user registration form and I can't seem to get it working. My code is this:

<?php
$fu = $modules->get('FrontendUser');
$myField = $fields->get(139);
echo $fu->register(array('username', 'email', 'password', $myField), $pages->get("template=home")->httpUrl);
?>

I'm 100% certain that the $myField variable is not empty too. Is this a bug or am I doing something wrong?

Share this post


Link to post
Share on other sites

Hi Fester,

You have to add an Inputfield. See example.

 // Create form field
$myField = $modules->get('InputfieldText');

Share this post


Link to post
Share on other sites

it was actually the same line; i can check more, but all i did was replace that line and then got the same exact error on the same line, but line 65, because of the added 2 lines

I shouldn't post workarounds and fixes in hurry...  :rolleyes:

It's a missing feature with php < 5.5

Note:
Prior to PHP 5.5, empty() only supports variables; anything else will result in a parse error. In other words, the following will not work: empty(trim($name)). Instead, use trim($name) == false.

So I removed one method call... but there are TWO  :-[

Maybe this fix will work, because it's without an method call. But I don't know if php <5.5 empty() can handle object properties...

At the moment I haven't a php 5.3 test env, so maybe it works for you and you can report back here ;)

//if (empty(wire('session')->get('registerStep'))) {
$session = wire('session'); 
if (empty($session->registerStep)) {

If the PW alternate syntax ($session->registerStep) shouldn't work with empty() isset could work.

//if (empty(wire('session')->get('registerStep'))) {
$session = wire('session'); 
if (!isset($session->registerStep)) {

Share this post


Link to post
Share on other sites

Just a note to all having to deal with a host that only offers 5.3: demand better service or switch hosts! It's not anything special these days to use multiple PHP versions on a Linux distro, newer than the one in the distro's repository. 5.3 is EOL for almost a year and simply a security catastrophe waiting to happen.

Bottom line: any host that forces 5.3 on you is inept and not worthy of your/your client's money.

Share this post


Link to post
Share on other sites

PW 2.x requires php 5.3. So I wouldn't increase the requirements by my module...

Just a note to all having to deal with a host that only offers 5.3: demand better service or switch hosts! It's not anything special these days to use multiple PHP versions on a Linux distro, newer than the one in the distro's repository. 5.3 is EOL for almost a year and simply a security catastrophe waiting to happen.

Bottom line: any host that forces 5.3 on you is inept and not worthy of your/your client's money.

but you're right! php 5.3 is EOL and an modern hosting should offer a new(er) version or multiple php versions.

Share this post


Link to post
Share on other sites

I'm not running 5.3 on any of my new/development sites, its all 5.4; we just released a module (AceExtended) that is for 5.4+; i think it's fine, just put that in the requirements and don't use any> 5.4 features?

Apache/2.2.23 (Unix) mod_ssl/2.2.23 OpenSSL/0.9.8r DAV/2 PHP/5.4.10

Share this post


Link to post
Share on other sites

Habe you tested this?

I shouldn't post workarounds and fixes in hurry... :rolleyes:

It's a missing feature with php < 5.5

Note:
Prior to PHP 5.5, empty() only supports variables; anything else will result in a parse error. In other words, the following will not work: empty(trim($name)). Instead, use trim($name) == false.
So I removed one method call... but there are TWO :-[

Maybe this fix will work, because it's without an method call. But I don't know if php <5.5 empty() can handle object properties...

At the moment I haven't a php 5.3 test env, so maybe it works for you and you can report back here ;)

//if (empty(wire('session')->get('registerStep'))) {
$session = wire('session'); 
if (empty($session->registerStep)) {
If the PW alternate syntax ($session->registerStep) shouldn't work with empty() isset could work.
//if (empty(wire('session')->get('registerStep'))) {
$session = wire('session'); 
if (!isset($session->registerStep)) {

Share this post


Link to post
Share on other sites

yep, tried changing everything, isset and nothing works.. WSOD all the way. Maybe you can setup a temp account on lightning.pw so that your module can be tested with some more widely used version of php?

Share this post


Link to post
Share on other sites

it works for me... i just change all the

empty(wire('session')->get('registerStep'))

to

$session = wire('session');
!isset($session->registerStep)

there alteast 4 errors are there....

post-3301-0-43193400-1432100355_thumb.pn

Share this post


Link to post
Share on other sites

Last update should be php 5.3 compatible. I just removed empty() calls like that.

//if (empty(wire('session')->get('registerStep'))) {
if (!wire('session')->get('registerStep')) {

//if (!empty(wire('session')->get('registerStep')) && wire('session')->get('registerEmail') !== $form->fhValue('email')) {
if (wire('session')->get('registerStep') && wire('session')->get('registerEmail') !== $form->fhValue('email')) {

No warnings or errors with php 5.5. 

Would be great if somebody could test the new version 0.8.6 with php 5.3.

@naldrocks98

Thank You for your feedback! :)

Could you explain which errors you mean? Error mesage?

  • Like 1

Share this post


Link to post
Share on other sites

Hi Fester,

You have to add an Inputfield. See example.

 // Create form field
$myField = $modules->get('InputfieldText');

this seems to be working for me:

// Create form field
$last_name = $modules->get('InputfieldText');
$last_name->label = 'Last Name';
$last_name->attr('id+name', 'last_name');
$last_name->required = 1;

Share this post


Link to post
Share on other sites

@Macrura, @Fester

Right. You have to use an Inputfield instead of an "Field".

Take a look at this topic how to use the PW form api.

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

After field is added you need a hook to handle the input value (sanitize, maybe additional processing and add to userObj).

For example see usernameRegister() and passwordRegister().

Share this post


Link to post
Share on other sites

I'm getting this error when trying to use the register form

Error: Exception: Method FrontendUser::attr does not exist or is not callable in this context (in /Volumes/Docs/MAMP/htdocs/processwire_xys/wire/core/Wire.php line 350)

not sure what the issue could be; tried various things - has anyone got a registration form working with FU yet, and if so could you post steps?

TIA

.. also - i noticed you are maybe using using $sanitizer->username() but it seems to be deprecated in favor of pageName (?) http://cheatsheet.processwire.com/sanitizer/properties-and-methods/sanitizer-username-value/

Share this post


Link to post
Share on other sites

Module and sub module should work as is.

"attr()" is removed during PHP 5.3 compatibility changes.

Just use $fu->userObj or $fu->form inside the template. Inside a hook wire('fu') instead of $fu works with PHP 5.3+

Share this post


Link to post
Share on other sites

@pwFoo - thanks for the reply & info.

i'll see if i can make it work, and carry on testing the various features.

in terms of sanitizing/processing additional custom fields on a registration form, any tips on how and where in the process to do that?

thanks again

Share this post


Link to post
Share on other sites

Sanitize field value is a FormHelper feature ;)

Set sanitizer to field as an additional attribute

$emailField->fhSanitizer = 'email';

Get sanitized value after form processing / submitted

$value = $fu->form->fhValue('emailField')

Change sanitizer if needed...

$value = $fu->form->fhValue('emailField', 'pageName')

Or just do it without FormHelper inside a field processInput hook

// hook after field processed (form need to be submitted)
$myField->addHookAfter('processInput', function($event) {
  $currentField = $event->object;
  
  $value = $currentField->value;
  §sanitizedValue = wire('sanitizer')->pageName($value);

  // Do ...
}

You can take a look in each FU field (like username field for registration) to see some examples. ;)

Or at the wiki plugin examples (register, login).

Set additional user field "nickname" based on username during registration (plugin).

Just hook before "save", generate the value and set it to the userObj. "userObj" is a temp object of type User. All existing fields will be saved.

$fu->addHookBefore('save', function($event) {
    $form = wire('fu')->form;

    if(!count($form->getErrors())) {
        wire('fu')->userObj->nickname = $form->fhValue('username', 'text');
    }
});

You need an additional field with user input? Add a field with sanitizer and a processing hook... Same as username field ;) So you can use it as starting point

        $myField = $modules->get('InputfieldText');
        $myField->label = $this->_('MyLabel');
        $myField->attr('id+name', 'MyField');
        //$myField->required = 1;
        $myField->fhSanitizer = 'text';
        // Call hook after field is processed by PW form api
        $myField->addHookAfter('processInput', function($event) {
            $field = $event->object;

            // Value will be sanitized as text with "$sanitizer->text()"
            $mySanitizedCustomInput = wire('fu')->form->fhValue($field->name);
            
            // Do ...
           
            // Example: Add value to user during registration
            wire('fu')->userObj->myField = $mySanitizedCustomInput;

            // Need to set an field error?
            // $field->error('Custom field has an error...');
        });

        // Define the field before you call FU and add it as additional field...
        $fu->register(array('username', 'email', 'password', $myField));

If You need more examples or have a plugin idea just post it here.

  • Like 1

Share this post


Link to post
Share on other sites

Question... let's say I want users only with a particular role to be able to log in, how would I go about that using hooks?

Current code:

$fu = $modules->get('FrontendUser');
$fu->login();
$fu->login(array('username', 'password', 'persist', 'forgot'));
$fu->process($pages->get("/")->url);
echo $fu->render();

Share this post


Link to post
Share on other sites

Should be done with several hooks.  

For example hookAfter field username "processInput", get the user object by username and check the role. If role is missing, just set a error to the field and login will fail with a custom error message. 

Or take a look at this example. 
https://bitbucket.org/pwFoo/frontenduser/wiki/Login%20extensions%20and%20plugins

Instead of change the login name to email address or nickname just get the user and check the role. Is the role missing, just replace the hooked method. The FrontendUser::auth method returns (===) "true" if login was successful. So just replace and set an error message, that is displayed next to the submit button.

$event->replace = true;
$event->return = "Login failed! Missing required user role!";

Share this post


Link to post
Share on other sites

Updated 0.8.7

  • config email type html | text added to FrontendUserRegisterEmailValidation
  • changed username sanitizer to pageName

Share this post


Link to post
Share on other sites

Maybe I'm a bit daft, but I can't figure out how to create a logout link. The regular ?logout=1 doesn't seem to work.

So I'm looking at $fu->logout($redirectDestination); but don't know what to do with it. Plz help :undecided:

Edit: bah, I figured it out:

if($user->isLoggedin()) {
  $fu = $modules->get('FrontendUser');
  if (isset($_GET['logout'])) $fu->logout($redirectDestination);
  echo "<a href='?logout'>Logout</a>";
}

Thanks again for the great modules :)

Edit: bonus tip: $redirectdestination must be a url, so if you want to redirect to the front page after registering:

$redirectDestination = $pages->get(1)->url;
  • Like 1

Share this post


Link to post
Share on other sites

It's designed in order to avoid the need URL parameters ;)

So you can create a template / page logout or just use your code above.

Share this post


Link to post
Share on other sites

Hi Beluga,

I don't like captcha solutions and so I haven't used the recaptcha module. I use my emailValidation plugin (shipped with FrontendUser module).

echo $fu->register(array('username', 'email', 'emailValidation', 'password'), $redirectDestination);

It validates the email address as an additional registration step before the user will be added. 

If recaptcha needs an additional form field just add the form field object

echo $fu->register(array('username', 'email', 'password', $myRecaptchaField), $redirectDestination);

Add a hook to the form processing (a $form->addHookAfter 'processInput' should do it...) to execute "verifyResponse". If the recaptcha validation isn't ok just set a field error inside the hook to stop the user registration process. 

$form->fhSubmitBtn->error('reCAPTCHA validation not ok!');

I hope that will help you to figure it out, because I'm in hurry and have no time to take a closer look at it.

Share this post


Link to post
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 blad
      Hi guys!
      I just uploaded a module to explore files based on elFinder. By default it will show the "Files" folder.
      Screenshots:

      Video:
       
      To do:
       More options To fix:
       The function of rotating or scaling an image fails  Image editors V 1.01 (view issue)
      Fixed the bug working with the Multi-Language support ( translation of folders ). Fixed the name of elfinder.en  Github:
      https://github.com/LuisSantiago/ProcessElFinder/
      I hope you like it.
    • By BitPoet
      I'm really in love with FormBuilder, but the one thing missing to match all my end users' expectations were repeatable field groups. Think repeaters, in ProcessWire terms. Our primary application of PW is our corporate intranet, so "lines" of fields are quite common in the forms I build. We have all kinds of request forms where the information for a varying number of colleagues needs to be entered (from meal order to flight booking request) and where it is simply impractical to send a form for each, and I don't want to clutter my forms with multiple instances of fields that may only get used ten percent of the time.
      That's why I started to build FormBuilderMultiplier (link to GitHub).
      What it does:
      Adds an option to make a regular Fieldgroup repeatable Lets you limit the number of instances of a Fieldgroup on the form Adds an "Add row" button the form that adds another instance of the Fieldgroup's fields Adds a counter suffix at the end of every affected field's label Stores the entered values just like regular fields Makes the entered values available in preview and email notifications Supports most text based fields, textareas and selects (really, I haven't had enough time to test all the available choices yet) What it doesn't do (yet):
      Support saving to ProcessWire pages (i.e. real Repeaters) I haven't tested all the validation stuff, Date/Time inputs etc. yet, but since I'm utterly swamped with other stuff at work, I didn't want to wait until I have it polished. Any feedback is welcome. There might also be some issues with different output frameworks that I haven't encountered yet. The forms I work with mostly use UIKit.
      Status:
      Still alpha, so test well before using it in the field.
      Known issues:
      When rows are added, the form's iframe needs to be resized, which isn't completely clean yet.
      How it works:
      The Fieldgroup settings are added through regular hooks, as is the logic that adds the necessary field copies for processing the form and displaying previews.
      "Multiplied" field instances are suffixed with _NUM, where NUM is an incremental integer starting from 1. So if you have add two fields named "surname" and "givenname" to a fieldgroup and check the "multiply" checkbox, the form will initially have "surname_1" and "givenname_1" field (I'm still considering changing that to make the risk to shoot oneself into the foot by having a regular "surname_1" field somewhere else in the form less likely).
      When a "row" is added, the first row is cloned through JS and the counter in the fields' IDs, names and "for" attributes as well as the counter in the label are incremented before appending the copies to the Fieldset container in the form.
      To keep backend and frontend in sync, a hidden field named [name of the fieldset]__multiplier_rows is added to the form. Both the backend and the frontend script use this to store and retrieve the number of "rows".
      ToDo:
      Naturally, add the option to store the data in real repeaters when saving to pages. Do a lot of testing (and likely fixing). Make a few things (like the "Add row" button label etc.) configurable in field(set) context. Add a smooth API to retrieve the multiplied values as WireArrays. The mandatory moving screenshot:

    • By MoritzLost
      Hello there,
      I'm working on a tiny textformatter module that searches the text for titles of other pages on your site and creates hyperlinks to them. I'm not sure if something like this exists already, but I haven't found anything in the module directory, so I wrote my own solution 🙂
      It's not properly tested yet and is still missing some functionality I would like to implement, so at the moment it should be considered in BETA. Features include limiting the pages that will get searched by template, and adding a custom CSS class to the generated hyperlinks. As I'm writing this I noticed that it will probably include unpublished and hidden pages at the moment, so yeah ... it's still in development alright 😅
      You can download the module from Github:
      https://github.com/MoritzLost/TextformatterPageTitleLinks
      There's some more information in the readme as well.
      Anyway, let me know what you think! I'm happy about any feedback, possible improvements or ideas on how to improve the module. Cheers.
    • By adrian
      This module provides a way to rapidly generate Page fields and the required templates and pages for use as a drop down select (or any other Page field type).
      This module will let you create a full page field setup in literally a few seconds 
      To use, run Page Field Select Creator from the Setup Menu
      Enter a Field Title, eg: Room Types Select Options - These will become the child pages that will populate the page field select options. There are two different options.
       
      Option 1. TITLE FIELD ONLY - enter one option per line, eg:
       
      Single
      Double
      Suite
       
       
      Option 2. MULTIPLE FIELDS - the first line is used for the field names and the first field must be 'Title'. Subsequent lines are the values for the fields, eg:
       
      Title, Number of Beds, Number of People, Kitchen Facilities
      Single, 1, 1, Fridge Only
      Double, 2, 2, Fridge Only
      Suite, 3, 6, Full Kitchen
        Choose the parent where the page tree of options will be created, eg a hidden "Options" parent page Select a "Deference in API as" option depending on your needs Choose the input field type Check whether "Allow new pages to be created from field?" should be enabled. As an example, if you entered "Room Types" as the field title, you would end up with all of the following automatically created:
      a fully configured page field called: room_types MULTIPLE FIELDS OPTION - 3 additional fields - number_of_beds, number_of_people, kitchen a parent template called: room_types a child template called: room_types_items (with either just a title field, or with the 3 additional fields as well) a parent page called: Room Types a series of child pages named and titled based on the per line entries in the Select Options textarea The templates are configured such that the "room_types_items" child template can only have the main "room_types" template as a parent, and vice versa.

      Then all you have to do is add the newly created page field to any template you want and you're ready to go!
       
      You can grab it from:
       
      Modules directory: http://modules.processwire.com/modules/process-page-field-select-creator/
      Github: https://github.com/adrianbj/ProcessPageFieldSelectCreator
       

    • By bernhard
      WHY?
      This module was built to fill the gap between simple $pages->find() operations and complex SQL queries.
      The problem with $pages->find() is that it loads all pages into memory and that can be a problem when querying multiple thousands of pages. Even $pages->findMany() loads all pages into memory and therefore is a lot slower than regular SQL.
      The problem with SQL on the other hand is, that the queries are quite complex to build. All fields are separate tables, some repeatable fields use multiple rows for their content that belong to only one single page, you always need to check for the page status (which is not necessary on regular find() operations and therefore nobody is used to that).
      In short: It is far too much work to efficiently and easily get an array of data based on PW pages and fields and I need that a lot for my RockGrid module to build all kinds of tabular data.

      Basic Usage

       
      Docs & Download
      https://modules.processwire.com/modules/rock-finder/
      https://github.com/BernhardBaumrock/RockFinder
       
      Changelog
      180817, v1.0.6, support for joining multiple finders 180810, v1.0.5, basic support for options fields 180528, v1.0.4, add custom select statement option 180516, change sql query method, bump version to 1.0.0 180515, multilang bugfix 180513, beta release <180513, preview/discussion took place here: https://processwire.com/talk/topic/18983-rocksqlfinder-highly-efficient-and-flexible-sql-finder-module/