[Joey Kudish]

Hi Julien,

As Rob mentioned, I would usually recommend using a third-party plugin such as WordPress SEO by Yoast or the All-in-one SEO plugin.

That being said, you can add the following code to your theme’s functions.php file: https://gist.github.com/1964698 and it will noindex your single event pages.

Hope that helps.

[Joey Kudish]

Hi Michael,

Our plugin is set-up to use it’s own single view file, which you can overwrite with your own copy, using the technique explained in this FAQ article -> https://theeventscalendar.com/?qa_faqs=what-are-template-overrides-and-how-do-i-do-them. Doing so, you’ll have the exact same functionality as rolling your own single-tribe_events.php, it’s just a different filename and inside the ‘events’ folder.

As an aside, the templating/handling of views is something we’re going to carefully review in a future version, but it’s not the #1 priority either.

Hope that helps

[Joey Kudish]

Hey Sam,

Unfortunately we needed more time to zero down on this problem and fix it and it didn’t make into 2.0.4. It’s on the roadmap for 2.1 though.

Thanks for the patience!

[Joey Kudish]

Hi Hamish (and others),

We’ve patched this in our latest release (2.0.4) so this shouldn’t be a problem going forward as long as you’ve upgraded. Of course it might take a few days for Google to re-index your site after you upgrade though.

Cheers

[Joey Kudish]

Hi everyone,

Stepping in here to help out.

First of all, we released 2.0.4 this morning which has some bug fixes and few minor new features. I recommend you upgrade as one of the new options is to set how many events show up on any event based loop, without interfering with, and independently of your setting on the Reading page (aka how many blog posts show up).

That being said, I’ve tested out a few things and it does indeed seem that we don’t have pagination set-up for single-day views. Unfortunately this will take a bit of work on our side and not something I can just tell you how to implement over this thread. I’ve logged this as an issue for our team, and we’ll take care of it in a future release.

In the mean time, I wrote a quick filter that you can add to your theme’s functions.php file or as a standalone mini-plugin that will filter the number of events to display on the single day view to display all the events rather than the amount set by your setting, here’s the code: https://gist.github.com/1897199

Hope that helps,
Joey

[Joey Kudish]

Leonard, would be great if you shared your solution so that other users could benefit as well!

Let us know!

[Joey Kudish]

Hey Tony,

I am going to reverse everything I just said, and I apologize for the confusion; I myself wasn’t 100% sure on this one, but have now doen the proper research and can confirm my answer

We aren’t actually using those custom capabilities that I first mentioned, they are present in the codebase but will be removed in a future version as they are not used with the Events custom post type.

The events custom post type uses the exact same permissions as a regular post would within WordPress, so you should be looking at the list that Rob sent earlier: http://codex.wordpress.org/Roles_and_Capabilities. So for example you should look at edit_posts, publish_posts, edit_published_posts, etc…

Sorry about the confusion
Joey

[Joey Kudish]

Hey Tony,

Our main plugin registers a number of new capabilities that are assigned to the administrator role. Here is the extract from our plugin’s code that does this: https://gist.github.com/1889879 so you can see here all of the caps that are used. In retrospect, we probably should assign some of those capabilities to other roles to more closely match the role/capability system of WordPress core (how authors can write content but not publish it), and that’s something we’ll look at in a future release. In the mean time, you’ll have to resort to either using the administrator role, or manually assigning the capabilities to other roles, either with code or via a plugin (here’s a good one: http://wordpress.org/extend/plugins/members/ – although it does more than just role management).

Hope that answers your questions.

[Joey Kudish]

Sorry guys, our system wrangled my code, so here it is in a more readable format: https://gist.github.com/1881943

[Joey Kudish]

Hey Guys,

Good news on this front, wp_dropdown_categories actually has a ‘taxonomy’ paramater that you can pass to it, so you could use it to generate the exact same dropdown with the events taxonomy right out of the box without any customization, like so:


