pwFoo

FrontendUser: login, logout and register users / members

Recommended Posts

Quote

The FrontendUser module is just based on form api, inputfields, hooks. PW native features. So if you know PW you know how to extend the module.

For someone just coming in from the Wordpress world it is tempting to look for a module/plugin that does everything out-of-the-box to avoid having to learn about the form API, hooks, PW native features, etc.

If I have to know all that before I get anything usable, I might as well skip your FrontendUser module + two required helper modules that may or may not be compatible with the latest PW version and just use those PW native features to put my own solution together.

  • Like 2

Share this post


Link to post
Share on other sites

I too had used wordpress a long long time ago, and even wrote a few plugins for the 2.x versions since there was nothing out of the box available for my needs. I dumped it because that square peg was being force-fit into the round "one size fits all" hole with each passing version at the cost of security. And more and more plugins were coming on board that didn't work, had no support, wanted payments, and embedded hidden ads without your knowledge.

I'm glad I came across ProcessWire because I can solve my needs any way I see fit; that proverbial skinned cat. As an example, I wrote my own front-end user management system simply because ProcessWire makes it easy to do so, and it does exactly what I want, and ProcessWire doesn't impose restrictions.

You don't have to write your own, however, as there are quite a few user management modules/code snippets available to you in this forum, but you are certainly welcome to do so. This community would welcome your contribution, and gladly assist you with its development.

One other option is to hire someone to develop your module(s) to your specifications (See the Jobs forum).

  • Like 1

Share this post


Link to post
Share on other sites
On 3/10/2017 at 2:55 PM, fbg13 said:

@modifiedcontent Works the same as everywhere else, you have a form, form gets submitted, you process it (do what you need with the values submitted).

I showed you how to save the values in a page, the same way you can create a user.


<?php
// $input->post->username same as $_POST["username"]
if($input->post->submit) {
    $u = new User();
    $u->name = $input->post->username;
    $u->email = $input->post->email;
    $u->pass = $input->post->password;
    $u->registrationDate = time();
    $u->addRole("member");
    $u->save();
}

 

I am about to ask a big, stupid question... having gone through 50 pages of user, login, registration stuff.  I can easily create a form - or use formbuilder - to create a simple registration form for a couple levels of users (roles = subscribers, contributors) and I can easily send those entries to a page structure like

 Pages  

 --- Users

------Subscribers

       -- Bill Smith, etc. 

------Contributors

       -- John Jones, etc.

This creates a directory of pages, assigned roles, and page access based on role, but this doesn't put those people into: ACCESS > USERS > 

My user data lives in Admin > Access > Users -- not in the document tree.  If I want to have user accounts, doesn't Bill Smith, in the example above, have to be in both locations? Or, at least Admin > Access > Users?  This is a conceptual problem, not a code problem... as a new user of PW,  I don't know where my logged in users are supposed to live -- and if I use a form, how to get them there.

 

Share this post


Link to post
Share on other sites

Your users actually live in page tree: Admin => Access => Users => User

So you can just create your users like that. Instead of $p = new Page(), just use $u = new User(); and you are good to go. No need to define template and parent in that case also, if I remember correctly.

PW also has possibilities to use different templates than user for users. That is usable if you really need different fields for different kind of users or you need them to live on other place at pagetree. More information about that from here: https://processwire.com/blog/posts/processwire-core-updates-2.5.14/#multiple-templates-or-parents-for-users

  • Like 2

Share this post


Link to post
Share on other sites
9 hours ago, apeisa said:

Your users actually live in page tree: Admin => Access => Users => User

So you can just create your users like that. Instead of $p = new Page(), just use $u = new User(); and you are good to go. No need to define template and parent in that case also, if I remember correctly.

PW also has possibilities to use different templates than user for users. That is usable if you really need different fields for different kind of users or you need them to live on other place at pagetree. More information about that from here: https://processwire.com/blog/posts/processwire-core-updates-2.5.14/#multiple-templates-or-parents-for-users

I read through the multiple parents post. All my users basically enter the same 6 fields. They get assigned one of two roles depending upon whether they are just subscribing to content, or contributing content.  I tried creating a user registration form... got it to create (albeit missing data, no follow up page, and ugly) to access > users ...  but I'd need it to also notify the admin that a new user is waiting. 

Share this post


Link to post
Share on other sites

You could hook into Pages::added, check to make sure the page has the user template and then create your own logic to notify the admin - eg send an email.

Share this post


Link to post
Share on other sites

