[wp-hackers] Best practice: custom registration form

Lox lox.dev at knc.nc
Tue Aug 3 18:13:46 UTC 2010

2010/8/4 Frank Bueltge <frank at bueltge.de>:
> WP has fuctions for this job, see on wp_login_form

Mmmh well I can't find any wp_login_form.php but a wp_login.php that I
am currently duplicating to be available from the frontend, integrated
into a choosen page.

> Is easy-contact to use without plugins, you can also use wp_rewrite for
> Customer rewrite

wp_rewrite will take over the whole target page whereas I want to use
it so the WP admins can set/edit the title and a descriptive text for
the registration page and also link to it from the new nav_menu

> On Tuesday, August 3, 2010, Lox <lox.dev at knc.nc> wrote:
>> I do not like the short-code approach ei...
> Trying to avoid short codes entirely is asking for headaches when you
> are using wp. They are the most common solution to many problems and
> are popular because they are easy to create and use. If you are having
> scaling issues you need to work on them separately, banning short
> codes is not an efficient use of time

I never talked about banning short-codes and I make extensive use of
them in my project.

But it is a waste of ressources to set a shortcode that will be used
only ONCE in a website of over 300 pages....


So I decided to use the do_action('registration_form') approach. It is
added manually for now but it will override the target page template
with its own when finished.

Now i face the problem (that I will have faced using shortcodes) that
I can't set any header, either for setting cookies or for

lox.dev at knc.nc

More information about the wp-hackers mailing list