TribeEvents::TAXONOMY) ); ?>


Note: there’s a full list of paramaters for the function here: http://codex.wordpress.org/Function_Reference/wp_dropdown_categories

Let me know if you have any other questions
Joey

[Joey Kudish]

Corey: Fair enough – I didn’t mean to exclude you or anything like that; but it is kind of a shame that Headway doesn’t provide a good upgrade path for their users from 2.x to 3.x. Unfortunately though, we do have to limit our testing and support time for third-party themes to the most recent versions. And to be perfectly honest, Headway does so much of it’s own thing (outside of WordPress core behaviour) that it makes particularly difficult to test against and support in an official capacity. That’s why, for example, we probably won’t fix the issue with the Events Default Template.

Anyway, I just tested my most recent patch and it will fix the issue for 2.x as well as 3.x – so we’re all set here. Expect an imminent release in the next few days.

[Joey Kudish]

Hey guys,

Just went through the two sites; a few notes on each:

— Corey: you are running an old version of Headway (2.x) whereas the newest is 3.x. Unfortunately at this time, we can only support the most up to date version since our fixes depend on the current Headway codebase. Realistically speaking it doesn’t make sense for us to go back and support a now old and deprecated version of the theme. That being said I navigated around your site’s /calendar pages and in no scenario did the menu items change, so I am wondering if there is a specific page where it occurs only? In any case, unfortunately as I said, we can only support the most recent codebase of Headway.

— Phil: I was able to duplicate the issue on your site very easily and was also able to see the issue on my local development site. With that, I was able to further debug the issue and create a proper patch in our 2.0.4 code. We’re going to QA this one internally and we’ll have a final release in the next few days for sure.

Thanks
Joey

[Joey Kudish]

Hey guys,

I’m the dev who worked on this issue with Rob. I’d like to ask you a few questions about plugins you’re running, the theme version, etc… but I think it would be faster and easier if I could have immediate access to your site. Can you please send a set of wp-admin and ftp credentials to pro [at] tri.be and reference this thread in the email?

If you do so soon, hopefully I’ll be able to figure out what’s going on and get it properly patched. Otherwise, we might have to release 2.0.4 without this patch, which would be a shame.

Let us know!
Thanks

[Joey Kudish]

Woops, one of my comments got mangled, I meant:

– I’ve changed featured-event to a div instead of a ul since it wasn’t a list

[Joey Kudish]

Hi Paul,

the die(var_dump($post)); was just there as an example, it basically output all of the contents of the $post variable.

A few notes on your full code:

— no need for that global $sp_ecp in the top, that’s from an old (pre 2.0) version of The Events Calendar
— sp_get_option is also a function from the old (pre 2.0) version of The Evetns Calendar
— you don’t need the query_posts before your first query since you are already at the homepage, the default query will already query for that page
— you can use the_permalink() and the_title() instead of using the $post variable
— no need to check if the has_post_thumbnail function exists unless you plan on running a pre 2.9 version of WordPress
— you should use wp_reset_query() instead of wp_reset_postdata()
— where you have upcoming-events in the sidebar it doesn’t fully make sense you’re checking if there’s a dynamic_sidebar called ‘Homepage Upcoming Events’ but if it does, you’re not doing anything; I’ve removed it from my example for now
— I’ve changed featured-event to a instead of a since it wasn’t a list

Anyways, none of these little things were why the query wasn’t working for you. In fact it was because setting ‘eventDisplay’ => ‘upcoming’ was overwriting the ‘orderby’ => ‘rand’ argument. So instead you need to use the ‘meta_query’ and fetch upcoming events by their ‘_EventStartDate’

here’s the corrected example with all the code changes I specified above: https://gist.github.com/1860947

I tested with a few events in the featured category (some being past and others in the present) and it worked as expected for me. This should definitely get you going.

Cheers
Joey

[Author]

Posts