This can (and should) be achieved using the admin_post action. Take a look at the docs for an example: https://codex.wordpress.org/Plugin_API/Action_Reference/admin_post_(action) SitePoint also have a more comprehensive tutorial here: https://www.sitepoint.com/handling-post-requests-the-wordpress-way/ Hope that helps.
In your PHP, use wp_create_user(). With this function, you can pass username, email and `password’. Then, wp update user() to give the user the other bits of info. I would hook my user-creation function to the init hook. Also, you want to put a nonce field in your form e.g. this, between the <form> tags: … Read more
For the first part of your question, you can add new columns to the users table. Its in two steps: first you need to register the columns, then output information for each row. To add new columns, you hook into the manage_users_columns filter: function yourdomain_manage_users_columns( $columns ) { // $columns is a key/value array of … Read more
I have solved it. In the redirect I changed if (count($error) == 0 ){ to if (count($error) < 1 ){ Also for any custom user meta fields added duplicated the following line and change the word ‘description’ to the name of the field create in your function file. if ( !empty( $_POST[‘description’] ) ) update_user_meta( … Read more
According to WordPress Codex about the template_redirect hook: This action hook executes just before WordPress determines which template page to load. So, you are redirecting the user to another page before the template is even loaded, which your form won’t load at all. You can use another hook which runs after template_redirect, such as wp_footer. … Read more
What about (1) current_screen? action hook, or a condition for (2) get_current_screen() in your conditional and then calling wp_redirect? Both give you a WP_Screen object which has several parameters, including a $parent_base property that can give broader inclusion if needed, too. Here’s the property list from the codex: $action Any action associated with the screen. … Read more
Problem solved. There was a conflict with the Ninja Popups Plugin because it tries to capture any form submit. The Contributer of the Mailchimp for WordPress Plugin helped me here: https://wordpress.org/support/topic/buddypress-and-mailchimp-form-doesnt-work-together/#post-9397642
It’s not possible without JavaScript. The HTML for it is output in the WP_Admin_Bar in a private and protected method with no filter. You can remove them after the page has loaded with JS like so: function wpse_287259_remove_skip_link() { echo “<script>jQuery( ‘.screen-reader-shortcut’ ).remove();</script>”; } add_action( ‘wp_after_admin_bar_render’, ‘wpse_287259_remove_skip_link’ ); I hope it goes without saying that … Read more
Just saw it… …in your HTML, take the action out entirely. We’re not using the HTML to tell the form/submit button what to do, we’re using JS/AJAX for that. <form method=”POST” action=”<?php echo admin_url(‘admin-ajax.php’); ?>” id=”modal-form-ajax” autocomplete=”off”> Should become: <form method=”POST” id=”modal-form-ajax” autocomplete=”off”> Also, instead of targeting the form, target the submit button, so the … Read more
So the root problem is sending headers, specifically the timing. Webpages have http headers, and http headers come before the content. The headers tell the browser what it’s recieving, and they must be sent first. When PHP outputs stuff, it needs to tell the browser to expect output, so the moment a character is output, … Read more