Opened 7 years ago
Closed 6 years ago
#3108 closed defect (bug) (fixed)
Plugin Directory: Logging in from a plugin page redirects to the home page
Reported by: | SergeyBiryukov | Owned by: | Otto42 |
---|---|---|---|
Milestone: | Priority: | normal | |
Component: | Login & Authentication | Keywords: | has-patch needs-testing |
Cc: |
Description
- If you're logged in, log out.
- Go to a plugin page like https://wordpress.org/plugins/akismet/.
- Click Log In in the Toolbar.
- Upon login, you're redirected to https://wordpress.org/plugins/ instead of the plugin page.
Attachments (1)
Change History (13)
#2
follow-up:
↓ 3
@
7 years ago
There's nothing wrong with the SSO class. If it's being passed the wrong redirect_to link, then that's the problem.
#3
in reply to:
↑ 2
@
7 years ago
Replying to Otto42:
There's nothing wrong with the SSO class. If it's being passed the wrong redirect_to link, then that's the problem.
Shouldn't it redirect to the previous page by default? The workaround in [4613] doesn't seem specific to the forums, is there a reason the SSO class can't parse $_SERVER['REQUEST_URI']
itself?
#4
@
7 years ago
Shouldn't it redirect to the previous page by default?
Well, yes, but in this case it's actually sending a redirect_to with just the /plugins/ URL. So it's still getting the wrong URL from the plugins directory.
I'll look into it.
#8
@
6 years ago
- Resolution fixed deleted
- Status changed from closed to reopened
I just ran into that weird WPOrg_SSO
while trying to find out why I'm not being redirected to my profile when using wp_login_url()
.
This is clearly an issue with WPOrg_SSO::login_url()
being used as a callback to the login_url
filter and not handling the passed parameters correctly.
Is WPOrg_SSO::login_url()
used anywhere other than as that filter callback that prevents us from just fixing the parameters?
#9
@
6 years ago
- Keywords has-patch needs-testing added
@SergeyBiryukov @Otto42 Would you mind testing my patch on your sandboxes and see if it needs adjustment?
#10
@
6 years ago
@SergeyBiryukov @Otto42 I'd like to land this this week, do you think you'll have time to take my patch for a spin today or tomrrow?
Support forums apparently have a workaround for this, added in [4613]. We could probably add a similar workaround to the Plugin Directory, but it seems like something that should be fixed in the
WPOrg_SSO
class itself.