Redirect on logout

Hello,

I have the (M) Social theme installed, and my activity and directory areas are all hidden and can only be seen when logged in. So, when a user logs out when they are on one of these pages they of course get a "404" error page not found. I'd like to change it to when they logout it redirects to the home page. I don't really want to tie it to a specific button because there are multiple ways to logout.

Is there a way to add this redirect to the logout functionality across the theme?

Thanks.

http://wordpress.org/support/topic/wp-l ... o-homepage

Hi @Cyberek

It doesn't seem to work for me on the pages that are login-restricted.

I put the following in my functions.php file:

Code: Select all

// redirects to homepage after logout
add_action('wp_logout','go_home');
function go_home(){
  wp_redirect( home_url() );
  exit();
}

If I'm in an activity thread or the directory or groups or any page that I have listed as must be signed-in to view I get this when I hit the "Logout" button in the menu bar that is part of your theme.

This is the url that shows up: https://briarcliffcommunityalliance.org ... tion=login

Image URL: https://qsnapnet.com/snaps/fuc493w93eszia4

This is standard wordpress bevahe. Could you check if with default theme it behaves same?

I tried this on my test site and it worked fine. I believe it is related to SSL that I have implemented on the site that is having issues. Is it common for SSL to cause issues with WordPress functions and plugins?

That is why I have asked you to test the solution on default WP theme. I'm not familiar with this kind of issues on certified sites but perhaps redirect solution itself doesn't work with ssl somehow.
While this is not a standard WP solution, nor our template one, I can't help much more.

Well, it didn't work on the default WP theme either. I did figure it out though, I had to update the login url in the settings. It seems to work now.

Where exactly have you set the login url up?

In the MSocial Template Options > Features. Also, I had my blog set as http instead of https, but I think that was another issue.

Ok, thanks for sharing the solution.