|
Mark Mangoba
|
September 26, 2014 at 11:41 am
After adding the JSON API plugin, the settings show up on my admin, but going to the test url results in a 404 error. The espresso-api folder does not exist on the server either.
|
|
Josh
|
September 26, 2014 at 12:37 pm
Hi Mark,
Do you have EE3 and the Espresso JSON API plugin installed on a publicly accessible web server? Along with that, you’ll need to make sure that WordPress is set up to structure postname permalinks.
You will not need the espresso-api folder if you have the HD iOS app. The HD app is currently on version 1.6.4. Any other version isn’t the HD app.
|
|
Mark Mangoba
|
September 26, 2014 at 1:48 pm
Sorry for the lack of details.
But I’m running on IIS 7.5
It is on a publicly accessible server.
And the WordPress is set to postname permanlinks.
I am also using the HD iOS app.
However, it worked perfectly fine when I setup the WP on Amazon AWS with Bitnami WP.
I’m running on WordPress 4.0 with EE3 and JSON API 2.1.3 and Espresso Ticketing 2.1
Also on the iOS app, the login returns 404 error.
|
|
Lorenzo Orlando Caum
|
September 26, 2014 at 2:00 pm
Hi Mark,
Would you happen to have access to an Apache or Nginx server?
We’ve seen issues with Windows IIS based servers in the past so we no longer recommend them:
https://eventespresso.com/requirements/
—
Lorenzo
|
|
Mark Mangoba
|
September 26, 2014 at 2:20 pm
I see. I’m running on AWS currently, but it’d be most ideal to host it inhouse. Is there anything I can try with IIS while I spin up an Apache?
|
|
Josh
|
September 26, 2014 at 6:37 pm
Hi Mark,
I’m afraid that if you try to make JSON API work on IIS you’ll end up with at least a few headaches. Apache or nginx are the two server platforms we develop, test on, and support.
|
