[Barry]

Hi birchmere,

Not finding this in any of the templates:

The basic idea, within your custom list.php template and anywhere else you want to make this change, would be to remove code that calls the tribe_get_end_date() function.

This thread was created in late June (before 3.0 was released) and was originally in the Events Calendar PRO forum – it didn’t seem initially to relate to Community Events and was only moved across here when snyderwagon clarified the problem (just to explain why you won’t have much success with that original piece of advice).

We are in the process of building up more tutorials and other resources to help guide people through customizations – something more ambitious like not requiring an end date (or leaving it explicitly open ended for some but not all events) is more tricky and right now I’m afraid we can’t help with that. Definitely do add your support to the idea by posting on our UserVoice page:

https://tribe.uservoice.com/forums/195723-feature-ideas

You can either endorse an existing suggestion (if for instance snyderwagon already added a request for this) or create a new one if your use-case is notably different/if snyderwagon didn’t get around to posting his request.

Thanks!

[Barry]

I’d love to help with that, but right now I can’t – we’re simply swamped with support requests right now and so a “nice-to-have” but what I understand to be non-essential customization like this unfortunately would have to wait until we have greater support bandwidth (and, it may be it is beyond the scope of support that we can offer in any case).

In broad outline though you might add a listener for the save_post action, determine if it is an event (and one being submitted via the community form), then loop through any attachments and delete the original sizes (for which your code may need to wait until a later point in the lifetime of the request).

I appreciate that’s a very high overview completely lacking in detail, nor is it the only strategy, but it could form part of a briefing if for instance you outsourced this work to an independent developer.

Cheers,

Barry

[Barry]

We definitely would like to help here but I’m not completely clear as to the problem. Can you break it down and perhaps give me point-by-point steps that will let me see the issue on your site?

Also, is it possible that this stems from other customization work, or a conflict with your theme/another plugin (besides our plugins and WooCommerce)? In other words, can you see if the problem persists even when you are only running Modern Tribe plugins, WooCommerce and a default theme such as Twenty Twelve?

Thanks!

[Barry]

Thanks: I’ll definitely take a look at this but just to make you aware I have no more availability until early next week. It’s possible another team member might be able to step in but if not (and especially since this is a conflict with third party code rather than a bug as such with our own code) it might be Tue/Wed next week before I can take this up again.

Apologies for any inconvenience that causes.

[Barry]

We may not be able to help with these items right now – simply because they are customizations and we don’t guarantee to be able to assist with those (though we’ll definitely try). We’re having to be a little stricter about this than normal due to heavy demand for support right now, but we will certainly see if we can get you started.

Can I ask however that you choose one of these two customizations to pursue in this thread and then create a separate thread for the other issue?

It would also be great to get just a little more detail:

* Where should events be marked as sold out? In the upcoming events list? In the single event page only?
* Should sold out events be hidden from just the calendar (month view) or also from other views (which)?

Please also note that I will not be available tomorrow and so it could be early next week before I can take a good look at what you want here – unless of course another team member is able to step in (and please accept our apologies for any delay that causes).

Thanks!

[Barry]

Yes indeed: creating a new order via WooCommerce (for ticket products) is now reflected in the attendee list.

[Barry]

We certainly don’t want you to look like a tool 🙂 and we are genuinely apologetic if the documentation hasn’t met your expectations. It is rather thin on the ground at this time, mainly because the focus to date has been on development of our new range of products – but improving the documentation is definitely on the radar.

Can we break this down problem-by-problem though? How about we start with embedding tickets on a non-events page first of all then any further issues can be handled by creating new threads (simply to avoid confusion – so please feel free to create threads for instance for the white box where the photo should be and the inability to add more than one ticket).

So, to get started, what are you trying to do? Do you want them to display in the upcoming list view, or do you want to arbitrarily include them in any page you choose? If so how do you envision doing that (how do you want the client to do that)?

[Barry]

Hi Steven,

In the first instance can I check if you have customized and overriden the single-event.php template? If so can you share the code via Pastebin, Gist or a similar service?

Thanks!

[Barry]

Hi Rick,

So as covered in your other thread product variants are not directly supported by WooTickets.

Your items will not display in the WooCommerce storefront as the catalog visibility setting for tickets is, by default, set to hidden – however you can change this by editing the ticket from the product editor.

[Barry]

WooTickets offers a simple ticketing solution: product variants/add-ons are not directly supported at this time, I’m afraid. Please do feel free to add a feature request – ideally detailing your use case – over on UserVoice:

https://tribe.uservoice.com/forums/195723-feature-ideas

That’s a particularly good way of requesting features as other users can then show if they are in support of the idea.

Thanks!

[Barry]

The new status will be reflected. HOWEVER, the total sales and the quantity remaining will not be changed. Meaning that I could have one ticket hanging loose.

That’s correct and that is also expected behaviour, though we can of course understand why not everyone would want that.

It is however part of the design of WooCommerce: for instance, forgetting WooTickets for the moment, if a completed order for 5 x Generic Product is placed, and that order is then cancelled, those 5 items are not restocked.

It’s not really for WooTickets to change the modus operandi of the underlying e-commerce platform, in this case WooCommerce, which is that manual intervention requires manual inventory control (and that is a perfectly sensible approach in many cases) – and so right now our feeling is that this should remain something individual merchants solve with a solution specifically designed to address just that, if indeed they feel it is necessary.

So – don’t get me wrong – we’re genuinely grateful that you’ve taken the time to share your solution, but in general this process is unlikely to be completely incorporated into WooTickets itself.

[Barry]

Thanks for sharing!

As a general note to all, remember also that tickets (the products themselves) can be removed with the delete link.

Additionally, if an order for tickets needs to be cancelled or refunded then this can be accomplished by editing the order via WooCommerce – the new status will then be reflected in the attendee’s list.

[Barry]

That’s a possibility, but right now our plugin simply follows the current practices of WordPress itself. If you feel strongly that it should be something our plugin should solve then definitely feel free to create a feature request for this:

https://tribe.uservoice.com/forums/195723-feature-ideas

Otherwise you would need to introduce a customization or workaround specific to your needs, whether that is an automated approach where the original size is deleted after upload (when and only when it comes through the community submission form), or else substituting a different upload mechanism that can crunch down and resize large images before they even leave the browser.

[Barry]

@ddfaktde: this is still on our agenda, but because the assigned developer has less availability than normal this week there will be a slight delay before we can get back to you with a more substantive update.

We do appreciate your continued patience, thank you!

[Barry]

Thanks, well we’ll look at editing/improving both of those. I’m not actually sure how long the 2.0 documentation will remain online – it’s possible it may be retired at some point in the not to distant future – but I’ll certainly pass your feedback along.

Thanks!

[Author]

Posts