Jump to content
adrian

Email New User

Recommended Posts

This seems to be a very versatile and hackable module, thank you for creating it :)

I've already created a version, which only emails the admin, when a new user is created (=registers on their own).

Now I'm tinkering with a version, which only emails the user manually, with the "Send email" feature in the user page.

If I want to block the automatic emailing on user creation, is it enough to add

if(!$this->page->process == 'ProcessUser') return;

in the sendNewUserEmail function before the other exiting conditions?

I though I'd ask and share the inspiration, before I even put the site online and can actually test the emailing functionality :)

My goal is to import a bunch of users from another CMS, send them the welcome email on creation, then disable adrian's original module and enable my two modified modules permanently.

Share this post


Link to post
Share on other sites

Hi Beluga - glad you are finding it useful, although I have to wonder if your use case for emailing the admin when a new user registers couldn't be better handled by a separate custom module - most of the code from this module is likely not relevant.

I think your tinkering regarding a manual only send email feature might be a useful option for this module. It could be a configurable option that adds a checkbox to the user page which could be checked or unchecked by default which determines whether the email is sent or not when registering a new user - would that work for you?

Share this post


Link to post
Share on other sites

I think your tinkering regarding a manual only send email feature might be a useful option for this module. It could be a configurable option that adds a checkbox to the user page which could be checked or unchecked by default which determines whether the email is sent or not when registering a new user - would that work for you?

It sure would work. Thanks for considering it.

Share this post


Link to post
Share on other sites

Ok, there is a new version with a new config setting: Automatic Email Send. This is checked by default, but if you uncheck this, then when creating new users the Send Email checkbox will be unchecked by default, so you will need to manually check each time to want to email a new user upon creation. This setting also works with users added via the API. If unchecked, they won't be sent an email, so you will need to use:

$newuser->sendEmail = true;

to have the email sent.

Hope that meets your needs and others also find it useful!

  • Like 2

Share this post


Link to post
Share on other sites

Ok, now I got to test it on an online site.

Some notes:

- if creating users with CSV import, the pwd is generated only, if left blank in the CSV. If pwd exists in CSV, it won't be overwritten by a generated one. I don't know, if this is intentional, so decided to mention

- users registered via FrontendUser module will not trigger emails!

Here is the source for the FrontendUser module in Bitbucket.

Share this post


Link to post
Share on other sites
- if creating users with CSV import, the pwd is generated only, if left blank in the CSV. If pwd exists in CSV, it won't be overwritten by a generated one. I don't know, if this is intentional, so decided to mention

This is intentional - if you want the automatically generated password to be used, make sure the password field is not populated.

- users registered via FrontendUser module will not trigger emails!

Not surprising - EmailNewUser is not autoload outside of the admin interface - see the instructions for using via the API where it mentions that you need to manually load it first. You could either change:

"autoload": "template=admin",

in the EmailNewUser.info.json to autoload : true or you would need to hack the FrontendUser module so that it loads this module with:

wire('modules')->get("EmailNewUser"); // call the module since it is not autoload on the front end

Perhaps you could request for pwFoo to add a check if this module is installed and if so, load it - others might find that useful too.

  • Like 1

Share this post


Link to post
Share on other sites

Thanks! Setting autoload to true actually didn't work, but it is simply enough for me to put this in my register.php:

$modules->get('EmailAdminNewUser');

Now I will get admin emails for users that have registered!

  • Like 2

Share this post


Link to post
Share on other sites

Dont really wortk for me with the FrontendUser Module 

<?php include('./_head.inc'); // include header markup 
$modules->get('EmailAdminNewUser'); // lade Modul um den Admin zu benachrichtigen 
?>
<div class='container paddingtop100'>
  <div class='row'>
            <div class='col-md-4'></div>
            <div class='col-md-4'><img class='img-responsive' src='../site/assets/files/1/pluco-logo.jpg'/></div>
            <div class='col-md-4'></div>
        </div> 
  </div>
<section  class="contain nav-link ">
    
<div  class="register weissbg">
<div class="small text-center" ><?=$page->body_m ?></div>
<div class='container '>
<div class='row'>
<?php 
$fu = $modules->get('FrontendUser');
// prepare login form (default parameters)
$fu->login();
// Default parameter
//$fu->login(array('username', 'password'));
    echo "<h4>Registrierte Nutzer hier anmelden</h4>";
