[Barry]

You can definitely stop the end date from displaying. In the first instance, please check out:

* Our themer’s guide
* This handy tutorial on template overrides

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.

Does that help?

[Barry]

Hi Andrea – have you checked out the following tutorial?

How to Completely Customize Widgets

[Barry]

Hi!

So it looks to me like the events in question have an end date that is still in the future – for instance you have one event that runs from June 19, 2013 – July 10, 2013. Since people could still potentially go and join this (it hasn’t ended yet) it still displays as an upcoming event.

Remember that if it is a single day event that happens to recur every day for a week then you should set it up so that:

* The start and end date are the same
* The recurrence pattern itself should end a week later
* Set it to daily

By contrast, if you set it up in this fashion:

* The start date is today and the end date is one week from now
* And the recurrence pattern is also set to end a week later
* It recurs daily

Then you will have 7 instances of the event, each a week long in duration and by day 7 there will be 7 concurrent instances. I know that can be a little confusing, but with the exception of one or two special cases the solution is to use the approach in my first example (have the event start and end dates set to the same date – and set the recurrence end date to the end of the pattern).

Does that help/clarify things at all?

[Barry]

Hi Dan,

If you manually delete the duplicates then the events tied to them would indeed become orphaned – you’d basically have to edit them and “point” them to the venue that you are going to keep.

That’s definitely going to be a bit of a pain (and thanks for posting on UserVoice, by the way) … what I’d suggest, if you can wait just a little longer, is checking out if Events Calendar PRO 3.0 can fix this up for you. We’ve added a tool to that version which can be run once-only (ie, when you first upgrade) and it will merge duplicate venues and organizers and handle reassignment to the merged version – so that may very well solve this.

There is not a fixed release date that I can provide for 3.0, but I can say that we are now within an ace of releasing it.

[Barry]

Hi!

We have a new version coming along shortly and all ticket products will be virtual by default, which should remove shipping fees.

If you want to get a jump start on this then you could take a look at this approach and either use it as-is or adapt to your needs: a description of what it does is given in that thread and though I can’t offer any guarantees you are welcome to try it out.

Thanks!

[Barry]

Hi ben099,

That of course shouldn’t happen – so it indicates that there might be a conflict.

When you created this thread you indicated that you had tried deactivating all other plugins and reverted to a default theme such as Twenty Eleven or Twenty Twelve to check for conflicts … did that yield and useful information and were you able to isolate any components, such as your theme or another plugin, that were causing this problem?

Thanks!

[Barry]

Hi redsquare,

I do not believe that either WooTickets or WooCommerce expose a way of doing this at user-interface level but, if you familiarize yourself with WooCommerce internals, you could definitely use the same approach as WooTickets to attach items.

Please see the WooCommerce Codex or reach out to the WooThemes guys for support on that end (you can probably find snippets of code floating around the interwebs for this one, too).

Thanks!

[Barry]

Yes, I think that makes sense – you basically want to create a set of WooCommerce products and use and re-use them to sell tickets to events (whereas WooTickets will create a new product every time you create a new ticket) … is that correct?

[Barry]

Hi flaviarusso,

The next version of WooTickets – which should be available shortly – will do this by default.

If you can’t wait until then please take a look at the code posted earlier in this thread – bearing in mind you may have to adapt it slightly to meet your needs.

Thanks!

[Barry]

Likewise!

[Barry]

Hi Barry, looked for the full_width function and it was already there in my functions.php???

It isn’t part of Twenty Twelve, so you must have added it twice somewhere along the line (if indeed it is exactly the same and doesn’t simply share the same name).

Anyway, it still returns the same page with the content at 2/3.

That’s a shame 🙁

All I can really say is that it solves the problem for me – I can’t really offer anything else since if I understand correctly you are developing locally. If you do move things to a web-accessible URL though and still need help just let me know and I can take another look and see if there are any obvious clues as to why it isn’t working.

Thanks!

[Barry]

Great, thanks Stefan.

[Barry]

Excellent, glad to hear it’s working well.

I’ll pass your remarks about adding it to the next version back to the developers (thank you for testing this) and hopefully we’ll be all good in subsequent releases.

However… we are actually so close to releasing 3.0 that it may not be possible to put the code in there as there is currently a code freeze in place – so just be aware of that.

Since I think we’re all good otherwise I will go ahead and close this thread.

[Barry]

So you’ve got a category of events that is called workshops?

When I test out fullwidth template with an events category (using the above snippet) everything seems fine to me. Can you provide a URL where I can see the problem, or are you developing locally only at this point?

[Barry]

So there are different ways you might deal with that.

You could make the table cell hide any overflowing text, or add a horizontal scroll bar for overflowing cells, or one of many other ideas. Really it depends on what your preference is.

This problem isn’t specific to The Events Calendar as such though, it’s just a routine problem of fitting long, unbroken pieces of text into small areas of a webpage.

[Author]

Posts