Support

March 10, 2014 at 3:55 am

Hi Bob,

You should not need a different setting for Android.

Can you tell me which Android device did you use and the firmware version please? (Settings -> About Device)

March 10, 2014 at 8:14 am

The JSON API is now used in both HD versions of the App (Both iOS and Android)

‘espresso-services’ is how the ‘old’ versions of the Android app connected to the WordPress site. (iOS has always used the API) If the Android phone could not connect without the espresso-services folder then that phone still has the older version of the app. The one that did work was likely using the HD version and as such the JSON API.

This is the latest version for Android:

https://play.google.com/store/apps/details?id=com.eventespressoHD.android

Check that is the current version for any of the Android phones you are using. You will then not need to use espresso-services and all should work well.

The fact that the iOS devices are working shows the API is correctly setup, so once the Android App’s are updated all should be well.

If not just let us know and we can investigate further.

March 10, 2014 at 8:42 am

Can you link me to the site please? I’d like to take a look at the API response.

If you would prefer to keep the site off the forum just send and email to support@eventespresso.com with a reference to this thread.

March 10, 2014 at 9:54 am

Can you go to Event Espresso -> API Setting.

Change ‘Allow Public API Access?’ to Yes and save the settings please.

Also, is it possible for you to provide some temporary log in details for me to login via the Android app?

Is so please send via https://eventespresso.com/send-login-details/

March 11, 2014 at 2:35 pm

Hi Bob,

I checked with the credentials you sent and what it looks like is this isn’t a user account that has access to Event Espresso. That may explain why one user was able to view events and others were not. What you can try doing is logging into the Android app with an admin user account.

March 11, 2014 at 3:44 pm

I think that’s one area where the iPhone app and the Android apps differ. Can you try logging into the Android app with an account that has full admin access?

March 12, 2014 at 7:26 am

Hi Bob,

Also something to note, to test the JSON API you should be able to go to this page:

http://linnareaphotoclub.org/espresso-api/v1/events/public.pretty_json

When public access was NOT enabled this message should (and was) be displayed:

{
  "status": "Not authorized to access that endpoint",
  "status_code": 403
}

Now that public access has been enabled when that page is viewed the Server throws Error 500 – Internal Server Error which is not normal/expected.

Error 500 is a general error which basically means ‘something’ went wrong on the server.

I noticed you have caching enabled on the site, you could try disable caching, then purge (delete) the cache. Simply de-activating the plugin does not help caching issues as the cache is still active after the plugin has been disabled.

Then flush the Permalinks, go to Settings -> Permalinks. Do not make any changes and hit save. Then see if the URL above loads.

It could also be any number of active plugins, you could try temporarily disabling all plugins and view the URL above to see if it then loads. If so activate each plugin one-by-one refreshing the page in between until it stops working. Then report back which plugin caused this so we can investigate.

March 12, 2014 at 1:07 pm

Hi Bob,

Can you tell me the version number of NextGen, Download Monitor and the Espresso API please?

We have found a bug with the API and NextGen previous which is fixed in the latest version of the Espresso JSON API Add-on.

Download Monitor we’ve not had issues with before but will investigate.

As for the App, as long as that page works the Android app should also work correctly. We have issued a ticket to investigate why the Android app and iOS app differed in this situation.

March 14, 2014 at 4:38 pm

Hi Bob,

I have the NextGen and Download monitor plugins installed on my test site and the JSON API feed continues to work as expected. I do see that the memory usage on my site goes up with these two additional plugins installed, so your server may be running low on memory and deactivating those two frees up enough memory to allow the JSON API to not time out.

March 17, 2014 at 9:30 am

Hi Bob,

Can you check with your host to see if you’re really getting 256M of ram? Sometimes if you set a value for the memory limit in the wp-config.php file the host will override this to a lower amount.

March 19, 2014 at 2:02 pm

That’s interesting Bob. The thing is, I can activate NextGen, Download Monitor, and the JSON api all at once and the feed continues to work. That said, when we get then next update to the Android app that may help with the other issue you were having.