|
Matthew McDavid
|
February 16, 2022 at 12:15 pm
Greetings. We are upgrading our site to EE4 after ten years with EE3. We are still in the implantation phase, so this is not time sensitive. Our staff will be using the Android and iOS EE app to check-in attendees. We are testing this now. We have run into the familiar “Sorry, you are not allowed to list events. Missing permissions:…” error. Our host, WP Engine, deprecated .htaccess, however, through their help desk we added the prescribed “fastcgi_pass_header Authorization;” rule to the nginx server. No change. We have utilized Application Passwords. No change. I have used my super-admin (our WP install is multisite) login. Same error. I created a new user, set role as editor, added the User & Roles plugin to insure the Editor Role had the appropriate permissions. No change.
On all occasions it appears I can login to the app successfully then the “missing” error appears, but it displays (pops up) three consecutive times. I have to hit “ok” three times to clear the three identical pop ups. I do not know if this is a clue.
The specific error message reads:
Sorry, you are not allowed to list events. Missing permissions: ee_read_events, ee_read_others_events, ee_read_private_events This operation couldn’t be completed. Sorry, you are not allowed to list events. Missing permissions: ee_read_events, Ee_read_others_events, ee_read_private_events
I am submitting a support token to obtain hands-on help as I understand this is a typical issue and I believe I have attempted all the troubleshooting options to no avail.
|
|
Matthew McDavid
|
February 20, 2022 at 7:20 pm
The support token request regarding this post has not been acknowledged. Please advise.
|
|
Tony
|
February 22, 2022 at 7:22 am
Hi there,
My apologies for not keeping you in the loop, I have been looking into this I just assumed with you mentioning it wasn’t time-sensitive I didn’t need to update until I found a solution (silly call on my part now that I read that back!).
So right now, it looks like the Authorization header isn’t making it through, but the responses on your site are a little… strange.
Normally when the above happens the site will return an permissions error because the auth header is missing and so the request is not logged in. On your site, its returning an error about the password not being a valid application password, which doesn’t really make sense currently and I’m trying to track down the cause.
Am I ok to install the REST API Log plugin on the site to see if that shows anything?
|
|
Matthew McDavid
|
February 22, 2022 at 2:21 pm
Tony, thank you for the update 🙂 , yes, installing the REST API will be ok, please deactivate when finished. The EE app is an important feature for us, I do hope we can solve this.
|
|
Matthew McDavid
|
February 24, 2022 at 2:18 pm
Any update on our app connectivity issue?
|
|
Matthew McDavid
|
February 28, 2022 at 3:07 pm
Greetings. Our registrations go live this week, we’ll be needing to train our staff on the new app, any news on a fix? Thank you for your help on this matter.
|
|
Tony
|
March 1, 2022 at 2:06 pm
Hi there,
Just noting that I haven’t forgotten about you and this issue is weird, everything on the request looks valid. The fix from WP Enginge doesn’t allow the HTTP_AUTHORIZATION header to pass, but there is one in the query string which should be working.
I’ve asked one of developers for some feedback on this.
|
|
Matthew McDavid
|
March 1, 2022 at 9:17 pm
Tony, thank you! Reach out to WP Engine if prudent, their 24/7 help desk has been beneficial to us. I provided access in the token request.
|
|
Matthew McDavid
|
March 3, 2022 at 12:46 pm
Tony, our site is displaying the following text on the front and back end. This is new in the last 12 hours, while we have not been working on the site. The text goes away when EE4 is deactivated, not sure if this is related to your work.
string(7) “/socal/” array(1) { [0]=> string(7) “/socal/” } string(5) “socal” string(7) “/socal/” array(1) { [0]=> string(7) “/socal/” } string(5) “socal” string(7) “/socal/” array(1) { [0]=> string(7) “/socal/” } string(5) “socal” string(7) “/socal/” array(1) { [0]=> string(7) “/socal/” } string(5) “socal”
|
|
Tony
|
March 3, 2022 at 1:45 pm
Hi Matthew,
The app should now be working, this was a fairly deep issue caused by the MultiSite setup you’re using.
The additional path from that setup throws out the check for the WordPress and EE API requests within Event Espresso, which meant the basic-auth plugin we bundle into Event Espresso then didn’t load. That would then mean basic auth didn’t run at all (which explains why you were getting a different error to what I expected).
That also meant that anywhere checking for/using the REST API to communicate with Event Espresso, failed to load correctly as the checks to confirm the request was for the REST/EE API would then return false.
Anyway, I’ve applied a patch to the version of Event Espresso you are using to fix this on your site BUT, it’s not something we can include in core currently as it has the potential of causing issues elsewhere, we are still investigating this and the differences between your site and out test sites (the test sites work as is)
Can you confirm if the app is working on your end please?
I’ve installed 2 plugins on your site, the REST API Log plugin and a custom plugin I used to force the application passwords to not load on that site (which is no longer needed) which are now de-actived.
Would you like me to remove those or would you prefer to do so yourself? (As its removing something from the site some people prefer to do it themselves)
|
|
Matthew McDavid
|
March 4, 2022 at 1:23 pm
Tony, I now have access to events using the app! When I select an event on the app and attempt to check-in a registrant, I get the following error: “unsupported URL”, so, although I have access to the events I cannot check-in attendees.
Thank you for this patch! If Event Espresso is updated, would this erase your patch?
I will address the plugins, thank you.
|
|
Tony
|
March 4, 2022 at 1:29 pm
Hmm, I didn’t want to alter any of the attendees previously.
I’ll check into this, does it matter which attendees I test or are they all test registrations?
|
|
Matthew McDavid
|
March 4, 2022 at 4:28 pm
these events are not until May, incidentally, I just deleted my test registrants. Feel free to add your own test registrants.
|
|
Matthew McDavid
|
March 10, 2022 at 2:25 am
This reply has been marked as private.
|
|
Matthew McDavid
|
March 14, 2022 at 3:07 pm
Hi Tony, checking in about marking as attended still showing “unsupported url” thank you for your help!
|
|
Tony
|
March 16, 2022 at 8:04 am
Hi Matthew,
We are working through some changes to core for this type of setup, I’ll keep you posted.
|
|
Tony
|
March 23, 2022 at 7:09 am
Hi Matthew,
Apologies for the delay, this took some digging!
We’ve applied a patch to the version of Event Espresso running on your site which should fix the above issues.
Can you please confirm if the app now works for you?
|
|
Matthew McDavid
|
March 25, 2022 at 12:04 am
Greetings Tony,
A while ago the ios app began returning the former error. It had worked for a time as of 3/4 although we could not change attendance status. I have updated EE4 to the current version today and the problem persists. I presume your patch was unique to our install and with future updates the patch will disappear. – As of right now the app is inoperable for us. Please advise, thanks.
|
|
Tony
|
March 25, 2022 at 7:26 am
I have updated EE4 to the current version today and the problem persists. I presume your patch was unique to our install and with future updates the patch will disappear. – As of right now the app is inoperable for us.
The patch was added within EE4 itself so will have been lost when you updated the plugin, so right now you’ll be testing the app as it was before my patch/fix.
I’ve re-applied the change on the site again, can you retest now?
|
|
Tony
|
March 25, 2022 at 7:27 am
This reply has been marked as private.
|
|
Matthew McDavid
|
March 25, 2022 at 1:21 pm
Thank you for reapplying the patch, we have access again. I am logging in with the full URL and check-in still reports ‘unsupported url’
|
|
Tony
|
March 25, 2022 at 2:33 pm
This reply has been marked as private.
|
|
Matthew McDavid
|
March 25, 2022 at 5:31 pm
This reply has been marked as private.
|
|
Tony
|
March 26, 2022 at 2:56 am
Hi Matthew,
The video doesn’t show that error?
|
|
Matthew McDavid
|
March 27, 2022 at 1:10 pm
This reply has been marked as private.
|
|
Tony
|
March 28, 2022 at 3:38 am
This reply has been marked as private.
|
|
Matthew McDavid
|
March 28, 2022 at 12:46 pm
It works!! I deleted the app and reinstalled it. We are up and running! May I have the patch code and minor instructions to reapply in the event up wanting to apply EE4 app updates in the future? – Y’all have been a great help and I am very appreciated of your help forum. Utilizing this app is going to significantly boost our efficiency!
|
|
Tony
|
March 29, 2022 at 4:23 am
May I have the patch code and minor instructions to reapply in the event up wanting to apply EE4 app updates in the future?
I have no objection to posting the change I’ve made, however, we are applying the change to EE4s core code and so it will be included within Event Espresso shortly (likely within the next update) so you shouldn’t need to reapply a patch.
I’ll post details if you still want them? Its a relatively simple change.
Y’all have been a great help and I am very appreciated of your help forum. Utilizing this app is going to significantly boost our efficiency!
That’s great to hear 🙂
|
