|
Ben Magro
|
July 7, 2014 at 7:02 am
Currently when using the JSON API venue data is empty.
I’m seeing this on all events. I am not using the event manager, though all events have data in:
Additional Event/Venue Information:
Physical Location and Venue Information sections.
|
|
Dean
|
July 7, 2014 at 8:26 am
Hi Ben,
To clarify are you using EE3 or EE4? Also are you using the Venue Manager for the venues?
Can you provide a site link?
|
|
Ben Magro
|
July 7, 2014 at 4:55 pm
We are using EE3
We are not using the venue manager. Though venua data is being stored in the sections I mentioned in the above post.
The site is here:sydneycraftbeerweek.com
|
|
Dean
|
July 8, 2014 at 1:39 am
Hi,
Thanks for that.
Your JSON is offline so I can’t check your site, but I checked a test site and it appears fine, though it does not appear under venue data http://take.ms/QAK8E
I would recommend using the Venue Manager though as it tends to be much more flexible both in general use and with the JSON.
|
|
Ben Magro
|
July 8, 2014 at 6:12 am
This is one of the node:
{
id: 102,
code: “0”,
name: “Cliff Dive/Mountain Goat”,
description: “<p>Beers, Bands.. </p> “,
status: “secondary/waitlist”,
limit: 300,
group_registrations_allowed: true,
group_registrations_max: 5,
active: true,
member_only: false,
virtual_url: “”,
call_in_number: “”,
phone: “”,
metadata: {
default_payment_status: “”,
venue_id: “”,
additional_attendee_reg_info: “1”,
add_attendee_question_groups: {
1: “1”
},
date_submitted: “N/A”,
event_hashtag: “”,
event_format: “”,
event_livestreamed: “”,
primary_image: “http://sydneycraftbeerweek.com/wp-content/themes/eventure_child/images/”,
: “”
},
Datetimes: [
{
id: 204,
is_primary: true,
event_start: “2014-10-22 19:00:00”,
event_end: “2014-10-22 23:00:00”,
registration_start: “2014-07-31 09:00:00”,
registration_end: “2014-10-25 09:00:00”,
limit: 300,
tickets_left: 300
}
],
Venues: [ ],
Categories: [
{
id: 6,
name: “For Everyone”,
identifier: “for-everyone”,
description: “”,
user: 1
},
{
id: 8,
name: “Free”,
identifier: “free”,
description: “”,
user: 1
},
{
id: 7,
name: “Weekly Special”,
identifier: “weekly-special”,
description: “”,
user: 1
}
],
Promocodes: [ ],
Prices: [
{
id: 203,
name: “General Admission”,
amount: 0,
description: “”,
limit: 300,
remaining: 300,
start_date: null,
end_date: null,
Pricetype: {
id: 1,
name: “Base Price”,
is_member: false,
is_discount: false,
is_tax: false,
is_percent: false,
is_global: true,
order: 0
}
},
{
id: 203.1,
name: “Surcharge for General Admission”,
amount: 15,
description: “”,
limit: 300,
remaining: 300,
start_date: null,
end_date: null,
Pricetype: {
id: 3,
name: “Surcharge Percent”,
is_member: false,
is_discount: false,
is_tax: false,
is_percent: true,
is_global: true,
order: 10
}
},
{
id: 203.2,
name: “Members Admission”,
amount: 0,
description: “”,
limit: 300,
remaining: 300,
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
}
}
]
},
None of those fields you mentioned are populated event though they are populated in the back end.
None of this data is turning up:
Stored Data
|
|
Ben Magro
|
July 8, 2014 at 6:15 am
I’m accessing it on this url /espresso-api/v1/events/[APIKEY].json
|
|
Dean
|
July 8, 2014 at 6:28 am
Thanks for the clarification.
It does indeed look like that information isn’t included. Most doubt an oversight as the Venue Manager is most commonly used (and I would still recommend it as it allows easy reuse of venues).
I’ll get a ticket raised to look into this, but I cannot advise when this will be resolved.
|
|
Dean
|
July 9, 2014 at 1:48 am
Hi Ben,
I got some feedback from the development team.
Basically, everything will need to route through the Venue Manager. The previous venue system that you are using has been deprecated and has been left in only for users who have been using it for a long time.
Going forward EE4 only uses the Venue Manager and that’s how it will remain.
As such I would recommend swapping over to using the Venue Manager, as that will allow the data to be shown in the API.
|
