I’m experiencing a consistent issue with the login functionality on the homepage of Varaderoparadise.com. Symptom: the user logs in successfully, but the homepage still shows the “Log in / Register” link. When navigating to any other page, the menu updates and correctly displays the account area, confirming that the login itself is valid.
I have carefully applied all the recommendations shared by HivePress in previous threads reporting the exact same behavior with LiteSpeed Cache. However, the issue persists with any combination of those settings; the only way to fully resolve it is by completely deactivating the LiteSpeed Cache plugin.
Thanks for the details. We registered a user named “test123” on your website and tested everything in detail, but we were unable to reproduce the issue. As soon as you can reproduce the issue on your end, and after logging in, the Sign in button is still displayed, please send us the URL of this page (after you have entered your details and clicked Sign in), and we will investigate further.
i have a slightly different issue. Login has to be done twice to be able to actually login with the Social Login on Google.
I am not able to use the other Social Logins like Facebook etc at all.
If any users here have correctly configured it for anything other than Google, please share how you did it. Thanks
I have communicated with Litespeed support and they responded as follows and resolved the issue for me:
“this happens because your site theme is using POST /wp-json/hivepress/v1/users/login/ to do the login action , unlike normal wordpress site that doing the POST to the page itself
and our plugin will set a cookie _lscache_vary to identify and vary the login users , however , because the login happens takes place on that wp-json URI, so such cookie didn’t set”
“ I added the wordpress’s default login cookie to Cache → Advance → Vary Cookies , as my screenshot”.
Thank you for your solution, it will be useful for the community. However, please note that HivePress already excludes the Veray feature. You may have customized the code or the plugins are being loaded in some other way (for example, you have a multisite installation).
