Hey gfields108,
Migration to 2.0 can definitely be a little brutal! It was such a huge change. Glad you made it through to the other end. =)
We are actively working on documentation and hope to have quite a bit of it on our site in the next few weeks. I never imagined writing documentation would be harder than writing the plugin itself. Learning a lot about offering a complete product right now. It is a fun adventure.
Event categories are a completely independent taxonomy from post categories. The migration tool looks at the categories your “events” from 1.6.5 had and tries to faithfully cary them over. It created new categories with the same name in the new events custom post type. I’d back up first just on the tiny odds that I am wrong (it happens). You can safely delete the news category with no repercussions.
Thanks for the nice words.
If you would please consider having an option to make the events posts again.
Our events that we want to scroll across our home page require them to be in the “Featured” category of posts. Under the upgrade we are no longer able to make featured events scroll across the home page since they are now event categories not posts.
This was one of the most important features for us.
Your consideration would be very appreciated.
Thank you for your hard work.
Hi Spencario,
I hear your request. That is not the tiny thing it sounds. Those are deeply different architectural approaches.
That said, you should be able to update your featured events slider to pull from the events category post using the tribe_get_events template tag without too much trouble (if someone on your crew has a touch of wp theme knowledge). We will have further documentation on the use of all our updated tags next week with the release of 2.0.1.
-S
“Event categories are a completely independent taxonomy from post categories.”
This is crazy to do this. They should be just like regular categories. Now, you can’t make use of your special “event categories” with membership plugins like Wishlist Member or any other plugins that want to access or plug into the regular wordpress categories to do something.
Essentially now you’ve got a closed system and to extend the functionality we have to buy additional add-ons and plugins from you.
This severely cripples the full extensibility of this plugin by not allowing outside plugins and your plugin not playing nice with others.
I had high hopes for this plugin and it looked wonderful but after playing around with it, I can see its severe limitations.
bwp
(@bwordpress)
rvlawrence’s post comes off a bit harsh, but that’s part of the reason I’m sticking with The Events Calendar 1.6 for now. Unfortunately I know of no other decent calendaring plugin that DOES treat events as posts! (One says it’s in the works.)
Maybe there’s a better way, with an non-plugin calendar? I just haven’t found anything good, and I don’t want to just put everything on Google Calendar…
rvlawrence – the issue you state about other plugins integrating has more to do with WordPress being in a period of flux between having everything be either posts or in its own table and authors fully adopting custom post types. The core WordPress team is placing a heavy emphasis on CPTs and most major plugin authors are moving over. For example Shopp is moving from their own tables to CPTs in 1.2 (some time around december). As more and more plugins make the move, the integration you want to see will return in a much more powerful and controlled manner.
If you want wish list member and other plugins to integrate, push them to support custom post type integration.
What about your “event categories”? Aren’t those in their own special table? If you were using the traditional wordpress categories, then plugins could interact with them. When you make them separate, then these plugins can’t, unless they were written especially for your plugin. This is a separate issue from custom post types.
Hi Lawrence.
Events does not create a single table.
We simply use WordPress’ build in db architecture. Our events cats live in Terms table like the rest. They are an independent taxonomy, but not in an independent table. I was referencing to the way WordPress now works with taxonomies (term_taxonomy table). My apologies for the confusion.
Hey guys, I found a fix for this. Put it in your functions.php to get your old categories to show up and replace demos with with the words events or whatever. I got it from this link http://www.deluxeblogtips.com/2010/07/custom-post-type-with-categories-post.html
Worked great for Me!
add_action(‘init’, ‘demo_register_post_type’);
function demo_register_post_type() {
register_post_type(‘tribe_events’, array(
‘labels’ => array(
‘name’ => ‘Demos’,
‘singular_name’ => ‘Demo’,
‘add_new’ => ‘Add new demo’,
‘edit_item’ => ‘Edit demo’,
‘new_item’ => ‘New demo’,
‘view_item’ => ‘View demo’,
‘search_items’ => ‘Search demos’,
‘not_found’ => ‘No demos found’,
‘not_found_in_trash’ => ‘No demos found in Trash’
),
‘public’ => true,
‘supports’ => array(
‘title’,
‘excerpt’
),
‘taxonomies’ => array(‘category’, ‘post_tag’) // this is IMPORTANT
));
}
Just need to get the permalinks to stay with domain.com/events/ instead of domain.com/tribe-events/ only issue giving all my event links 404s any help would be appreciated
handsomeman, thats awesome. We just had someone submit a tutorial today on how to do this in a different approach. We are going to work with him to clean it up and put it on our blog soon.
Hey Shane, awesome, that is perfect!! Yea I was thinking you could slide the following in to the above code.
‘rewrite’ => array(‘slug’ => ‘event’, ‘with_front’ => false),
hmm.?! we will see.
success! Flawless.. just change out the demo and replace event with the slug your using
add_action(‘init’, ‘demo_register_post_type’);
function demo_register_post_type() {
register_post_type(‘tribe_events’, array( ‘rewrite’ => array(‘slug’ => ‘event’, ‘with_front’ => false),
‘labels’ => array(
‘name’ => ‘Demos’,
‘singular_name’ => ‘Demo’,
‘add_new’ => ‘Add new demo’,
‘edit_item’ => ‘Edit demo’,
‘new_item’ => ‘New demo’,
‘view_item’ => ‘View demo’,
‘search_items’ => ‘Search demos’,
‘not_found’ => ‘No demos found’,
‘not_found_in_trash’ => ‘No demos found in Trash’
),
‘public’ => true,
‘supports’ => array(
‘title’,
‘excerpt’
),
‘taxonomies’ => array(‘category’, ‘post_tag’) // this is IMPORTANT
));
}
bwp
(@bwordpress)
Thanks, handsome! Could you explain a bit more what this is doing? Do I gather that this exposes the standard WP category selection box while creating or editing Tribe Events custom posts types?
And that those custom post type events will then be treatable and listable as normal posts when displaying the contents of a category (e.g., from a menu link)?
Yup. so you will see and use the custom post type categories and the normal ‘post’ type categories on your sidebar. After adding this code my homepage worked correctly like before. It was such a pain to to figure out how to implement my homepage to pull in the new custom post type categories. Here is all the code I have added to my functions.php to get everything working properly with the original categories and also keeping the new ones too from the events plugin.
[Code moderated as per the Forum Rules. Please use the pastebin]
So you can work with both list of categories. The word ‘event’ is used to maintain the domain.com/event because if you don’t have the slug your using… it will revert it to domain.com/tribe_events giving you 404s on all your homepage links or where ever. I just switched out the words demo starting at the word ‘name’ and worked down to ‘not found in trash’ and replaced it with the appropriate “event” or “events” so it made sense in your dashboard menu/sidebar.
I added it directly below the following line, which is first in your functions.php
<?php wp_enqueue_script(‘jquery’);
So essentially you will see original categories and custom post type categories when creating a new event. (this might be restated, sorry ha)
