Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
JSON feed is blank | Event Espresso - Staging Server

Support

Home Forums Pre-Releases JSON feed is blank

JSON feed is blank

Posted: April 29, 2013 at 5:47 pm

Viewing 7 reply threads


Daniel

April 29, 2013 at 5:47 pm

After updating to the latest pre-release of the API plugin I haven’t been able to log into the iPad app. When I look at the test link to see the JSON output it just comes up blank.

I’ve completely removed the plugin and re-installed it but nothing seems to work.

Any ideas what it could be?


Dean

  • Support Staff

April 30, 2013 at 4:53 am

Hi,

Have you changed the addons settings to be public?

If so and it is still blank, can you provide a link please?


Daniel

April 30, 2013 at 9:00 am

It is set to public.

Here is the link


Seth Shoultes

  • Support Staff

April 30, 2013 at 9:26 am

It kind of sounds like a memory issue. I have a few questions:

  • What version of Event Espresso are you running?
  • How many events are in your system?
  • Do you have access to your error logs?
  • Can you turn on debugging in your wp-config.php for a short time to check for errors?


Daniel

April 30, 2013 at 9:40 am

I’m running on 3.1.31.3.P

I only have 3 events active currently but about 10-15 archived.

This shows up in my error log when accessing the feed:

[30-Apr-2013 10:34:36] WordPress database error Table ‘livingni_wrd12.wp_events_attendee’ doesn’t exist for query SELECT COUNT(id) FROM wp_events_attendee made by require(‘wp-blog-header.php’), wp, WP->main, WP->query_posts, WP_Query->query, WP_Query->get_posts, WP_Query->parse_query, do_action_ref_array, call_user_func_array, EspressoAPI_Router->template_redirect, EspressoAPI_Generic_Controller->handleRequest, EspressoAPI_Generic_Controller->generalRequest, EspressoAPI_Generic_Controller->generalRequestGet, EspressoAPI_Generic_Resource_Facade_Read_Functions->getMany
[30-Apr-2013 10:34:37] PHP Fatal error: Call to a member function get() on a non-object in /home1/livingni/public_html/wp-includes/cache.php on line 113

I also found this from a while back:

[28-Mar-2013 21:14:19] PHP Fatal error: Cannot redeclare class EspressoAPI_MethodNotImplementedException in /home1/livingni/public_html/wp-content/plugins/espresso_api-pr/includes/helpers/EspressoAPI_Exceptions.php on line 5


Josh

May 1, 2013 at 9:46 am

Hi Daniel,

That is a bug in the current version of the API. What’s happening is the table prefix is hardcoded in as “wp” but that doesn’t account for a different prefix. We’ll be releasing an update that will fix this shortly.


Shawna Brown

May 2, 2013 at 10:43 am

I am also getting a blank JSON feed when I do the test link.  When do you expect that this bug will be resolved?


Seth Shoultes

  • Support Staff

May 2, 2013 at 11:08 am

Should be released today.

Viewing 7 reply threads

The support post ‘JSON feed is blank’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Event Espresso - Staging Server