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
API Pricing Name | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium API Pricing Name

API Pricing Name

Posted: March 6, 2013 at 1:06 pm

Viewing 14 reply threads


Adam Harris

March 6, 2013 at 1:06 pm

I’m using the Event Espresso API Plugin to retrieve data for a mobile app. It works great, but I’m trying to get the pricing data for an event that has 3 pricing options (Single Participant, Family (Head of Household), Additional Family Members)), but when I retrieve the data, I can’t see the names. All I can see is Members Admission, or Member Price as shown below:

<code>"Prices": [
      {
        "id": 78.2,
        "name": "Members Admission",
        "amount": 250,
        "description": null,
        "limit": 30,
        "remaining": 17,
        "start_date": null,
        "end_date": null,
        "Pricetype": {
          "id": 4,
          "name": "Member Price",
          "is_member": true,
          "is_discount": false,
          "is_tax": false,
          "is_percent": false,
          "is_global": true,
          "order": 0
        }
      },
      {
        "id": 79.2,
        "name": "Members Admission",
        "amount": 0,
        "description": null,
        "limit": 30,
        "remaining": 17,
        "start_date": null,
        "end_date": null,
        "Pricetype": {
          "id": 4,
          "name": "Member Price",
          "is_member": true,
          "is_discount": false,
          "is_tax": false,
          "is_percent": false,
          "is_global": true,
          "order": 0
        }
      },
      {
        "id": 77.2,
        "name": "Members Admission",
        "amount": 150,
        "description": null,
        "limit": 30,
        "remaining": 17,
        "start_date": null,
        "end_date": null,
        "Pricetype": {
          "id": 4,
          "name": "Member Price",
          "is_member": true,
          "is_discount": false,
          "is_tax": false,
          "is_percent": false,
          "is_global": true,
          "order": 0
        }
      }
    ]
</code>

How can I get the correct names?


Jonathan Wilson

  • Support Staff

March 6, 2013 at 2:02 pm

Hi Adam,

It looks like you have Member prices added to the event. This could be causing the problem. Try checking for that and removing the member prices.


Adam Harris

March 6, 2013 at 2:12 pm

I’m sorry, but I don’t understand exactly. What do you mean by Member prices added to the event and how do I remove them?


Chris Reynolds

  • Support Staff

March 6, 2013 at 2:20 pm

Your events are going to have member prices if you have the WP User Integration add-on active. You can set the member prices to be the same as the general admission prices if you want or deactivate the WP User Integration add-on if you aren’t planning on using it.


Jonathan Wilson

  • Support Staff

March 6, 2013 at 2:20 pm

In Event Espresso > Event Overview select your event. You will then probably see event prices here: http://awesomescreenshot.com/00610jpp7d

Those need to be removed, or the names need to be changed.


Adam Harris

March 6, 2013 at 2:23 pm

I’m not using the User Integration Add-on. As far as Event Espresso goes, I’m only using:
Event Espresso
Event Espresso – Multi Event Registration
Event Espresso API Plugin


Adam Harris

March 6, 2013 at 2:32 pm

Jonathan, I don’t see that Member Pricing section. All I have is a standard pricing section. Here’s a screenshot:
http://awesomescreenshot.com/04410jrn4a


Seth Shoultes

  • Support Staff

March 6, 2013 at 10:17 pm

It looks like the API might have a bug in it, so it is returning the wrong price values. I created a ticket for our developers to look into it.


Michael Nelson

  • Support Staff

March 7, 2013 at 12:21 pm

yes this was a bug in the API. Even though the members addon wasn’t active, members prices are actually still saved in the DB, and were getting returned instead of the normal prices.
I just made a fix for this bug and am getting it tested. The next release of the API will correctly return the price names, and only return the members prices if that addon is active.
Thanks for reporting the bug Adam!


Adam Harris

March 22, 2013 at 10:47 am

Any news on when the next release of the API will be available?


Josh

March 25, 2013 at 9:59 am

Hi Adam,

It still needs to go through some testing. Would you to try out the latest build? If so we can email you a copy of it.


Seth Shoultes

  • Support Staff

March 25, 2013 at 10:00 am

I don’t think we have posted the latest build of the API or iOS app yet.


Seth Shoultes

  • Support Staff

March 25, 2013 at 10:57 am

Hopefully we can release an update today.


Adam Harris

March 25, 2013 at 1:34 pm

Yes, Josh, I would love to receive the latest build. adam@adamwadeharris.com


Seth Shoultes

  • Support Staff

March 25, 2013 at 2:10 pm

The update to the JSON API is in the pre-release channel.

Viewing 14 reply threads

The support post ‘API Pricing Name’ 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