|
amcfamily
|
September 30, 2016 at 7:01 am
We updated from 4.9.12.p to 4.9.13.p yesterday and now the mobile app gives the error “No route was found matching the URL and request method” on login. I can see that it authenticates (it switches from the login screen to the event list view in the background), but it doesn’t load any events.
I’ve tried saving the permalink settings, disabling and re-enabling the Event Espresso plugins, and re-saving the settings. This is using the Event Espresso 4 (v 2.1) app and WordPress 4.6.1.
Any thoughts?
|
|
amcfamily
|
September 30, 2016 at 8:15 am
On further investigation, I tried the following url:
https://www.amcfamily.com/wp-json/ee/v4.8.36/events
and I do get the json list of events as I would expect. It’s just the mobile app refusing to read it for some reason.
|
|
Josh
|
September 30, 2016 at 8:44 am
The app isn’t necessarily authenticating because the API will list events without authentication (as you can see from the URL you posted).
You can try resetting the site’s rewrite rules. You go to the WordPress > Settings > Permalinks page from your WordPress dashboard and WordPress will automatically reset the rewrite rules when the page loads.
|
|
amcfamily
|
September 30, 2016 at 9:42 am
Thanks Josh. I’ve tried saving the permalinks several times, to no avail. Is there any way in the app to see what URL it’s trying to request? I also tried doing a capabilities reset in the Maintenance section without success.
|
|
Josh
|
September 30, 2016 at 10:15 am
Is there any way in the app to see what URL it’s trying to request?
No.
Do you have any security plugins activated on this site?
|
|
amcfamily
|
September 30, 2016 at 11:42 am
I have Wordfence set up, although it made no difference when I deactivated it just now and tried again.
|
|
amcfamily
|
September 30, 2016 at 11:50 am
Is there a way to save the events and settings, remove/reinstall the plugin, and restore the settings and events?
|
|
Josh
|
September 30, 2016 at 11:53 am
There’s some code that Wordfence adds to your server’s .htaccess file that will still execute when Wordfence is deactivated.
You could try renaming the htaccess file and creating a new one with just the basic WP rewrite rules in it.
|
|
amcfamily
|
September 30, 2016 at 12:34 pm
Commented out all the code in htaccess except for the basic rules and deactivated Wordfence. Still no success. I’m trying to think of what else could have possibly changed.
|
|
Josh
|
September 30, 2016 at 12:50 pm
Are you familiar with the Postman app? It’s another way to send an API request to your site, and you can test your site’s basic authorization headers this way.
First, you install the postman app.
Then you send a GET request to this endpoint:
https://www.amcfamily.com/wp-json/ee/v4.8.36/attendees
you’ll need to set an Authorization to Basic Auth, and set your WP Username and Password (or if you’re using the Application Passwords, you can use the Application password). Then you click Update Request, then Send. You might even get a useful error message if there’s trouble with sending those authentication headers.
|
|
amcfamily
|
September 30, 2016 at 1:05 pm
I created the request and passed in the Basic Auth parameters and got back a HTTP 200 with a large json response that looks like all of the applicable attendee data. It appears that the response is good from the site. When I tried intentionally sending bad auth data I got a bad permission error as expected, so it seems to be responding to the data correctly. I’m getting the same error on two devices with two different users (both with full admin rights), so I’m not sure if I should be chasing a plugin or an app error at this point.
|
|
Josh
|
September 30, 2016 at 1:10 pm
May I ask are you using the iOS app or is it the Android app? You might try the other platform if you have a device that runs it.
|
|
amcfamily
|
September 30, 2016 at 1:14 pm
Both devices are Android. I’ll see if I can get access to an iOS device to test.
|
|
amcfamily
|
September 30, 2016 at 1:24 pm
On an iOS device it says “Error Occurred. The requested resource could not be found but may be available again in the future. Subsequent requests by the client are permissible.” It must be something at the site end then.
|
|
Josh
|
September 30, 2016 at 2:12 pm
Have you gone through the troubleshooting checklist outlined in the documentation:
https://eventespresso.com/wiki/ee4-event-apps/#troubleshooting
|
|
amcfamily
|
September 30, 2016 at 2:59 pm
I went through the suggested steps. We have active events, the plugins and WordPress are completely up to date and activated, we’re using /%category%/%postname%/ as the permalink setting (which has worked fine for the past several months), we’re not using the iTheme security, we don’t have any old Event Espresso JSON plugins, and I’ve tried both variants of the Apache rewrite rules in .htaccess.
|
|
Josh
|
September 30, 2016 at 3:04 pm
There’s only one variant of the Apache rewrite rules that should be tried.
You could try reverting to 4.9.12.p to see if it was in fact updating to 4.9.13.p that caused the apps to no longer work.
https://github.com/eventespresso/event-espresso-core/releases/tag/4.9.12.p
If that doesn’t help, you could contact your host to see if they’ve changed anything server-side, like the firewall, since the time it was working.
|
|
RJG
|
October 1, 2016 at 12:16 am
I’m having the same issue and none of the troubleshooting steps have helped.
|
|
Josh
|
October 1, 2016 at 8:16 am
@RJG Have you checked with your host about the firewall? Is your server apache or nginx?
|
