Jump to content
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 MoritzLost
      This is a new module that provides a simple solution to clearing all your cache layers at once, and an extensible interface to perform various cache-related actions.
      The simple motivation behind this module was that I was tired of manually clearing caches in several places after deploying a change on a live site. The basic purpose of this module is a simple Clear all caches link in the Setup menu which clears out all caches, no matter where they hide. You can customize what exactly the module does through it's configuration menu:
      Expire or delete all cache entries in the database, or selectively clear caches by namespace ($cache API) Clear the the template render cache. Clear out specific folders inside your site's cache directory (/site/assets/cache) Refresh version strings for static assets to bust client-side browser caches (this requires some setup, see the full documentation for details). This is the basic function of the module. However, you can also add different cache management action through the API and execute them through the module's interface. For this advanced usage, the module provides:
      An interface to see all available cache actions and execute them. A system log and logging output on the module page to see verify what the module is doing. A CacheControlTools class with utility functions to clear out different caches. An API to add cache actions, execute them programmatically and even modify the default action. Permission management, allowing you granular control over which user roles can execute which actions. The complete documentation can be found in the module's README.
      Beta release
      Note that I consider this a Beta release. Since the module is relatively aggressive in deleting some caches, I would advise you to install in on a test environment before using it on a live site.
      Let me know if you're getting any errors, have trouble using the module or if you have suggestions for improvement!
      In particular, can someone let me know if this module causes any problems with the ProCache module? I don't own or use it, so I can't check. As far as I can tell, ProCache uses a folder inside the cache directory to cache static pages, so my module should be able to clear the ProCache site cache as well, I'd appreciate it if someone can test that for me.
      Future plans
      If there is some interest in this, I plan to expand this to a more general cache management solution. I particular, I would like to add additional cache actions. Some ideas that came to mind:
      Warming up the template render cache for publicly accessible pages. Removing all active user sessions. Let me know if you have more suggestions!
      Links
      https://github.com/MoritzLost/ProcessCacheControl ProcessCacheControl in the Module directory

    • By joshua
      This module is (yet another) way for implementing a cookie management solution.
      Of course there are several other possibilities:
      - https://processwire.com/talk/topic/22920-klaro-cookie-consent-manager/
      - https://github.com/webmanufaktur/CookieManagementBanner
      - https://github.com/johannesdachsel/cookiemonster
      - https://www.oiljs.org/
      - ... and so on ...
      In this module you can configure which kind of cookie categories you want to manage:

      You can also enable the support for respecting the Do-Not-Track (DNT) header to don't annoy users, who already decided for all their browsing experience.
      Currently there are four possible cookie groups:
      - Necessary (always enabled)
      - Statistics
      - Marketing
      - External Media
      All groups can be renamed, so feel free to use other cookie group names. I just haven't found a way to implement a "repeater like" field as configurable module field ...
      When you want to load specific scripts ( like Google Analytics, Google Maps, ...) only after the user's content to this specific category of cookies, just use the following script syntax:
      <script type="optin" data-type="text/javascript" data-category="statistics" data-src="/path/to/your/statistic/script.js"></script> <script type="optin" data-type="text/javascript" data-category="marketing" data-src="/path/to/your/mareketing/script.js"></script> <script type="optin" data-type="text/javascript" data-category="external_media" data-src="/path/to/your/external-media/script.js"></script> <script type="optin" data-type="text/javascript" data-category="marketing">console.log("Inline scripts are also working!");</script> The type has to be "optin" to get recognized by PrivacyWire, the data-attributes are giving hints, how the script shall be loaded, if the data-category is within the cookie consents of the user. These scripts are loaded asynchronously after the user made the decision.
      If you want to give the users the possibility to change their consent, you can use the following Textformatter:
      [[privacywire-choose-cookies]] It's planned to add also other Textformatters to opt-out of specific cookie groups or delete the whole consent cookie.
      You can also add a custom link to output the banner again with a link / button with following class:
      <a href="#" class="privacywire-show-options">Show Cookie Options</a> <button class="privacywire-show-options">Show Cookie Options</button> This module is still in development, but we already use it on several production websites.
      You find it here: https://github.com/blaueQuelle/privacywire/tree/master
      Download: https://github.com/blaueQuelle/privacywire/archive/master.zip
      I would love to hear your feedback 🙂
      Edit: Updated URLs to master tree of git repo
       
    • By David Karich
      Admin Page Tree Multiple Sorting
      ClassName: ProcessPageListMultipleSorting
      Extend the ordinary sort of children of a template in the admin page tree with multiple properties. For each template, you can define your own rule. Write each template (template-name) in a row, followed by a colon and then the additional field names for sorting.
      Example: All children of the template "blog" to be sorted in descending order according to the date of creation, then descending by modification date, and then by title. Type:
      blog: -created, -modified, title  Installation
      Copy the files for this module to /site/modules/ProcessPageListMultipleSorting/ In admin: Modules > Check for new modules. Install Module "Admin Page Tree Multible Sorting". Alternative in ProcessWire 2.4+
      Login to ProcessWire backend and go to Modules Click tab "New" and enter Module Class Name: "ProcessPageListMultipleSorting" Click "Download and Install"   Compatibility   I have currently tested the module only under PW 2.6+, but think that it works on older versions too. Maybe someone can give a feedback.     Download   PW-Repo: http://modules.processwire.com/modules/process-page-list-multiple-sorting/ GitHub: https://github.com/FlipZoomMedia/Processwire-ProcessPageListMultipleSorting     I hope someone can use the module. Have fun and best regards, David
    • By dimitrios
      Hello,
      this module can publish content of a Processwire page on a Facebook page, triggered by saving the Processwire page.
      To set it up, configure the module with a Facebook app ID, secret and a Page ID. Following is additional configuration on Facebook for developers:
      Minimum Required Facebook App configuration:
      on Settings -> Basics, provide the App Domains, provide the Site URL, on Settings -> Advanced, set the API version (has been tested up to v3.3), add Product: Facebook Login, on Facebook Login -> Settings, set Client OAuth Login: Yes, set Web OAuth Login: Yes, set Enforce HTTPS: Yes, add "https://www.example.com/processwire/page/" to field Valid OAuth Redirect URIs. This module is configurable as follows:
      Templates: posts can take place only for pages with the defined templates. On/Off switch: specify a checkbox field that will not allow the post if checked. Specify a message and/or an image for the post.
      Usage
      edit the desired PW page and save; it will post right after the initial Facebook log in and permission granting. After that, an access token is kept.
       
      Download
      PW module directory: http://modules.processwire.com/modules/auto-fb-post/ Github: https://github.com/kastrind/AutoFbPost   Note: Facebook SDK for PHP is utilized.


×
×
  • Create New...