OAuth Redirect to blog archives, not wp-admin

[John]

When validating the plugin with my application on Eventbrite, the redirect uses the correct URL, with a code parameter appended: /tribe-oauth/eventbrite/?code=XXX. This parameter somehow forces the redirect to the blog archives page instead of wp-admin. Without the parameter, the redirect is to the homepage.

I have also attempted this locally and the redirect worked just fine. Can you offer any insight into the logic of the /tribe-oauth/eventbrite URI and why it may be behaving this way?

[Brian]

Hi,

Thanks for using our plugins. I can help out here.

Are you having issues importing or registering events because of this redirect?

I am not exactly sure what the issue is.

Visiting the OAUTH url should go to your home page:

http://yoursite.com/tribe-oauth/eventbrite/

But that is all used by the coding so there is no reason to visit the url.

Let me know and we can go from here.

Thanks

[John]

This reply is private.

[Brian]

Ok, since it is not working because of the redirect I would try first following the steps in our 404 Error Guide and see if resaving the permalinks fixes the issue.

https://theeventscalendar.com/knowledgebase/fixing-http-404-errors/

If that does not help please follow the Testing for Conflicts Guide and see if that can narrow down the cause:

https://theeventscalendar.com/knowledgebase/testing-for-conflicts/

Let me know what you find out.

Thanks

[John]

But the issue is not a 404 – 404s correctly route to the 404 template. This is a unique case in which only this Tribe-specific callback URL *with* the code parameter renders a blog archives page. Without the code parameter it routes to the homepage.

[Brian]

I get that it is not a 404 issue, but it is a permalink issue so those steps my help or they may not, but at least it would be ruled out.

So can you please follow both guides I linked to and see if either one helps either narrow down or resolve the issue.

Thanks

[John]

I was able to resolve by validating the plugin locally (using my localhost URL as the OAuth callback), then push the database up to production. Not ideal, but it worked.

[Brian]

Ok, glad you found a work around. If you run into trouble in the future I would recommend following those two guides and see if that can narrow down a source.

Since this is marked resolved I am going to close this ticket, but if you need anything else related to this topic or another please post a new topic on the forum and we can help you out.

Thanks

[Leah]

Hello,

Thank you again for bringing this issue to our attention. We’re happy to say that we have added a fix for this into our upcoming version 3.11 release. Keep an eye on your Updates page for the new version. If you have any trouble with the update (or are still seeing this problem after you update) please start a new thread and we’d be happy to help out.

Thank you for your patience while we got this release ready to go!

Best,
Leah
and the rest of The Events Calendar team

[Author]

Posts