[Barry]

Thanks Tom – let me see if I can replicate it now.

[Barry]

Hi Reed – this isn’t exactly what you are looking for but it sounds like it is pretty close: “customize output of recurring events: list title/desc once, all dates under that.”

The only difference is that you only want the next date, not all of the subsequent dates, but you might be able to take the snippets in that thread and reshape them a little to fit your precise requirements.

[Barry]

Hi Tom, Barry from the Community Team here. I wonder if I could get a little more information from you to help me replicate this:

• Are you assigning a pre-existing venue or creating a new venue? What is the full venue address?
• Does this only happen when you take an existing event and try to push the details to Eventbrite, or does it also happen either consistently or sporadically when you create new events and register them with Eventbrite at that point?

Thanks!

[Barry]

Hi Mike, Leah asked me to fill you in on the situation with the mini calendar here.

Essentially it’s expected that tribe_calendar_mini_grid() will be called from within a widget, rather than directly (which is noted in our docs for that template tag). Some associated Javascript does also have to be enqueued for it to work successfully.

The best and safest way to get this working is indeed to purchase Events Calendar PRO and use the provided calendar widget – so long as you have a dynamic sidebar you can drop it into (or else if you can create a new sidebar area) you will be good to go.

One last thing I would highlight is that the alternative method of inserting a widget using WordPress’s the_widget() function currently does not work with this widget, I believe a fix is in the works for this.

Does that answer your question? If you need me to clarify anything please just ask 🙂

[Barry]

Great – and sorry once again for the poor experience when updating, it is something we are aware of and hopefully it can be eliminated from future updates.

So for CSS: what you can do is copy events.css from plugins/the-events-calendar/resources and place it in your theme’s events folder, then you can customize away.

The important thing to remember is that if events.css is present in your theme’s events folder then the original version (contained in the plugin directory) will no longer be used – so the key takeaway is that you can’t create mytheme/events/events.css and only put in one or two rules to override the original stylesheet, since that will never be loaded.

In other words, make sure it contains all of the same rules as the original, at least as a starting point. I hope that makes sense but just let me know if you need any further help here.

[Barry]

Hi Terri – I’m sorry that you’ve experienced difficulties here. Unfortunately this has affected a number of our users and hopefully this can be resolved in time for the next release.

What seems to have worked for a number of people is uploading the current versions of each plugin via FTP, overwriting the existing copies. Are you able to give this a try?

[Barry]

Is this website hosted within the same environment/by the same host as the others?

I appreciate when you created this post you marked down that you have already tried deactivating all other plugins to check for a plugin conflict – but have you run through the same process with your theme?

[Barry]

Hi Andrew – since The Events Calendar uses a custom taxonomy you will need to do things differently. If you search for conditional categories you should find another recent forum post on the same topic – hope that helps 🙂

[Barry]

… Have you also double checked that the Eventbrite API key has been entered correctly and for the user who was performing this task?

[Barry]

Hi Craig – sorry to hear you are experiencing problems.

An error occurred while updating Eventbrite. Please review your information and try again. Error:

In the above error message, was there any further text following “Error:” (there may not have been)?

[Barry]

So I’ve reported this as a bug (the reference on our end is #18250) and hopefully this can be addressed in one of the forthcoming releases.

A possible workaround is to add the following function to your theme’s functions.php file: http://pastebin.com/LaZCsjAG

Then find any calls to tribe_get_event_link() within your templates – such as within events/list.php – and change them to tribe_get_unslashed_event_link() … that should form a working solution until we can fix this is the core plugin code.

[Barry]

Hi Wort, thanks for updating this thread and providing a live example of the problem: I can see it and just want to check a few things out here. Will update you soonest.

[Barry]

… Just to clarify, you would need to repeat the same procedure with the list.php template.

[Barry]

Hi Kathryn. I totally appreciate your viewpoint on editing files, however so long as you follow the guidelines laid down in our Themer’s Guide (link on the right, under Useful Resources) you should be ok – as your customizations will be stored separately from the core plugin and unaffected by The Events Calendar updates.

If you want to remove those buttons, you can do! Once again please refer to the Themer’s Guide for the background to this – but what you will be looking to remove from the relevant custom templates are template tags such as:

tribe_get_listview_link();

And also:

tribe_get_gridview_link();

For example, you can find this block of code in gridview.php – http://pastebin.com/s2QcBrn2 – if you simply remove it (from your custom template that is) then the buttons will no longer be present. Does that help?

[Barry]

Yeah so I actually removed that extra tribe_get_ticket_form() because it’s superfluous, I’d regard it as a bug (and I’ve logged it as such – so thanks for bringing it to our attention).

The reason your code didn’t work initially was because as soon as tribe_get_ticket_form() was evaluated it was also printing out the Eventbrite form, so the second call didn’t actually do anything.

So that’s all a bit confusing and again I have logged this as a bug, hopefully it can be revised in a future version and made a little clearer. For the time being it sounds like you’re on track with this one though 🙂

[Author]

Posts