@hollyvalero FrontendUser should be stable with older PW modules. I think some users here use it with prod websites too. It should work with PW 3, but there seems to be a problem with a password inputfield change ("Not yet validInvalidToo shortToo commonWeakOkGoodExcellent"). Additional css / js is needed to fix it.

 After seaching the blog I think this update causes the issue with the
https://processwire.com/blog/posts/upgrades-optimizations-pw-3.0.22/#major-enhancements-to-our-password-field

If I'm right the module should work fine / stable with PW <3.0.22 / <2.8.22. Newer version needs a workaround like @jmartsch mentioned earlier.

 

Share this post


Link to post
Share on other sites
13 minutes ago, pwFoo said:

@hollyvalero FrontendUser should be stable with older PW modules. I think some users here use it with prod websites too. It should work with PW 3, but there seems to be a problem with a password inputfield change ("Not yet validInvalidToo shortToo commonWeakOkGoodExcellent"). Additional css / js is needed to fix it.

 After seaching the blog I think this update causes the issue with the
https://processwire.com/blog/posts/upgrades-optimizations-pw-3.0.22/#major-enhancements-to-our-password-field

If I'm right the module should work fine / stable with PW <3.0.22 / <2.8.22. Newer version needs a workaround like @jmartsch mentioned earlier.

 

I'm running the latest version of PW, but if the only problem is the PW nag?  I think I'll export the site profile, load it to a second spot and try front end user... with the added js/css for the field validation and see if it works.  If it does, then we're all set.  I also looked at the subscribers module ... that too seemed to be in alpha :-D ...  I'll try Front End User first.

Share this post


Link to post
Share on other sites
28 minutes ago, adrian said:

You could hook into Pages::added, check to make sure the page has the user template and then create your own logic to notify the admin - eg send an email.

uh, yeah.. that. Maybe someday. I am still in the beansprout/newbie phase.

Share this post


Link to post
Share on other sites
2 minutes ago, modifiedcontent said:

