WordPress Trac: Ticket #14412: User Registration via Templateshttps://core.trac.wordpress.org/ticket/14412
<p>
To improve the vast multitude of WP installtions that utilize member registrations, I suggest and implore the development team to improve user registration via templates. The reasons are as follows:
</p>
<ul><li>More secure
</li><li>More flexible
</li><li>Better customization options
</li><li>Better integration
</li></ul><p>
I was prompted by this post: <a class="ext-link" href="http://www.cozmoslabs.com/2010/05/31/wordpress-user-registration-template-and-custom-user-profile-fields/"><span class="icon">​</span>http://www.cozmoslabs.com/2010/05/31/wordpress-user-registration-template-and-custom-user-profile-fields/</a> the development of Hooks and Filters has made it relatively easy to make such improvements system-wide.
</p>
en-usWordPress Trachttps://core.trac.wordpress.org/chrome/site/your_project_logo.pnghttps://core.trac.wordpress.org/ticket/14412
Trac 1.0.1wpmuguruSun, 25 Jul 2010 03:18:36 GMThttps://core.trac.wordpress.org/ticket/14412#comment:1
https://core.trac.wordpress.org/ticket/14412#comment:1
<p>
Related: <a class="new ticket" href="https://core.trac.wordpress.org/ticket/14108" title="enhancement: Unify registration between single site and network configurations (new)">#14108</a>
</p>
TicketGuruXLSun, 25 Jul 2010 05:59:28 GMThttps://core.trac.wordpress.org/ticket/14412#comment:2
https://core.trac.wordpress.org/ticket/14412#comment:2
<p>
Just remember my main concern is being able to register users via the front-end without having to resort to complex hacks. There is no real user management system in place with WP, the ability to edit the default roles of Contributor, Editor, Administrator.
</p>
<p>
We are looking at: user_register, wp_login, wp_logout, register_form, profile_update, etc all these hooks would be involved in making a FRONT-END user registration and profile editing screens, customizable via templates. On the backend, you would manage the users who sign up and can assign them into custom usergroups (have the default but, you can edit those) and then use content protection, so only those users can access certain areas like the admin panel or specific URLs or Post/Page IDs. Those most of the rest of that can be done via plugins.
</p>
TicketwpmuguruSun, 25 Jul 2010 16:31:10 GMTmilestone changedhttps://core.trac.wordpress.org/ticket/14412#comment:3
https://core.trac.wordpress.org/ticket/14412#comment:3
<ul>
<li><strong>milestone</strong>
changed from <em>Awaiting Review</em> to <em>Future Release</em>
</li>
</ul>
<p>
Replying to <a class="closed" href="https://core.trac.wordpress.org/ticket/14412#comment:2" title="Comment 2 for Ticket #14412">GuruXL</a>:
</p>
<blockquote class="citation">
<p>
Just remember my main concern is being able to register users via the front-end without having to resort to complex hacks.
</p>
</blockquote>
<p>
Building a custom registration process does not require *any* hacks (complex or otherwise). The extended profile component in BuddyPress (<a class="ext-link" href="http://buddypress.org"><span class="icon">​</span>http://buddypress.org</a>) already does nearly all the things you have described.
</p>
TicketmikeschinkelTue, 03 Aug 2010 00:35:36 GMTcc changedhttps://core.trac.wordpress.org/ticket/14412#comment:4
https://core.trac.wordpress.org/ticket/14412#comment:4
<ul>
<li><strong>cc</strong>
<em>mikeschinkel@…</em> added
</li>
</ul>
<p>
Replying to <a class="closed" href="https://core.trac.wordpress.org/ticket/14412#comment:3" title="Comment 3 for Ticket #14412">wpmuguru</a>:
</p>
<blockquote class="citation">
<p>
Replying to <a class="closed" href="https://core.trac.wordpress.org/ticket/14412#comment:2" title="Comment 2 for Ticket #14412">GuruXL</a>:
</p>
<blockquote class="citation">
<p>
Just remember my main concern is being able to register users via the front-end without having to resort to complex hacks.
</p>
</blockquote>
<p>
Building a custom registration process does not require *any* hacks (complex or otherwise). The extended profile component in BuddyPress (<a class="ext-link" href="http://buddypress.org"><span class="icon">​</span>http://buddypress.org</a>) already does nearly all the things you have described.
</p>
</blockquote>
<p>
Off topic maybe, but I've only recently tried BuddyPress only to be dismayed by the fact it appears that you either have a WordPress site or a BuddyPress site (that is unless you do *lots* of hacking.) I'd love to have a main site with a BuddyPress "<em>off to the side</em>" like many people are now creating WordPress-based websites with a blog off to the side.
</p>
<p>
So I concur with @GuruXL; it would be nice to have a better front-end based user registration system that doesn't require as much code as BuddyPress has to use for some use-cases, and for other use-cases it also be nice if BuddyPress could be integrated into a WordPress site w/o taking it over.
</p>
Ticketchriscct7Wed, 08 Oct 2014 04:55:30 GMTkeywords, status changed; focuses, resolution sethttps://core.trac.wordpress.org/ticket/14412#comment:5
https://core.trac.wordpress.org/ticket/14412#comment:5
<ul>
<li><strong>keywords</strong>
<em>close</em> added; <em>user</em> <em>profile</em> <em>registration</em> removed
</li>
<li><strong>status</strong>
changed from <em>new</em> to <em>closed</em>
</li>
<li><strong>focuses</strong>
<em>ui</em> added
</li>
<li><strong>resolution</strong>
set to <em>wontfix</em>
</li>
</ul>
<p>
There are so many plugins that do this now using the included actions and filters that this no longer seems to be a valid concern
</p>
TicketDrewAPictureWed, 08 Oct 2014 19:02:48 GMTkeywords, milestone deletedhttps://core.trac.wordpress.org/ticket/14412#comment:6
https://core.trac.wordpress.org/ticket/14412#comment:6
<ul>
<li><strong>keywords</strong>
<em>close</em> removed
</li>
<li><strong>milestone</strong>
<em>Future Release</em> deleted
</li>
</ul>
<p>
Related <a class="new ticket" href="https://core.trac.wordpress.org/ticket/20075" title="enhancement: Add action hooks to wp-activate.php in WP network (new)">#20075</a>
</p>
Ticket