// Additional LoginPersist and ProcessForgotPassword module integration (built-in)
$fu->login(array('username', 'password',  'forgot'));
// process login / form submit
$fu->process('../objekte/');
// output form
echo $fu->render();
 ?>
<?php 
    echo "<br /><h4>Nutzerregistrierung</h4>";

$u_vorname = $modules->get('InputfieldText');
$u_vorname->label = $this->_('Vorname*');
$u_vorname->attr('id+name', 'u_vorname');
$u_vorname->required = 1;
$u_vorname->fhSanitizer = 'text';
$nachname = $modules->get('InputfieldText');
$nachname->label = $this->_('Nachname*');
$nachname->attr('id+name', 'nachname');
$nachname->required = 1;
$nachname->fhSanitizer = 'text';
$unternehmen = $modules->get('InputfieldText');
$unternehmen->label = $this->_('Unternehmen*');
$unternehmen->attr('id+name', 'unternehmen');
$unternehmen->required = 1;
$unternehmen->fhSanitizer = 'text';
$strnr = $modules->get('InputfieldText');
$strnr->label = $this->_('Strasse / Hausnummer*');
$strnr->attr('id+name', 'strnr');
$strnr->required = 1;
$strnr->fhSanitizer = 'text';
$plz = $modules->get('InputfieldText');
$plz->label = $this->_('Plz / Ort*');
$plz->attr('id+name', 'plz');
$plz->required = 1;
$plz->fhSanitizer = 'text';
$tel = $modules->get('InputfieldText');
$tel->label = $this->_('Telefonnummer*');
$tel->attr('id+name', 'tel');
$tel->required = 1;
$tel->fhSanitizer = 'text';

$fu->addHookBefore('save', function($event) {
    $form = wire('fu')->form;
    $user = wire('fu')->userObj;
    $user->addRole('registered');
    if(!count($form->getErrors())) {

        wire('fu')->userObj->u_vorname = $form->fhValue('u_vorname', 'text');
        wire('fu')->userObj->u_nachname = $form->fhValue('nachname', 'text');
        wire('fu')->userObj->u_unternehmen = $form->fhValue('unternehmen', 'text');
        wire('fu')->userObj->u_hausnummer = $form->fhValue('strnr', 'text');
        wire('fu')->userObj->u_plzort = $form->fhValue('plz', 'text');
        wire('fu')->userObj->u_telefonnummer = $form->fhValue('tel', 'text');
 
    }
});
// Call hook after field is processed by PW form api
// prepare register form
$fu->register();
// Default parameter
//$fu->register(array('username', 'email', 'password'));
// Additional email pre-register validation plugin (built-in)
$fu->register(array('username',  $u_vorname, $nachname, $unternehmen , $strnr, $plz, $tel, 'email', 'password'));
// process register / form submit
$fu->process('../registrieren/aktivation/');
// output register form
echo $fu->render();
echo "<p class='small description'>* Gekennzeichnete Felder sind Pflichtangaben<br />Nach der Freischaltung erhalten Sie umgehend eine Bestätigungs-Email mit Ihren Login-Daten.</p>";
?>
</div>
</div>
</div>
</section>
  
<?php include('./_foot.inc'); // include footer markup ?>

whats the mistake here ? 

Share this post


Link to post
Share on other sites

@iNoize,

Looking at your code, you are loading: EmailAdminNewUser rather than EmailNewUser. So, you are not using this module at all, but rather a module written by @Beluga - https://processwire.com/talk/topic/9811-frontenduser-login-logout-and-register-users-members/?p=101533

So I am afraid you will need to ask him about it.

Share this post


Link to post
Share on other sites

Hi, I'm consistently getting the error: 

 No email was sent to the new user because of an unknown problem. Please try the 'Re-send Welcome Message' option.

I'm assuming this is a server configuration problem, does anyone have any idea how to go about rectifying/troubleshooting this?

EDIT: Really strange, if I hardcode the 'from' email address into line 141 instead of using the passed variable (which as far as I can see is exactly the same) it works correctly.

Share this post


Link to post
Share on other sites

Hi @ZGD and welcome to the forums!

Sorry you are having troubles with this module. It does sound like a very weird situation indeed.

Can you please confirm that the from email address is correctly filled out in the module config settings, like so:

