[Q]

Back again – I have a few more ideas:

Each EB event can have a featured image – why not pass the featured images of the WP post, if this is allowed?

I also wrote to EB today about opening up their API to allow for CC sales – it’s really annoying to have to add and then manually remove PayPal settings.

In fact, as an overall UX it’s a little odd to be able to add only the first ticket via WP – and then to shift to EB to complete and fine-tune the event – it is a confusing concept to try and train up a non-technical client on.

I agree that the validation for adding tickets is important, but it’s not consistent – one of the clearest example is on the start date of tickets, which from within the EB site can be set in the past – but which must be a future time from with WP ( the main disadvantage of this is that the ticket cannot then be tested until the date is set to the past on the EB site ) – if EB allows past dates for tickets, why don’t you?

Similarly, I would default to an end date for ticket sales to x hours or x days before the event – configured as a main setting in the plugin, with a manual override option per ticket, if required.

I think that the most important element for me – and really the thing that will keep this add-on active on my clients site is improving the integration between the two systems – aiming to move all the optins required to add multiple tickets within WP – reducing the need to move between both sites to complete a simple ticket set-up.

There are many fine-tuning options available on EB tickets ( I’ve not checked the API to see which may be configured remotely ) but where possible, it must make sense to pass automated settings which can be manually over-ridden where possible – such as custom event URL’s and as mentioned event images.

Overall – I’m happy, but the client is the ultimate judge and their level of technical knowledge is the real decider – this plugin is bordering on geeky and I love that, but geeks needs clients to pay the bills!

Thanks…

[Q]

thanks – good work..

[Q]

Thanks Barry – that’s basically what I had except you removed the first check if tribe_get_ticket_form() returned anything – either way, thanks

[Q]

bit crap not to be able to post code snippets to a forum about code – http://pastebin.com/7YrNZVCk

[Q]

posting removed my code – I’ll try with tags..

[Q]

I’m not sure if that little gem about the eventbrite API key being stored in the user profile is listed in the documentation anywhere – might be a good idea to make it clearer if not! – thanks..

[Q]

well, it might have one or two small errors.. I’m still testing it – I also use a simple get event cat function ( http://pastebin.com/bzaSe984 ) which I was using to get the category – perhaps better to be using your own class – which I tried in the SEO title function…

[Q]

here’s my take on TEC & WPSEO titles – I’ve added a custom taxonomy – tags – to tribe_events, so needed to separate that out to – http://pastebin.com/VVXMVn7M

[Q]

Hi Jonah – thanks for your positive reply – be great to know if and when that’s included.

[Q]

how about hooking into the EB API to allow users to view current and previous ticket purchases from within our own sites?
view post here:

eventbrite sign-up / purchases page

[Author]

Posts