[Barry]

You can rearrange it in almost any fashion you like 🙂

What I’d recommend at this point in time though, if you can wait just a little longer, is delaying further customizations until our very next release arrives.

Right now you could possibly do what you want and need via CSS (incidentally, please do check out our Themer’s Guide – it covers a lot of the background info you’ll need to safely tweak things) however that might be pushing what is easily accomplishable. Moving sections of information around with the current release is also possible but you need to hook into the meta factory: you’re more than welcome to give that a blast but you’ll probably find it’s a whole lot easier in the very next release, as that section of the single event page will be created from a set of customizable templates just like everything else.

I hope that helps 🙂

[Barry]

OK – thanks for confirming.

In that case this is almost certainly a known bug and we’ve actually got a fix in the works which should be delivered as part of our very next maintenance release. If you can hold on a little longer (I can’t give an exact number of days, but it shouldn’t be too long) a fix will be with you shortly 🙂

[Barry]

OK – please do check as if you have only a handful of events this would be surprising behaviour to say the least.

[Barry]

OK, so the existing logic is contained exclusively in our Javascript (in the case of list view, that means tribe-events-ajax-list.js) and you can certainly refer to that to see how things are currently handled – but really to do what you need you’re going to have to create a PHP implementation and I’m afraid we can’t write that for you.

Here’s an example though outlining the basics of setting up a filter for the next link:

add_filter( 'tribe_get_upcoming_link', 'my_custom_next_events_link' );

function my_custom_next_events_link( $base_link ) {
    $page = 1; // Expand this with your own logic, of course
    return add_query_arg( 'tribe_paged', $page, $base_link );
}

In terms of figuring out what the current page is you would need to inspect the URL query for the current request:

$current_page = isset( $_GET['tribe_paged'] ) ? absint( $_GET['tribe_paged'] ) : 1;

There isn’t too much more help we can provide for a customization like this one I’m afraid (and so I’ll go ahead and close this thread), but I hope that helps and at least gives you a basic outline you can build upon 🙂

[Barry]

Excellent – glad that worked 🙂

I’ll go ahead and close this thread – but of course if anything else crops up please just open a new thread and one of the team will be only too happy to help.

[Barry]

Hi 1968rouleur,

I’m a fellow member of the support team and I just wanted to check in here and make sure everything is sorted for you.

It sounds like the outstanding issues are with excess whitespace and the small arrow graphic. Casey’s done an awesome job explaining that one but I see you haven’t had a chance to put those rules into effect just yet – for your convenience, I just wanted to summarize the next steps:

• You’ve already set up a tribe-events-pro.css file and right now that contains one rule relating to the .entry-title element
• You now need to add two more rules – one to deal with the extra whitespace, one to remove that arrow
• Please replace the existing contents of your custom tribe-events-pro.css file with the following code:

.tribe-events-adv-list-widget .entry-title { font-size: 16px }
.sidebar .tribe-events-adv-list-widget li:before { content: "" }
.tribe-events-adv-list-widget ol li { margin-bottom: 0px }

I hope that helps and if you have any further questions about this or find that doesn’t quite work please don’t hesitate to let me know 🙂

[Barry]

Hi – sorry you’re hitting difficulties here.

Went to add a new event today and there is no “Post” or “Add” button, instead it says “Submit for Review”

Also noticed that the Tags and Event Category blocks are missing.

I went to EVENTS and choose a recent event to edit and everything looks and functions perfectly (blocks are there, have option to “Update”)

It’s certainly sounding like the result of a conflict to me (looks like you also have a dropin or “must use” plugin in place – can you confirm that it was also removed at the same time as you deactivated all other plugins and switched to a default theme)?

Also, to confirm, you are signed in as an administrator and not a lower-level user role?

[Barry]

I’m sorry you’re hitting difficulties here: can you confirm if imported events are set to save as drafts (or pending review)?

[Barry]

Hi!

Can you try adding the following snippet to your theme’s functions.php file?

add_filter( 'tribe_events_single_event_the_meta_group_venue', '__return_true' );

Does that help at all?

[Barry]

Hi!

It sounds like our Community Events plugin is a super close fit for your needs, here. You can find out more about Community Events at the following links:

• Community Events product page
• Community Events new user primer

In essence, Community Events allows users to submit events and have them published in the main calendar powered by The Events Calendar (free to download!), which Community Events builds upon. You can require users to be logged in before making submissions and can also stop them from entering the admin environment/dashboard.

Registration for events isn’t covered by Community Events alone, but you could definitely consider something like our Eventbrite Tickets addon or WooCommerce Tickets to cover that aspect.

Does that help?

[Barry]

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

Can you give an indication of how many events you have, what proportion (if any) are recurring events and if this server is currently under load? (If so, how many visitors approximately does it receive when you hit this problem?)

I see you already tried deactivating all other plugins and switching to a default, unmodified theme – was the same problem apparent under those conditions?

Thanks!

[Barry]

Hi!

I’m afraid we don’t have any example code for that – but you could certainly make use of these filters to change things:

• tribe_get_past_link
• tribe_get_upcoming_link

Or, if you prefer a different approach, you could customize and remove the existing nav links via a template override – taking list view as an example, that might mean setting up a custom list/nav.php and adding your own custom code in there to form the links.

Sorry we can’t offer much more on this one, but do check out the Themer’s Guide if you haven’t already done so for an overview of the basics when theming The Events Calendar 🙂

[Barry]

Awesome!

I’ll go ahead and close this thread in that case – but if we can help with anything else please don’t hesitate to create a new thread (or threads) as needed 🙂

[Barry]

Hi Laura,

It’s difficult to say.

Of course the HTML generated by our plugins – and the accompanying CSS – does change from time to time as new versions roll out. We do test as widely as we can against default themes and a range of other popular themes, but we can’t guard against everything and it may simply be that something cropped up which conflicted in someway with a piece of existing CSS already in place via your theme/some other plugin.

Sounds like you figured out a solution you’re happy with, though, which is awesome 🙂

I’ll go ahead and close this thread – but if we can help with anything else please don’t hesitate to post new threads as needed.

Thanks!

[Barry]

OK – thanks for checking/updating it in any case 🙂

I do also see you have two different copies of jQuery being enqueued. One is the standard version that ships with WordPress (great!) one is being pulled in from Google’s CDN service (sometimes great – but not if jQuery is already present!).

You noted having already tried deactivating all other plugins and switching to a default theme: it looks to me like the second copy of jQuery relates to your theme’s slider and I do indeed see a JS error relating to that in the console. With that in mind can you confirm that this problem persisted when only our plugins and a default theme were in use?

[Author]

Posts