Instead of … } else { echo “<p>Your file has been uploaded.</p>”; } … redirect to another address on success: } else { $new_url = add_query_arg( ‘success’, 1, get_permalink() ); wp_redirect( $new_url, 303 ); exit; } Status code 303 triggers a GET request: This method exists primarily to allow the output of a POST-activated script … Read more
The latest entered password is stored as a secure hash in a cookie named ‘wp-postpass_’ . COOKIEHASH. When the password form is called, that cookie has been validated already by WordPress. So you just have to check if that cookie exists: If it does and the password form is displayed, the password was wrong. add_filter( … Read more
The code he posted in that tutorial (very nice BTW) post’s the form to the build-in “reset password” module which redirects to the login.php on error, but you can change that and build your own based on the original and add it to the template page, change: <form method=”post” action=”<?php echo site_url(‘wp-login.php?action=lostpassword’, ‘login_post’) ?>” class=”wp-user-form”> … Read more
No, but it should 😉 There are several custom field class’s (backend). wpAlchemy : https://github.com/farinspace/wpalchemy Meta Box Script: https://github.com/rilwis/meta-box My-Meta-Box: https://github.com/bainternet/My-Meta-Box meta-box-class: https://github.com/corycrowley/meta-box-class Meta Boxes Class: https://github.com/Bakke/Wordpress-Custom-Meta-Boxes-Class For front-end forms, you probably best off with a plugin in Eugene Manuilov’s link.
Jeff Starr wrote a great tutorial on front-end registration, login and password recovery taking the similar approach as suggested by onetrickpony. So take this as a follow up to his answer and as another resource that might help you get it done: http://digwp.com/2010/12/login-register-password-code/ Now you have two examples how to code this yourself and trust … Read more
Maybe a little late but I stumbled on this when I was having issues figuring it out so thought I would supply what I found out for future people. I’ve found the basic principles are to have a hidden input named action and it’s value being a custom set identifier. For example <input name=”action” type=”hidden” … Read more
It looks like this is supported by Contact Form 7 natively, it’s just not very obvious on how to make it happen. Here’s a documentation page explaining the functionality: http://contactform7.com/selectable-recipient-with-pipes/ Basically, all you have to do is put the values like so: “Visible Value|actual-form-value” What comes before the pipe | character will be shown in … Read more
You should use the wp_ajax or the wp_ajax_nopriv function. First of all you should put the the admin ajax url as the action attribute value in the submission form. <form id=”” action=”<?php echo admin_url(‘admin-ajax.php’); ?>” method=”post” class=”form” > That way the the form will be submitted to the admin-ajax.php by default (without JavaScript). You can … Read more
Send the form action either to your homepage, or to a specific page URL. You can’t have $_POST handling within the template because you need to redirect after your process it, and redirect needs to be fired before any HTML output. // you should choose the appropriate tag here // template_redirect is fired just before … Read more
Prefix everything, especially your variables. The names you are using are used by WordPress internally (see the comment form), so WordPress might try to do something with your form values. If that fails you get an error. While $_GET problems are usually rather easy to debug, $_POST and $_REQUEST names are not so simple. The … Read more