|
Bryce Jacobson
|
May 3, 2016 at 10:16 am
I’m getting an error when clicking on “Attendees” inside of an event.
The error is the following:
Error Occurred
The request was a valid request, but the server is refusing to respond to it. Unlike a 401 Unauthorized response, authenticating will make no difference. On Servers where authentication is required, this commonly means that the provided credentials were successfully authenticated but that the credentials still do not grant the client permission to access the resource (e.g., a recognized user attempting to access restricted content).
The site uses https everywhere. I also tried logging in with two different administrators but get the same error.
EE: 4.8.42
WP: 4.5.1
iOS 9.3.1
Any insight into this would be great.
|
|
Josh
|
May 3, 2016 at 10:37 am
Hi Bryce,
The error message you reported reads like an http 403 forbidden error. Here’s some basic information on how to troubleshoot a 403 error:
https://www.digitalocean.com/community/tutorials/how-to-troubleshoot-common-http-error-codes#403-forbidden
|
|
Bryce Jacobson
|
May 3, 2016 at 4:02 pm
Not having any luck. Checked permissions, disabled other plugins.
Do you know what files/folder the app is trying to access that may need their permissions checked?
|
|
Josh
|
May 4, 2016 at 6:18 am
It’s not a permissions issue as far as files and folders go, the API is outputting events from your site if you go to your-site.com/wp-json/ee/v4.8.36/events/ in a browser.
|
|
Bryce Jacobson
|
May 4, 2016 at 8:15 am
I can see the data at that url. But it’s the attendees list that throws the error when click inside of an event.
Looks like this is the same issue: https://eventespresso.com/topic/error-viewing-attendees-on-app/
|
|
Josh
|
May 4, 2016 at 9:44 am
Hi Bryce,
Can you check your site’s .htaccess file to see if there are any rules for HTTP_AUTHORIZATION there?
|
|
Bryce Jacobson
|
May 4, 2016 at 10:10 am
Nothing of that sort.
I removed everything other then required WordPress lines and still no luck.
|
|
Bryce Jacobson
|
May 4, 2016 at 10:13 am
Went directly to the event attendees list in the json file at it states this error:
{"code":"rest_attendees_cannot_list","message":"Sorry, you are not allowed to list attendees related to Event. Missing permissions: ee_read_contacts","data":{"status":403}}
|
|
Tony
|
May 4, 2016 at 10:25 am
Hi Bryce,
You will get that error if you have not logged in via the api.
How are you viewing the attendees?
|
|
Bryce Jacobson
|
May 4, 2016 at 10:34 am
In that last case I was viewing it just via my desktop directly at
/wp-json/ee/v4.8.36/events/2100/attendees
I’m logged into WordPress as well as an admin. But how do you login via the api? Do I need the OAuth plugin installed on the site as well?
|
|
Josh
|
May 4, 2016 at 11:01 am
You can use the Postman App or the Postman plugin for Chrome and use the Authentication feature to do an API call with authentication.
|
|
Tony
|
May 4, 2016 at 11:13 am
Do I need the OAuth plugin installed on the site as well?
No you do not need the OAuth plugin installed.
|
|
Bryce Jacobson
|
May 4, 2016 at 12:00 pm
I ran it through Postman and I can see the events list just fine (I always have). But the attendees list is still throwing a 403. I tried with and without adding a WordPress user under the Basic Auth (or is that not correct)?
I’m wondering how this would help get the attendees list to show in the Mobile App when all said and done?
Apologies for not fully understanding this.
|
|
Josh
|
May 4, 2016 at 12:14 pm
It doesn’t help get the attendees list to show in the app. The reason I mentioned Postman was because you asked
> But how do you login via the api?
At this point, we do not know why some of the sites are having trouble with authenticating with the API to view attendees. There are a few guesses floating around (rules in the .htaccess file, server configuration, other plugins, restricted capabilities for the user account.)
We’ll update the documentation and this thread when we know more. In the meantime, if you want to continue to troubleshoot this, you could check the .htaccess file on your site for any extra rules beyond the normal WordPress rewrite rules, verify that your WP user account has all capabilities (this can be done with a User Roles Manager plugin), and you could rule out any plugin conflicts that may be affecting the authentication mechanism.
|
|
Bryce Jacobson
|
May 4, 2016 at 12:52 pm
Thanks, looking forward to more details.
I just tried again deactivating all plugins (except EE and EE Tickets) and clearing our the .htaccess file (except default WordPress stuff) with the same results. I can also confirm that the user I am logged in with has “ee_read_contacts” checked in capabilities.
|
|
Josh
|
May 4, 2016 at 12:55 pm
Thanks, this may narrow things down to a server configuration issue then.
|