post-985-0-10727300-1441374057_thumb.png

If it is, could you try an:

error_log($this->data['fromEmail']);

just after line 141 and see what it returns.

Share this post


Link to post
Share on other sites

Very strange indeed, I'd checked it multiple times, but copy pasting the email address back into the same input seems to have fixed it. I have no idea what happened there, but thanks for suggesting to check it once again.

I have one other question regarding using this in conjunction with Ryan's Import Pages from CSV module. I have a test CSV with 4 columns (title,displayname,email,roles) and 5 rows. I'm trying to import multiple users and have EmailNewUser auto-generate a password for each, it works successfully for the first user/row, but then I get the error "No email was sent to the new user because either their email address or password was not set." after that, I'm assuming because of line 137 (although I'm not sure if it's because of the email or password being blank? Has anyone successfully managed to do this?

EDIT: Seems if I include the 'pass' column, and use "" as the value for each row, it works!

  • Like 1

Share this post


Link to post
Share on other sites

Great - glad to hear you got everything working. 

I am super busy here at the moment and don't have time right now to see if there would be a simple way to remove the need for a blank "pass" column in the CSV field, but I don't think it matters so long as anyone attempting this knows it is required.

Share this post


Link to post
Share on other sites

Thanks adrian, the users have very restricted access to non-sensitive information for this one, it's more of a formality really. I will definitely be using ForcePasswordChange for future projects though, super easy to manage users through PW with these kinds of modules.

  • Like 1

Share this post


Link to post
Share on other sites

I changed my host to a dedicated server. I installed Postfix. Sending test email from module settings does not work.

It works (I receive email), if I replace the "wireMail(wire.." line with:

$mail = wireMail();
$mail->to('somemail@somesite.com')->from('myemail@site.com');
$mail->subject('Mail Subject');
$mail->body('Mail Body');
$mail->bodyHTML('<html><body><h1>Mail Body</h1></body></html>');
$mail->send();

How can I troubleshoot this? With Tracy debugger? :)

Share this post


Link to post
Share on other sites

Hi @Beluga,

Firstly, is it only the test send that isn't working, or do they also fail when adding a new user?

Well I don't think there should be a reason why the syntax you changed it to should work while the:

wireMail('user@domain.com', 'ryan@runs.pw', 'Mail Subject', 'Mail Body'); 

syntax won't.

I think the most likely problem is that I had an incorrect static call to a non-static method in there when doing the test send. Maybe your new server is failing on strict errors? I have fixed this in the latest version. Please let me know if that fixes it for you.

If it doesn't then you could play with Tracy like this and make sure they all return what is expected.

        // send test email if requested
        if (wire('input')->post->test) {
            bd(wire('user')->email, 'Admin User Email');
            bd($data['fromEmail'], 'From Email');
            bd($data['subject'], 'Subject'); // not really relevant, but may as well confirm its value
            bd(EmailNewUser::parseBody($data['body'], $data['fromEmail'], wire('user'), 'password'), 'Body'); // again, not really relevant
            wireMail(wire('user')->email, $data['fromEmail'], $data['subject'], self::parseBody($data['body'], $data['fromEmail'], wire('user'), 'password'));
        }
You will of course have to enable the Tracy debug bar for the backend.

Share this post


Link to post
Share on other sites

I use manual sending of the welcome email. I tested it and it does not work either. I used your bd() and the contents dumped look fine, my email is there etc.

I realized it is a general problem so I posted to the WireMail thread.

  • Like 1

Share this post


Link to post
Share on other sites
On 7/20/2015 at 4:28 PM, Beluga said:

Thanks! Setting autoload to true actually didn't work, but it is simply enough for me to put this in my register.php:


$modules->get('EmailAdminNewUser');

Now I will get admin emails for users that have registered!

Thanks for this @Beluga I had to use 

$modules->get('EmailNewUser');

in my register.php instead. But it works with the FrontendUser now. Very useful module @adrian!

  • Like 3

Share this post


Link to post
Share on other sites

I am also getting:

Session: No email was sent to the new user because of an unknown problem. Please try the 'Re-send Welcome Message' option.

PW 2.7.2

Share this post


Link to post
Share on other sites
1 hour ago, benbyf said:

I am also getting:

Session: No email was sent to the new user because of an unknown problem. Please try the 'Re-send Welcome Message' option.

PW 2.7.2

