[Barry]

OK – your site’s CSS is notably different to that of our demo site so we’ll need a different approach here (to save time in the future it is generally best just to link directly to a live example on your own site, as every site is different) 🙂

Something like the following CSS (again, it should be possible to add this to a custom tribe-events.css stylesheet) should work:

.tribe-events-tickets td div.quantity.buttons_added {
    height: 40px;
    position: relative;
}

.tribe-events-tickets td input.input-text.qty {
    height: 36px;
    width: 64px;
}
.tribe-events-tickets td input.minus {
    float: right;
    height: 18px;
    position: relative;
    right: 15px;
}

.tribe-events-tickets td input.plus {
    float: right;
    clear: right;
    height: 18px;
    position: relative;
    right: 15px;
}

[Barry]

Yess, that’s definitely possible. Please read through the Themer’s Guide first of all for some backgronud on safely overriding templates, but in essence you could find this template:

wp-content/plugins/the-events-calendar/view/list/single-event.php

Then make a copy which should live within your theme:

wp-content/themes/YOUR_THEMES/tribe-events/list/single.event.php

Within that, locate the following line of code:

<?php the_excerpt() ?>

Simply change this to:

<?php the_content() ?>

Does that help here?

[Barry]

Are you using a format like h:i (in WordPress’s General Settings)? If so, you’re right – the time selector doesn’t seem to switch to 24hr format.

I’ll certainly get this logged as in need of more attention … would it be possible to either switch to H:i (uppercase H) or else bear with this a little longer?

[Barry]

Hi – great questions!

Considering the Time.ly URL with this demo: “https://time.ly/calendar/action~agenda/cat_ids~163/”, we like the view of listed events with the collaps/expande effects. If that possible in Tri.be? Maybe not exact, but something like that. It would be an advantage if you could send us an example of how could show it.

The only limit is your imagination 🙂

We don’t ship a view quite like that out of the box, but The Events Calendar and Events Calendar PRO are highly customizable and you could certainly create something very similar to this.

If we are thinking to have an internationalization wordpress template, is it possible with Tri.be components?

We’ve made a lot of efforts to make our code translatable and you’ll be happy to know we already ship with a ton of language packs 🙂

Checking on Time.ly URL with this demo: “https://time.ly/calendar/action~agenda/cat_ids~163/” again, we have also focused on Tags cloud searcher as a very closed implementation of what we are looking for. PLease let us know if we could have some like that in Tri.be.

We’ve definitely got something comparable you might be interested in, yes – check out Filter Bar.

Finally, would it be possible to test the Event Calendar Pro for a period of time?

I’m afraid not. Our core plugin – The Events Calendar – is free though and you’re more than welcome to grab a copy and take it for a spin. Events Calendar PRO builds on this to add extra functionality, but the general look and feel is very close (and you can get a sense for what extras it provides by reviewing this page and this primer for new users).

I hope that answers your questions but do let me know if we can help with anything else 🙂

[Barry]

Hi!

I’m afraid purchasing a product from WooThemes does not entitle you to a free license for WooCommerce Tickets – we are a separate business and there’s no particular link beyond the fact that we have built an extension for one of their many awesome products 🙂

Does that clarify things?

[Barry]

Hi!

I’m going to move this out of pre-sales and over to the WooCommerce Tickets forum – but the thread URL should stay the same and you should still receive updates (if you subscribed to them when you opened the thread) 🙂

Basically though there are two different processes to run through.

1. WooCommerce itself (plus whichever payment gateways you are using) handles cancellations and refunds, so the order editor should be your first stop
2. From there, if you wish to completely remove the corresponding entries from the attendee list simply select the relevant items and used the Delete bulk action (in the attendee list view)
3. To actually “credit” their accounts I think you’re going to need something beyond just what WooCommerce and WooCommerce Tickets allow – there may be a suitable existing addon but we’d need to leave it to you to research that

Does that help?

[Barry]

Hi!

There are a couple of ways you could do this, but it might be easiest to use the functions provided by this (unofficial) plugin – or you might just check out how it works “under the hood” to build a picture of the relationships between events and tickets. Either way that might help get you on track here.

A brief summary of some of the customizations you can make and the available functions can be found here.

I hope that helps!

[Barry]

Hi! A great spot for event-page-related CSS is a custom tribe-events.css stylesheet, which would live at:

wp-content/themes/YOUR-THEME/tribe-events/tribe-events.css

There are more details in our Themer’s Guide. Does that help here?

[Barry]

Hi!

One possibility is to set up some code in your theme’s functions.php file – or some other suitable place – and create a filter something like this:

add_filter( 'gettext', 'change_nomenclature_globally' );

function change_nomenclature_globally( $text ) {
    $text = str_replace( 'Event Title', 'Name', $text );
    return $text;
}

You could set up as many rules in there as you need (and bear in mind it is case sensitive, if you do follow that approach). Alternatively, you may be able to use individual hooks and template overrides if finer-grained control is necessary (see our Themer’s Guide).

Does that help at all?

[Barry]

Hi – sorry you’re experiencing difficulties.

Can you confirm that you are using the latest versions of all four plugins (The Events Calendar, Events Calendar PRO, WooCommerce Tickets and WooCommerce itself)?

Is it possible that – perhaps inadvertently – the ticketing meta box was deselected? You can check this out by editing an event/creating a new event and searching for the Tickets checkbox in the Screen Options pulldown. Is it present and checked?

Let me know how you get on 🙂

[Barry]

Hi – great question!

One option is to simply move the ticket form higher, would that work for you? If so, please check out this tutorial.

Does that help?

[Barry]

Hi – I’m sorry you’re facing difficulties.

Would it be possible to link me both to an affected event and the corresponding event on Facebook?

[Barry]

Hi!

Yes, possibly you will – but if so it is possible to automate the process as described here.

I can’t give you a definitive yes or no because really this hinges on the particular payment implementation you decide to use (there are numerous ways in which you might accept credit card payments). What I can say is the process is anyway capable of automation – as above – and that the folks best placed to guide you here are either the team behind WooCommerce or possibly the authors of the payment gateway plugin you choose to use (if it’s sourced from someone other than WooThemes, that is).

Ticket products are regular products – there’s no real difference in how sales are processed between them and any other WooCommerce products.

Does that clarify things at all?

[Barry]

Hi!

You would normally do this via a template override (please see our Themer’s Guide if you’re new to this idea). With our current releases the template is actually found within The Events Calendar itself:

plugins/the-events-calendar/views/tickets/email.php

And you would set up a copy in your theme or child theme something like this:

themes/your-theme/tribe-events/tickets/email.php

Does that help here?

[Barry]

That is odd – sorry you’re hitting this issue.

I wonder if another plugin (or your theme) is adding a script that is preventing clicks on those elements from working. Could you try our regular troubleshooting steps and temporarily deactivate all other plugins and switch to a default, unmodified theme (such as Twenty Thirteen) then check and see if the same issue crops up?

Assuming for the moment everything works as expected under those conditions, try reactivating everything one-at-a-time, testing at each stage to see if the problem has returned – this could help us to isolate any conflicts that might be occurring (of course there may not be a conflict, but it’s well worth running through these steps to determine that).

Let me know how you get on 🙂

[Author]

Posts