mkaand
Forum Replies Created
-
Hi @theokefal
You should disable cookie based login page option and you should enabled redirect login option. Then you can use Peter’s plugin. Peter’s Plugin settings:
All other users section Logout URL:
[variable]http_referer[/variable]That’s it.
Thank you for your support. I hope developers can improve cookie based protection setup. Currently my secret showing at front-end. I don’t like it but It is OK. Developers also improves logout function. Without Peter’s plugin I cannot fix the issue. (I don’t want to modify core files)
Hi Again,
I fixed that issue with installing extra plugin called:
Peter’s Login RedirectI added following variable in to settings of Peter’s plugin:
All other users section Logout URL:
[variable]http_referer[/variable]Without any modification at core files, after logout user redirects to http referrer webpage. It works perfectly. I highly recommend Peter’s plugin for AIO WP Security users
Hi Again,
After my test I can clearly say this is not related with theme it is related with AIO WP Security plugin. I researched a lot and I read following topics (same issue reported before you)
I added following code to core functions.php and it works but I don’t like this solution. Because I do not want to modify core files. I am still looking for solution.
add_action(‘wp_logout’,’auto_redirect_after_logout’);
function auto_redirect_after_logout(){
wp_redirect( home_url() );
exit();
}Still working on it. I see this:
Maybe its related with theme? I just wonder why after logout it redirects to https://mysite.com/wp-admin/index.php
This is also related your plugin I guess. Because if I disable your plugin people can logout easily. Please help me. Thanks.
P.S. NGINX issue solved but other issue still continue.
Update:
I add following lines to my nginx.conf file proxy section:
proxy_buffer_size 128k;
proxy_buffers 4 256k;Problem solved but another problem show up. Now I do not see bad gateway error and no more above log in header. But after logout user redirects to https://mysite.com/wp-admin/index.php
And page says Not Available.
No new error and no more big header error at logs.
Hi,
Now its better, user can logout but I see Cloudflare Bad Gateway error after logıut. And user should go back to site manually. Here is the log:
2020/04/21 11:37:29 [error] 32545#32545: *162588 upstream sent too big header while reading response header from upstream, client: xx.xx.xx.xx, server: mega-mount.com, request: “GET /xxxxxxx/?action=logout&redirect_to=https%3A%2F%2Fmega-mount.com%2Fen%2Fmy-account%2F&_wpnonce=xxxxxxxxxx HTTP/1.1”, upstream: “http://xx.xx.xx.xx:8080/garip/?action=logout&redirect_to=https%3A%2F%2Fmega-mount.com%2Fen%2Fmy-account%2F&_wpnonce=xxxxxxx”, host: “mega-mount.com”, referrer: “https://mega-mount.com/xxxxxx/?action=logout&redirect_to=https%3A%2F%2Fmega-mount.com%2Fen%2Fmy-account%2F&_wpnonce=yyyyyyyyyy”
wpnonce parameter returns different xxxxxxx and yyyyyyy
Hi,
I tried what you said but it doesn’t work. It redirects to my home page now but user still logged in. Only way to logout clear cookies.
I use Secret Word also in same page. What I should do more? I can open you an account for testing if you wish.
Edit: Thank you very much for fast answer.
- This reply was modified 4 years, 11 months ago by mkaand.