Hi @myactivechild,
Thanks for reporting this and for narrowing it down — that’s really helpful.
The hidden field you’re seeing (members_redirect_to) is generated by the Members plugin as part of its login form output. It’s used internally by the plugin to manage post-login redirect behavior.
The reason it works fine on the standard wp-login.php page but causes issues on your custom login page is likely because the Members plugin hooks into WordPress’s core authentication process to intercept and handle that field. When login goes through wp-login.php, those hooks fire correctly and the field gets processed as expected. On a custom login form that doesn’t go through the same authentication flow, the field may get submitted but never properly handled — which can result in the redirect loop you’re experiencing.
To help us look into this further, could you let us know:
- How is your custom login page set up? Is it using the
[members_login_form] shortcode, the Members Login Form widget, or a completely separate/third-party login form?
- What versions of WordPress and the Members plugin are you running?
That’ll help us figure out whether this is a conflict between the Members plugin and your login setup, or something that needs to be addressed on our end.
Thanks!
Thread Starter
Support
(@myactivechild)
Thank you.
WordPress 6.9.1 and Members 3.2.18.
The login form is from The Events Calendar – Community Submission (tribe_events_community_login)
Hi @myactivechild,
I tried to replicate the issue from my end but looks like I’m missing something, could you please share the more info about the issue? Could you please share your setup?
Regards,