Are you using this with the frontend user module? Are you adding the user via the API or admin? Is the test send working ok?

Share this post


Link to post
Share on other sites

I didn't try the test as it wasnt obvious. I installed, added the settings, then went and created a user in the admin and got the error a couple of times (even when hard coding the email in the module as suggested above).

Share this post


Link to post
Share on other sites
9 minutes ago, benbyf said:

I didn't try the test as it wasnt obvious. I installed, added the settings, then went and created a user in the admin and got the error a couple of times (even when hard coding the email in the module as suggested above).

I am going to need more to go on here. I have been using this module on all my sites (on several different PW versions) since I created it. I don't suppose you could give me access to the server to take a look?

  • Like 1

Share this post


Link to post
Share on other sites

Really sorry but its a clients site not my own personal project. I cant seem to send out through wiremail() so that might be the issue. php mail() works fine.

Share this post


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

Really sorry but its a clients site not my own personal project.

No problem - understood!

2 minutes ago, benbyf said:

I cant seem to send out through wiremail() so that might be the issue. php mail() works fine.

Do we agree then that it's not an issue with this module, but rather with the setup in your wireMail sending module?

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
      TrelloWire
      This is a module that allows you to automatically create Trello cards for ProcessWire pages and update them when the pages are updated. This allows you to setup connected workflows. Card properties and change handling behaviour can be customized through the extensive module configuration. Every action the module performs is hookable, so you can modify when and how cards are created as much as you need to. The module also contains an API-component that makes it easy to make requests to the Trello API and build your own connected ProcessWire-Trello workflows.
      Features
      All the things the module can do for you without any custom code: Create a new card on Trello whenever a page is added or published (you can select applicable templates). Configure the target board, target list, name and description for new cards. Add default labels and checklists to the card. Update the card whenever the page is updated (optional). When the status of the card changes (published / unpublished, hidden / unhidden, trashed / restored or deleted), move the card to a different list or archive or delete it (configurable). You can extend this through hooks in many ways: Modifiy when and how cards are created. Modify the card properties (Target board & list, title, description, et c.) before they are sent to Trello. Create your own workflows by utilizing an API helper class with many convenient utility methods to access the Trello API directly. Feedback & Future Plans
      Let me know what you think! In particular:
      If you find any bugs report them here or on Github, I'll try to fix them. This module was born out of a use-case for a client project where we manage new form submissions through Trello. I'm not sure how many use-cases there are for this module. If you do use it, tell me about it! The Trello API is pretty extensive, I'll try to add some more helper methods to the TrelloWireApi class (let me know if you need anything in particular). I'll think about how the module can support different workflows that include Twig – talk to me if you have a use-case! Next steps could be a dashboard to manage pages that are connected to a Trello card, or a new section in the settings tab to manage the Trello connection. But it depends on whether there is any interest in this 🙂 Links
      Repository on Github Complete module documentation (getting started, configuration & API documentation) TrelloWire in the modules directory Module configuration

    • By Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-04-06 -- SnipWire 0.8.6 (beta) released! Adds support for Snipcart subscriptions and also fixes some problems 2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Multi currency support Custom order and cart fields Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • By bernhard
      #######################
      Please use the new RockFinder2
      #######################
      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/
    • By MoritzLost
      Process Cache Control
      This module 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) Clear the ProCache page render cache (if your site is using ProCache) 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.
      Plans for improvements
      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 CHANGELOG in the repository Screenshots


    • By Macrura
      PrevNextTabs Module
      Github: https://github.com/outflux3/PrevNextTabs
      Processwire helper modules for adding page navigation within the editor.
      Overview
      This is a very simple module that adds Previous and Next links inline with the tabs on the page editor. Hovering over the tab shows the title of the previous or next page (using the admin's built in jqueryUI tooltips.)
      Usage
      This module is typically used during development where you or your editors need to traverse through pages for the purpose of proofing, flagging and/or commenting. Rather than returning to the page tree or lister, they can navigate with these links.
      Warnings
      If you are using PW version 2.6.1 or later, the system will prevent you from leaving the page if you have unsaved edits.
      For earlier versions, to avoid accidentally losing changes made to a page that might occur if a user accidentally clicks on one of these, make sure to have the Form Save Reminder module installed.
      http://modules.processwire.com/modules/prev-next-tabs/
×
×
  • Create New...