@hollyvalero, just add $mail->send(... etc. at the point in the script where you want the admin email sent.

Yeah, I could probably do that... I'm going to install Front End User at another copy of PW... see how that looks.  Save this for my plan B. Thanks!

 

Share this post


Link to post
Share on other sites

Hi, I have a problem and I am seeking for advice.

I have users complaining of the way the login system works, the funny thing is that I am not able to duplicate the error. All I know is from the logs "Error: Call to a member function render() on null (line 137 of /home/consultazienda/public_html/site/assets/cache/FileCompiler/site/modules/FrontendUser/FrontendUser/FrontendUser.module)"

What happens is the user logs-in, gets a 404 page, some of them panic..., then goes back and the user has logged-in.

this is the code I see at :137

136	public function ___render() {
137		return $this->form->render();
138	}

I've many times to log-in with all the user-roles and never see this happening. Any idea where I could check? I know this a poor information post, but I dont know where to bang my head. Thanks

PW 3.0.50 - FU 0.9.3

Share this post


Link to post
Share on other sites

Sorry I think I found the problem, it was an if-statement I used during development and not properly cleaned... I've got only you guys in this forum on my most desperate moments :'(

Share this post


Link to post
Share on other sites

Hi,
is there any possibility to change the labels of the forms ( e.g. Translation )?
Thanks

Share this post


Link to post
Share on other sites

Hi!
Does anyboy know, how i translate the "register" - Button?
This doesn´t solve the problem:

    $buttonFieldreg = $fuRegister->form->get("fhSubmit3");
    $buttonFieldreg->label = "registrieren";

I also tried ->name and ->value - same result

Beyond this i would like to know, if there is a possibility to change the language of this parts ( siehe screenshot ).

Many thanks!!

 

Bildschirmfoto 2017-05-14 um 20.26.20.png

Share this post


Link to post
Share on other sites

This module was working fine until a month ago, then suddenly it stopped working in the desired manner. The login happens from pages other than the home page. But when someone tries to  login from the homepage, it just does not happen. I have been careful about the $redirectDestination and below is the code I am using, any suggestions will be extremely helpful.

 

    <? if($user->isGuest()) {
                 $fu = $modules->get("FrontendUser");
                 $fu->login(array('username', 'password', 'persist'));
                 if($page->path != "/"){
                    $redirectDestination = "/";
                }
                else {
                    $redirectDestination = "/blog/";
                }
            ?>
        <div class="new_login" id="new_login"><?  $fu->process($redirectDestination); echo $fu->render(); ?></div>
            <?    }
            else{ ?>
                <h4 style="padding-left:3em;text-transform:uppercase; -webkit-margin-after:0em; ">Welcome <?echo $user->name; ?></h4>
                <h5 style="padding-left:3.4em; -webkit-margin-before:0em;"><a href='/thank-you/' style="text-decoration:none; text-transform:uppercase;color:#bdbec0;">Logout?</a></h5>
            </div> 
            <? }    ?>
            </div>

 

You can see the working site at http://umbra.lightcube.in

Edited by kongondo
code blocks

Share this post


Link to post
Share on other sites

Hi,

any changes done like Update PW version? Code changes? Additional modules installed? At the moment the module isn't maintained / updated. So it could break if You update PW.

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 horst
      Wire Mail SMTP

      An extension to the new WireMail base class that uses SMTP-transport

      This module integrates EmailMessage, SMTP and SASL php-libraries from Manuel Lemos into ProcessWire. I use this continously evolved libraries for about 10 years now and there was never a reason or occasion not to do so. I use it nearly every day in my office for automated composing and sending personalized messages with attachments, requests for Disposition Notifications, etc. Also I have used it for sending personalized Bulkmails many times.

      The WireMailSmtp module extends the new email-related WireMail base class introduced in ProcessWire 2.4.1 (while this writing, the dev-branch only).
       
      Here are Ryans announcement.



      Current Version 0.2.6
      get it from the Modules Directory Install and Configure

      Download the module into your site/modules/ directory and install it.

      In the config page you fill in settings for the SMTP server and optionaly the (default) sender, like email address, name and signature.
      You can test the smtp settings directly there. If it says "SUCCESS! SMTP settings appear to work correctly." you are ready to start using it in templates, modules or bootstrap scripts.


      Usage Examples
      The simplest way to use it:
      $numSent = wireMail($to, $from, $subject, $textBody); $numSent = wireMail($to, '', $subject, $textBody); // or with a default sender emailaddress on config page This will send a plain text message to each recipient.
       
      You may also use the object oriented style:
      $mail = wireMail(); // calling an empty wireMail() returns a wireMail object $mail->to($toEmail, $toName); $mail->from = $yourEmailaddress; // if you don't have set a default sender in config // or if you want to override that $mail->subject($subject); $mail->body($textBody); $numSent = $mail->send(); Or chained, like everywhere in ProcessWire:
      $mail = wireMail(); $numSent = $mail->to($toEmail)->subject($subject)->body($textBody)->send(); Additionaly to the basics there are more options available with WireMailSmtp. The main difference compared to the WireMail BaseClass is the sendSingle option. With it you can set only one To-Recipient but additional CC-Recipients.
      $mail = wireMail(); $mail->sendSingle(true)->to($toEmail, $toName)->cc(array('person1@example.com', 'person2@example.com', 'person3@example.com')); $numSent = $mail->subject($subject)->body($textBody)->send(); The same as function call with options array:
      $options = array( 'sendSingle' => true, 'cc' => array('person1@example.com', 'person2@example.com', 'person3@example.com') ); $numSent = wireMail($to, '', $subject, $textBody, $options); There are methods to your disposal to check if you have the right WireMail-Class and if the SMTP-settings are working:
      $mail = wireMail(); if($mail->className != 'WireMailSmtp') { // Uups, wrong WireMail-Class: do something to inform the user and quit echo "<p>Couldn't get the right WireMail-Module (WireMailSmtp). found: {$mail->className}</p>"; return; } if(!$mail->testConnection()) { // Connection not working: echo "<p>Couldn't connect to the SMTP server. Please check the {$mail->className} modules config settings!</p>"; return; } Following are a ...


      List of all options and features


      testConnection () - returns true on success, false on failures


      sendSingle ( true | false ) - default is false

      sendBulk ( true | false ) - default is false, Set this to true if you have lots of recipients (50+)


      to ($recipients) - one emailaddress or array with multiple emailaddresses

      cc ($recipients) - only available with mode sendSingle, one emailaddress or array with multiple emailaddresses

      bcc ($recipients) - one emailaddress or array with multiple emailaddresses

       
      from = 'person@example.com' - emailaddress, can be set in module config (called Sender Emailaddress) but it can be overwritten here

      fromName = 'Name Surname' - optional, can be set in module config (called Sender Name) but it can be overwritten here


      priority (3) - 1 = Highest | 2 = High | 3 = Normal | 4 = Low | 5 = Lowest

      dispositionNotification () or notification () - request a Disposition Notification


      subject ($subject) - subject of the message

      body ($textBody) - use this one alone to create and send plainText emailmessages

      bodyHTML ($htmlBody) - use this to create a Multipart Alternative Emailmessage (containing a HTML-Part and a Plaintext-Part as fallback)

      addSignature ( true | false ) - the default-behave is selectable in config screen, this can be overridden here
      (only available if a signature is defined in the config screen)

      attachment ($filename, $alternativeBasename = "") - add attachment file, optionally alternative basename


      send () - send the message(s) and return number of successful sent messages


      getResult () - returns a dump (array) with all recipients (to, cc, bcc) and settings you have selected with the message, the message subject and body, and lists of successfull addresses and failed addresses,


      logActivity ($logmessage) - you may log success if you want

      logError ($logmessage) - you may log warnings, too. - Errors are logged automaticaly
       
       
      useSentLog (true | false) - intended for usage with e.g. third party newsletter modules - tells the send() method to make usage of the sentLog-methods - the following three sentLog methods are hookable, e.g. if you don't want log into files you may provide your own storage, or add additional functionality here

      sentLogReset ()  - starts a new LogSession - Best usage would be interactively once when setting up a new Newsletter

      sentLogGet ()  - is called automaticly within the send() method - returns an array containing all previously used emailaddresses

      sentLogAdd ($emailaddress)  - is called automaticly within the send() method
       
      Changelog: https://github.com/horst-n/WireMailSmtp/blob/master/CHANGELOG.md
       
    • By ukyo
      Call ProcessWire API Functions Inside STRING
      Github Repo
      Current status : BETA
      Each called method must return string value !
      I added all functions, but not tested all. I focused page(), page()->render and field properties (label, description and notes). I also tested some basic pages() api calls.
      Your API calls must start with { and must end with }. For use multiple arguments inside functions, separate arguments with ~ char.
      NOTE If you pass directly arguments to api {page(title)}, this call will check for requestedApiCall()->get(arguments).
      USAGE
      processString(string, page, language); Get page title <?php $str = "You are here : {page:title}"; echo processString($str); ?> Get page children render result <?php $str = "Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.<hr>{page:render:children}"; echo processString($str); ?> Get homepage title <?php $str = "You can visit our <a hre='{pages(1):url}'>{pages:get(1):title}</a>"; echo processString($str); ?> Get title field label, description or notes <?php $str = "Our title field properties are : label: {label(title)} - description: {description(title)} - notes: {notes(title)}"; echo processString($str); ?> Multiple examples <?php $str = " <ul class='uk-list uk-list-striped'> <li><b>01: GET FIELD LABEL</b> <code>&#123;label(title)&#125;</code> <b>RESULT :</b> <code>{label(title)}</code></li> <li><b>02: GET FIELD LABEL WITH PREFIX</b> <code>&#123;label(title~=> )&#125;</code> <b>RESULT :</b> <code>{label(title~=> )}</code></li> <li><b>03: GET FIELD LABEL WITH SUFFIX</b> <code>&#123;label(title~~ <=)&#125;</code> <b>RESULT :</b> <code>{label(title~~ <=)}</code></li> <li><b>04: GET FIELD DESCRIPTION</b> <code>&#123;description(title)&#125;</code> <b>RESULT :</b> <code>{description(title)}</code><br> <li><b>05: GET FIELD DESCRIPTION WITH PREFIX</b> <code>&#123;description(title~=> )&#125;</code> <b>RESULT :</b> <code>{description(title~=> )}</code></li> <li><b>06: GET FIELD DESCRIPTION WITH SUFFIX</b> <code>&#123;description(title~~ <=)&#125;</code> <b>RESULT :</b> <code>{description(title~~ <=)}</code></li> <li><b>07: GET FIELD NOTES</b> <code>&#123;notes(title)&#125;</code> <b>RESULT :</b> <code>{notes(title)}</code><br> <li><b>08: GET FIELD NOTES WITH PREFIX</b> <code>&#123;notes(title~=> )&#125;</code> <b>RESULT :</b> <code>{notes(title~=> )}</code></li> <li><b>09: GET FIELD NOTES WITH SUFFIX</b> <code>&#123;notes(title~~ <=)&#125;</code> <b>RESULT :</b> <code>{notes(title~~ <=)}</code></li> <li><b>10: GET PAGE TITLE</b> <code>&#123;page(title)&#125;</code> <b>RESULT :</b> <code>{page(title)}</code></li> <li><b>11: GET PAGE TITLE</b> <code>&#123;page:title&#125;</code> <b>RESULT :</b> <code>{page:title}</code></li> <li><b>12: GET PAGE RENDER TITLE</b> <code>&#123;page:render:title&#125;</code> <b>RESULT :</b> <code>{page:render:title}</code></li> <li><b>12: GET HOMEPAGE TITLE</b> <code>&#123;pages:get(template=home):title&#125;</code> <b>RESULT :</b> <code>{pages:get(template=home):title}</code></li> <li><b>13: GET HOMEPAGE TEMPLATE ID</b> <code>&#123;pages:get(template=home):template:id&#125;</code> <b>RESULT :</b> <code>{pages:get(template=home):template:id}</code></li> </ul> "; echo processString($str); ?>
    • By Robin S
      This module corrects a few things that I find awkward about the "Add New Template" workflow in the PW admin. I opened a wishlist topic a while back because it would good to resolve some of these things in the core, but this module is a stopgap for now.
      Originally I was going to share these as a few standalone hooks, but decided to bundle them together in a configurable module instead. This module should be considered alpha until it has gone through some more testing.
      Add Template Enhancements
      Adds some efficiency enhancements when adding or cloning templates via admin.

      Features
      Derive template label from name: if you like to give each of your templates a label then this feature can save some time. When one or more new templates are added in admin a label is derived automatically from the name. There are options for underscore/hyphen replacement and capitalisation of the label. Edit template after add: when adding only a single template, the template is automatically opened for editing after it is added. Copy field contexts when cloning: this copies the field contexts (a.k.a. overrides such as column width, label and description) from the source template to the new template when using the "Duplicate/clone this template?" feature on the Advanced tab. Copy field contexts when duplicating fields: this copies the field contexts if you select the "Duplicate fields used by another template" option when adding a new template. Usage
      Install the Add Template Enhancements module.
      Configure the module settings according to what suits you.
       
      https://github.com/Toutouwai/AddTemplateEnhancements
    • By AAD Web Team
      Hi,
      I've put in a support request (as a followup on an existing one) for this but it's nearly 10pm Ryan's time, so I thought I'd ask on here just in case someone can help...
      Yesterday we purchased ProDrafts, but I couldn't get the key to validate. Every time I hit submit on the module settings screen the key would be removed from the field I entered it in, and then it would complain about the missing value. I put in a support request and Ryan responded last night. It turned out it was because we're behind a proxy/firewall. He gave me a fix to get around that issue - some code to go into admin.php. I put that code in and saved admin.php, but now I can't even get into our admin anymore!
      (Just to clarify, I took the code back out and saved admin.php but that made no difference. It's definitely not the new code causing the error.)
      The errors relate to a lack of permission on the ProDrafts module (see attached screenshot). We do have a key, but evidently the code Ryan gave me to add the key in via admin.php isn't taking effect before the error is thrown...?
      I tried removing the ProDrafts directory from the modules directory, but that hasn't helped.
      Is there a hook I can put in somewhere to tell it not to load ProDrafts at all, or not check the permissions? Or is there some way to manually uninstall it from the file system?
      Thanks!
      Margaret

    • By DaveP
      I just made a textformatter module that allows you to insert dummy content (lorem ipsum style) in text fields via shortcodes.
      Usage is simple - just type for example [dc3] into a textarea with this textformatter applied (plain textarea or CKEditor) and it will be replaced at runtime by 3 paragraphs of dummy content. It can also be used to populate text fields (for headings etc) using e.g. [dc4w]. This will produce 4 words (rather than paragraphs) at runtime.
      The actual content comes from an included 'dummytext.txt' file containing 50 paragraphs of 'Lorem ipsum' from lipsum.com. The 50 paragraphs is arbitrary - it could be 10 or 100 or anything in between, and the contents of that file can be changed for your own filler text if you wish.
      The slightly clever bit is that for any given page, the same content will be returned for the same tag, but the more paragraphs available in 'dummytext.txt', the less likely it is that two pages will get the same content (very roughly speaking - it's actually based on the page ID) so content selection is determinate rather than random, even though only the tags are saved to the db.
      Update
      Tags now work like this -
      [dc3] - Show 3 paragraphs ([dc:3], [dc3p] & [dc:3p] all do the same). [dc3-6] - Show 3 to 6 paragraphs randomly per page load ([dc:3-6], [dc3-6p] & [dc:3-6p] all do the same). [dc3w] - Show 3 words ([dc:3w] does the same). [dc3-6w] - Show 3 to 6 words randomly per page load ([dc:3-6w] does the same). <End update on tags.>
      If you think it might be useful, you can download it from GitHub and give it a try.