Recurring Issue: Login Widget Redirects to “My Account” Without Logging In

Hello Woodmart Support Team,

I am reaching out regarding a recurring issue with direct user login via the Woodmart login widget on my store. The problem has occurred again: after clearing the cache, direct login works properly for a certain period, but after some time it returns. When attempting to log in, the widget redirects users to the “My Account” page without logging them in, forcing them to re-enter their credentials.

I am using the LiteSpeed Cache plugin and have already excluded the “My Account” page from caching. I would appreciate your advice on what additional pages, cookies, or settings I should exclude so that the widget operates correctly and allows users to log in directly without unnecessary redirections.

Thank you for your assistance.

Best regards

Hello,

Please deactivate all the 3rd party plugins and activate only theme-required plugins on the site, and then check the issue. I am sure your issue will be solved. Then activate the 3rd party plugins one by one and check which plugin is creating the issue for you.

Otherwise, if the issue still exists, then keep the 3rd party plugins deactivated and let me know I can check and give you a possible solution.

Best Regards,

Hi,
After deactivating the LiteSpeed Cache plugin, direct login via the widget works normally and users are logged in without issues. However, I need to use LiteSpeed Cache because my server is running on LiteSpeed technology. I assume that there are additional settings or specific pages, cookies, or resources that need to be excluded from caching for the login functionality to work correctly. Could you please advise what exactly should be excluded from LiteSpeed Cache to resolve this conflict?

Hello,

At the moment, we have not observed this specific issue on your site. However, based on how WordPress nonces work, we can assume that the problem may occur if the page cache is not refreshed for more than 24 hours. By default, a wp_nonce has a lifetime of 24 hours, after which it becomes invalid. If a cached page is served with an expired nonce, certain actions (such as form submissions or AJAX requests) may fail. You can read more about this behavior in the official WordPress documentation: https://developer.wordpress.org/apis/security/nonces/#modifying-the-nonce-lifetime

To prevent this, we recommend adjusting your cache plugin settings so that the page cache is refreshed at least once a day. This will ensure that any new nonce values are properly generated and served to users, minimizing the chance of errors related to expired tokens.

Best Regards,

Thank you for your assistance. I will update the cache settings to refresh every 24 hours and monitor how the login functionality performs.
Cheers

Hello,

You’re most welcome! Feel free to reach out anytime if you notice anything else.

Best Regards,

[Author]

Posts