[Barry]

Appreciated, Bill – we’ll definitely keep you posted 🙂

[Barry]

Sorry to hear that, Tim.

Generally speaking it should intelligently update things but, perhaps due to formatting and other issues, it was unable to identify the earlier imports.

In that case it may be better to delete the previous set of events and re-import them, yes.

[Barry]

Hi everyone,

I am afraid I am unable to provide any sort of ETA.

We have indeed been working intensively on this as on other parts of the overall ticketing solution: as I alluded to earlier, our ticketing framework started life as something that was deliberately kept small, simple and reliable.

There’s definitely been a lot of demand to take what it offers to the next level, however, and that means some restructuring work has been required — hence we were, regrettably, unable to deliver on this specific feature as quickly as we would have liked.

Please do know that we are indeed working hard on ticketing and some exciting changes are coming up. Right at this time though there is little else I can offer on a support level (and so will close this topic).

Remember to stay tuned to our blog for all the latest news and product announcements 🙂

[Barry]

Happy to help 🙂

[Barry]

Hi Chris,

We actually dropped this behaviour in our 3.11 release, the reason being that for a lot of users it was causing confusion.

As tickets have their product visibility set to hidden by default (ie, so they don’t display in the storefront) adding them to the “Tickets” category meant that where a list of product categories was displayed there would be an entry of “Tickets” but it led customers to what was effectively an empty page.

We did add some hooks to make it easy for customers to re-implement this or similar customizations, though:

• wootickets_after_create_ticket fires when a ticket is first created
• wootickets_after_update_ticket fires if a ticket is subsequently update
• wootickets_after_save_ticket fires on either occasion (update or creation)

So, some code like this would give you a way of reinstating the behaviour:

function categorize_new_tickets( $ticket_id ) {
    wp_set_object_terms( $ticket_id, 'Ticket', 'product_cat', true );
}

add_action( 'wootickets_after_create_ticket', 'categorize_new_tickets' );

You might add this to your theme functions.php file or any other suitable place. Does that help?

[Barry]

Thanks Tim, that looks a little better – the last thing to amend is the time formats. I’m afraid that:

5:30:AM

Is not understood by the parser – in fact it seems to confuse it completely! Can you alter any times like this and drop that final colon, so you end up with:

5:30 AM

Let me know if that helps!

[Barry]

Hi Tim,

Am I correct in thinking that you are using tab separation there (rather than commas)?

Can you try using actual commas, or configure whatever application you are using to generate the CSV to do so and try again? I realize some applications like Excel default to tab-based separators, but it is usually configurable.

Thanks!

[Barry]

Hi Bill,

That’s essentially what we’ll be doing (albeit, rather that switching exclusively to cURL we will use the WordPress HTTP API – which essentially picks the best available option in any given environment).

I’ve linked this topic to the matching bug report (on our internal tracker) and as soon as there’s an update we’ll let you know. Realistically, at this point, that probably isn’t going to mean the fix will be in the very next release, which is already in the final stages of preparation, but the subsequent release.

Thanks again for your patience and support while we address this 🙂

[Barry]

Hi Tim,

Just to confirm – are you using the CSV import tool, or are you importing via WordPress’s XML-based importer, or something else?

If it is the first of those – our own CSV import tool – would it be possible for you to share the actual CSV data, perhaps via Pastebin, Gist or some similar service (rather than dropping it directly into the forum)?

Thanks!

[Barry]

🙂

[Barry]

You can override the template used to create the ticket email (just like you might for any other template) and are free to use both our and WordPress’s template tags within the custom template, so you can access post meta data etc.

theeventscalendar.com/knowledgebase/themers-guide

If you need help specifically with setting up template overrides, though, I’d ask that you create a new forum topic and one of the team will be happy to try and clarify things 🙂

[Barry]

Hi again Bill,

Unfortunately Copyblogger/Synthesis cannot change their system to provide short-term relief on this occasion, but as above we’ll make some changes in the iCal Importer code and will keep you posted when we have done so.

Thanks again!

[Barry]

Hi Bill,

Thanks first of all for all your patience.

Copyblogger were really helpful here and provided us with a testing environment in which we could replicate the problem. It seems that the way things are configured there prohibits some types of communication with other websites and services, and that is why you are unable to import anything.

I should be clear, however, that the way they have configured things is not unreasonable by any means. What I’ve done therefore is this:

• I have requested that they make an exception in your case (and allow the loading of remote content through fopen() wrappers) however it’s not impossible they will decline and they would be in their rights to do so
• We have identified some changes we can make to workaround this problem and we will try to move ahead with that in the next release cycle
• You’ve been extremely patient through all this and we really appreciate that … however, it also means you have paid for a license key for a product you cannot use – with that in mind I have extended the license expiry by an additional year which I hope will allow you to get value from it

Right now there isn’t too much more we can do except wait a) to see if Copyblogger/Synthesis might be able to accommodate a short term change on their end and b) for our own improvement/fixes to roll out in an upcoming release.

We’ll do our very best to keep you updated as things progress on our end and of course please feel free to reach out with any questions in the interim.

[Barry]

My pleasure 🙂

[Barry]

Hi @eastlife,

Thanks for sharing that information and for facilitating some testing: typically we do not work on weekends hence I only saw your replies upon logging in this morning – so apologies for any delay on that front.

If you would be able to set it back to a clean environment running The Events Calendar only so I could take a peak, that would be awesome (also, when you do enable PRO please ensure you leave some views other than photo view activated so I can compare things on that level, too – you may even wish to do so yourself (a critical issue there being the complexity of the geo-query that has to run).

Thanks!

[Author]

Posts