That action doesn’t pass that data: function return_user_data_on_logout( $user ) { Here, $user will alway be undefined. Additionally, you need to tell add_action how many parameters the function takes. But.. do_action( ‘clear_auth_cookie’ ); No information is passed to begin with, that’s not how this particular event/action works. So how do we get the current user … Read more
There’s no need to regenerate the logout URL (the $logout_url part in your code) because the first parameter passed to your function is already the logout URL. So basically, just rename that $force_reauth to $logout_url and remove the $logout_url = wp_nonce_url( … );: function my_custom_logout_url($logout_url, $redirect=null){ // rename the $force_reauth // And remove this: //$logout_url … Read more
In functions.php add: <?php function ps_redirect_after_logout(){ // get the current user’s id $current_user_id = get_current_user_id(); // Get Paul $paul = get_user_by(‘login’, ‘Paul’); $paulsid = $paul->ID; // check if current user is Paul if($current_user_id == $paulsid) { wp_redirect(‘https://www.example.club/logout-page/’); exit(); } } add_action(‘wp_logout’,’ps_redirect_after_logout’); I haven’t tested this code, but something like this should be the way to … Read more
I discovered the Hikari Hooks Troubleshooter (http://hikari.ws/hooks-troubleshooter/) this weekend to find what plugins were loading my header with competing open graph metadata. Enable it, and visit the frontend. There will be a modal dialog over your site which should list the hooks into wp_logout. One of these will be the offending plugin. If you’re still … Read more
It’s not clear, but I’m assuming you want a ‘log out’ url, that brings the user back to the current page? get_permalink() however, get’s the permalink of the current post in the loop (if you’re using it outside the loop, you’ll find that it takes the user to the last post in the loop after … Read more
You have in many ways already answered your question: the technique described in the article is not going to be reliable. What you might not have worked out is “why”. The code uses relative URLS… <form name=”loginform” id=”loginform” action=”/wp-login.php” method=”post”> … which are nearly always unreliable in WordPress context. That won’t work if the site … Read more
This will disable nonce checking for logging out – on your head be it: add_action( ‘login_form_logout’, function () { $user = wp_get_current_user(); wp_logout(); if ( ! empty( $_REQUEST[‘redirect_to’] ) ) { $redirect_to = $requested_redirect_to = $_REQUEST[‘redirect_to’]; } else { $redirect_to = ‘wp-login.php?loggedout=true’; $requested_redirect_to = ”; } /** * Filters the log out redirect URL. * … Read more
This should be possible, WordPress provides the WP_Session_Tokens class to manage logged in sessions. Then it’s just a matter of connecting it to the cron. The following is a simple plugin file which I think should do it. Add it to the plugins directory and it should start working. *not tested. <?php /* Plugin Name: … Read more
Here’s how I managed to set it up for one client. The code (which should go into the theme’s functions.php) assumes there’s an existing menu item titled ‘Login’. Works fine but may not be the best way, so critique is welcome. function wpse0520_modify_login_menu_item( $item ) { if(isset($item->title)){ if( $item->title ==’Login’ ) { if(is_user_logged_in()){ $item->url = … Read more
You can log out the current user with wp_logout() function: I think it is much better approach. wp_logout() destroys current session, clears authorization cookie and call wp_logout action. Also, it is a pluggable function, which means can be redefined by plugins. You can miss important stuff, specially when working in combination with other plugins. If … Read more