shaiful inquired about the functionality of the Path to your Login Page setting in the WP-Discourse plugin while using DiscourseConnect. They expected that setting the path to a dedicated Sign In page would redirect users to that specific URL (e.g., /sign-in) upon clicking Login in Discourse. However, users were instead being redirected to the WordPress homepage with SSO query strings. darkpixlz suggested that WordPress might be handling the redirect to the redirect_to endpoint, while angus hypothesized that local networking issues were the root cause, referencing a similar known issue. shaiful acknowledged the suggestions and confirmed their original assumption regarding the setting’s intended behavior. Ultimately, shaiful resolved the issue, determining it was caused by the Memberium membership plugin, which manages user authentication. They implemented a temporary fix by creating a custom WordPress plugin to patch redirects and URL encoding while awaiting an official solution from the Memberium developers.
I am using Wordpress as the identity provider for Discourse using DiscourseConnect.
In the WP-Discourse > DiscourseConnect Provider setting, how does the Path to your Login Page field work?
I set it to my dedicated Sign In page expecting that when someone clicks the Login button in Discourse they will be redirected to the /sign-in page in WP but it’s not happening in my case. Discourse brings the user to the WP homepage with some query string for example http://wp.test/?redirect_to=/?sso=abc&sig=123&qwe=456.
I set it to my dedicated Sign In page expecting that when someone clicks the Login button in Discourse they will be redirected to the /sign-in page in WP
I have confirmed that is indeed how the setting is supposed to work.
Anyway this issue is caused by the membership plugin we are using called Memberium that also manages user auths. We have resolved it temporarily by creating a custom WP plugin to patch redirects and URL encoding while the official plugin devs work on an official fix.