|
Gregoria Lara
|
April 19, 2014 at 12:11 am
I got the ticket scanning app / API to work literally for one evening. The next day, it stopped connecting. Try as I might, it won’t connect to the endpoint anymore. I tried everything: bumping PHP max execution time, set memory a bit higher… Nothing. Everything else in EE3 (latest version) works perfectly. It’s “just” the ticket scanner that won’t budge and frankly that’s a bit of a disappointment as it was a catchy reason to go with EE… What checklist of common problematic areas can I follow to troubleshoot this? Thanks in advance! (Oh, and the /espresso-api/v1/events/public.pretty_json testpage looks good to me, with a clean status 200)
|
|
Lorenzo Orlando Caum
|
April 19, 2014 at 5:23 pm
Hi there Gregoria,
You should not have sporadic issues with the App.
Have you recently made any changes to your site such as installing or updating any plugins?
Please double-check that your JSON API is set to public (try re-saving the setting in the WordPress admin).
Next, please ensure that you are logging into the app with a WordPress administrator login and that the endpoint URL is set to your site URL.
—
Lorenzo
|
|
Gregoria Lara
|
April 19, 2014 at 11:14 pm
Thanks Lorenzo, but that doesn’t brink the app back to life.
– Disabled as many plugins as I could but nope, no change
– JSON API access is set to public (frankly it baffles me why that would be necessary, with the app’s user/pass the API access should definitely be non-public!) and that doesn’t make any difference, either
– Try to log in with WP admin and EE Event Admin users and still nothing.
Goodness knows what happened here…
Having said that, here’s a side note: I suggest looking into the convenience of setting up a separate type of EE API user role for EE with carefully selected capabilities so that logging in with either WP admin (ouch!) or even EE Event Admin isn’t necessary. Think about staff at the door… Should they be using WP admin or even EE Event Admin creds? I don’t think so! That’s dangerous, frankly, all the more with the “public” API setting.
|
|
Gregoria Lara
|
April 20, 2014 at 2:40 pm
OK I think I have the culprit. It’s actually within EE3 itself, i.e. the user permissions settings which I had reset to their default values. If you do that you lock out access to the API. From what I can tell you need to give the EE Event Admin access to the various settings pages. This is something that in my opinion should be more clearly advertised, with regard to use in conjunction with API access and the HD app.
|
|
Gregoria Lara
|
April 20, 2014 at 3:06 pm
There was also a problem caused by two plugins that affect XML-RPC: Duo Security and WP Email Login. I don’t mind too much not being able to have users log in with their email address (annoying but not a show stopper) but no Duo Security? Not so happy with that. I really like to have 2-factor authentication because it’s the only way I have some measure of certainty that higher access users using weak passwords are protected from themselves. And of the 2FA plugins out there, Duo Security is really fantastic. I’ll see if I can work around it but I really want 2FA switched on.
Anyway – for purposes of the issue that prompted this ticket / topic, I’ll consider it resolved / closed now.
|
