|
Rob Mougey
|
September 3, 2018 at 3:09 pm
Hi –
I just downloaded the EE4 app for iPad. After it logs me in, I get a spinner where I assume it is trying to get the event info. After a while it returns what looks like a MySQL error that starts with “The operator ‘<%3D’ is not in the list of valid operators” followed by a list of what looks like all the valid MySQL operators.
The URL is: https://macnaconference.org/2018
A screengrab of the error is at: http://macnaconference.org/2018/wp-content/uploads/sites/7/2018/09/EE4-app-error.png
Any ideas?
Thanks!
|
|
Josh
|
September 4, 2018 at 9:47 am
Hi Rob,
I suspect something on your site does not like the encoded operator. If you hit the OK at the bottom of the error, then switch the view from “Events (All)” to “Events (Upcoming)” does it load up a list of upcoming events?
|
|
Rob Mougey
|
September 4, 2018 at 10:00 am
Hi Josh –
Aha, it looks like it failing consistently with that error when I pick “Today”, but not “Past” or “Upcoming”. When the app initially launches it looks like it is trying to do “All”, but once I click past the error it appears to load “All” (although there’s no spinner or anything so I am not sure if it’s really showing “All” or just redisplaying “Upcoming”).
Hopefully “All” is actually working or else we won’t be able to scan anyone in using “Today”. What did you mean by “something on your site does not like the encoded operator”? What URL is the app trying to hit, so that I can try to debug further?
Thanks!
|
|
Josh
|
September 4, 2018 at 10:16 am
This is a screenshot of the Query parameter that includes the encoded operator:
https://slack-files.com/T02SY781D-FCL468EDN-ed09f1a799
<%3d decodes to be <= but something is happening on your site where it throws an error instead of decoding the operator.
|
|
Rob Mougey
|
September 4, 2018 at 10:38 am
Thanks Josh, that helps – I think I see where things are going wrong. The site was set up with the “events” page being named “attend” instead of “events”. But there is at least one place in the checkout process where it appears to be hardcoded to try to go to “events” (some link during registration to go back to look at more events). So I added a redirect from “events” to “attend”, so maybe the extra encoding is happening during the redirect?
|
|
Josh
|
September 4, 2018 at 10:58 am
I’m not sure how that would be related. All of the requests from the app go directly to the endpoints via the REST API, specifically wp-json/ee/v4.8.36/. Your redirect shouldn’t be affecting GET requests via the API.
|
|
Rob Mougey
|
September 4, 2018 at 10:59 am
Actually, I take that back – the rewrite is only specifically for “2018/events” so should not be messing with any wp-json URLs…
|
|
Rob Mougey
|
September 4, 2018 at 11:01 am
Is it possible we have an outdated version of whatever plugin handles the wp-son URLs, and something in an older version is buggy w.r.t. URL decoding?
|
|
Josh
|
September 4, 2018 at 11:15 am
The REST API is part of WordPress core, is your version of WordPress up to date?
|
|
Rob Mougey
|
September 4, 2018 at 2:56 pm
We’re running the latest WP (4.9.8), so I’m kinda baffled. I’m going to try a RewriteRule to see if I can make this specific sequence of characters work.
|
|
Josh
|
September 5, 2018 at 7:48 am
Normally you should not need to add rewrite rules to allow the decoding. You could try temporarily deactivating all other WordPress plugins (leave just Event Espresso activated) and/or backing up the site’s .htaccess file and just use the standard WordPress rewrite rules in the .htacess file. For example you could make a backup of the .htacess file, then empty the file, then go to your site’s WP > Settings > Permalinks page. Then WP will write its rewrite rules to the .htaccess file. Then you try the app again.
|
