[Barry]

This thread’s not seen much activity for the last couple of weeks so I’ll go ahead and close it. Of course if you still need help with this or any other issue please don’t hesitate to create a new thread (or threads) and one of the team will be only too happy to help. Thanks!

[Barry]

OK, so if that’s the same issue then some additional CSS rules like these could help:

input.button.submit.events-community-submit {
    background: #eee;
    border: 1px solid #000;
    color: #000 !important;
    font-weight: normal;
    text-shadow: none !important;
}

Please try adding them to a custom tribe-events.css stylesheet (details of setting this up can be found in our Themer’s Guide) – does that help here?

[Barry]

All sorts of customizations are possible and our Themer’s Guide is a great starting point for this sort of thing. Beyond that, I’m not 100% clear as to what you want to change and where.

Can you break your question down and perhaps even give a URL with an example of something you wish to alter? That would be awesome.

Thanks!

[Barry]

Hi – here’s what I see:

So I’d certainly agree there are a few CSS issues here, but it isn’t quite as you described (being outside the button boundaries etc) … I just wanted to check in the first instance if we actually are seeing the same and/or get a little more information if we’re each seeing something different, such as what browser you are using.

We can definitely do a few things to improve its visibility re the above screenshot, though (which is the result of CSS rules from your theme, best I can tell).

Let me know!

[Barry]

Hi – sorry you’re facing difficulties here.

It looks like you might have made a few customizations with regards to month view: can you confirm if restoring default templates and removing any customizations restores normal behaviour?

If not, can you confirm exactly the steps I would need to take to replicate this locally?

Thanks!

[Barry]

Hi: great question!

We did do a large amount of work re 404s but the fact is more needs to be done – and we’re actively investigating the best path forward, particularly with regards to soft 404s.

All I can really suggest is bearing with us as I’m confident we’ll be able to roll out further tweaks and improvements over the next few release cycles.

Thanks!

[Barry]

Hi – great question.

As of 3.5 we’ve taken a new approach with regards to tooltips – largely to provide more flexibility with responsive layouts – and beyond recommending you check out the Themer’s Guide it’s probably well worth reading the fairly extensive documentation contained within the month/single-event.php template itself (and cross reference it with the new month/tooltip.php template).

Does that help?

[Barry]

<p>Definitely possible. If I’m interpreting your screenshot correctly and you want to keep some elements from the existing meta box but not all, it may be best to basically recreate the meta box template (the original view file lives at the-events-calendar/admin-views/events-meta-box.php) and strip out what you don’t need.</p><p>You can then tell The Events Calendar to use your version by passing the full filepath to your custom template via the tribe_events_meta_box_template filter hook.</p><p>There are a few other ways you could tackle it, too, like a little Javascript magic if you’re comfortable with that sort of approach – but that’s arguably less ideal and I don’t think there are sufficient CSS classes/IDs to manage this with CSS alone, either, though it’s possible.</p><p>Does that help?</p>

[Barry]

Hi – it does indeed look like a CSS issue. Try setting up a custom tribe-events.css stylesheet (see our Themer’s Guide for details) and add this code:

.tribe-events-list-event-description {
    margin-top: 0;
}

Does that help with this?

[Barry]

Hi!

Your theme applies this rule which is hiding the date:

.byline, .updated {
    display: none;
}

Try adding a custom tribe-events.css stylesheet (see our Themer’s Guide for an overview of this process) and add the following to “combat” your theme’s rule:

.tribe-events-single .updated {
    display: block 
}

Does that help?

[Barry]

Hi – great questions!

1. allow us to charge a service fee?

You could certainly factor a fee into the ticket price. Beyond that, tickets are simply regular WooCommerce products, so you can potentially treat tickets like any other products and apply WooCommerce functionality to them, too.

2. track affiliate sales? For instance, if multiple people are promoting the same event to keep track of the amount of sales for each person?

Tracking affiliate sales isn’t something WooCommerce Tickets itself is built to do and I don’t think WooCommerce itself will, either (though do check with WooThemes about that!). There are probably some dedicated affiliate plugins you can leverage here though and there may even be dedicated WooCommerce addons to assist with this.

3. check in application for tickets at events?

We do indeed have ticket check-in functionality: check out our new user primer for an overview (including videos) to get a better flavour for what’s possible.

Thanks!

[Barry]

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

So which template are you trying to use and what is it currently set to? Do you find this is only an issue with your current theme (ie, are you able to switch events template without any problem when using a default theme such as Twenty Thirtreen)?

Let us know!

[Barry]

Hi: I’m really sorry, I can only imagine how frustrating that would be. Did any events – theme updates, plugin updates, changes to settings, customizations – take place and coincide with this?

It does look as if the template may have been customized a little, for instance I see this in the source just before everything “cuts out”:

<!-- Commented out by AJ on 20140314.0736 <div><span> -->

Is it possible you introduced a change that caused this issue and have you tried restoring the default templates (/renaming your custom templates so they won’t be loaded) if so?

[Barry]

Hi: I’m sorry you’re experiencing difficulties.

It looks like this could be a case where our new responsive design code is misfiring. Can you try the technique described here for disabling responsiveness and see if that helps?

If you wouldn’t mind and can share a copy of your theme (via Dropbox or some similar service – you could post a link here as a private reply) that could be useful to us in avoiding this in the future.

Thanks – and let me know if that helps 🙂

[Barry]

How odd, I’m not sure I’ve seen quite that problem being reported previously. Can you update the entire series (“edit all”) and correct this times that way?

[Author]

Posts