Opened 14 years ago
Closed 14 years ago
#3152 closed defect (bug) (fixed)
Redirect at the end of upgrade/install wizard does not work
Reported by: | boonebgorges | Owned by: | |
---|---|---|---|
Milestone: | 1.5 | Priority: | critical |
Severity: | Version: | 1.5 | |
Component: | Core | Keywords: | has-patch |
Cc: |
Description
In the Finish step of the upgrade wizard (step_finish_save() is the name of the method), you get redirected to the BP general settings page. But this redirect seems to happen too soon, perhaps before the rest of BP is loaded, because the BP panel does not load correctly: on single WP, you get the "You do not have permission to access this page" message (refreshing the page will get you there) and on MS you are redirected to wp-admin/network/?c=1
I'm not sure what the solution is. I'm sure this is a load order issue, but given the way that the upgrade functions are conditionally loaded, I'm not certain that there's a way to give them a different priority with respect to the rest of BP. Another possible fix is to redirect back to the main Dashboard (perhaps with an admin notice that says "BP is set up! Click here to change settings"). Not quite as elegant, but easy, and it won't run into the same problems.
Marking critical because, for UX reasons, it really should be fixed one way or another.
Attachments (1)
Change History (8)
#4
@
14 years ago
What problem are you still having? The only problem I had after the patch was a wp_redirect problem where instead of redirecting to example.com/wp-admin/admin.php?=bp-general-settings, it would sometimes redirect to example.com/sub/directory/wp-admin/sub/directory/wp-admin/admin.php?=bp-general-settings which obivously isn't valid. I think that is one of the weird quirks in wp_redirect(). Before the patch, I would get the "You do not have permission to access this page" error, or sometimes the quirk. Was that the same issue you had?
#5
@
14 years ago
I was still getting "You do not have permission to access this page", yeah. I'll test again tomorrow in case I mis-applied the patch. (Using WP 3.1.1 and BP trunk)
This was actually an easy fix. The redirect link was wrong.