The largest change in 2.0 is the move from having events live in regular posts to the (somewhat new) WordPress custom post types. This means that events are no longer going to appear in your posts but rather in their own panel called events. Part of the process of upgrading is to move your events (we have a magic button).
STEP -1: OOPS – I didn’t want to update. No problem, you can easily revert. Grab a copy of the version of the events plugin you want here: http://wordpress.org/extend/plugins/the-events-calendar/download/ and add it to your plugins folder. Deactivate the new one and activate the old one your just upload. All better.
Ready to Go?
STEP 1: Before you do anything: BACK UP YOUR SITE. That way if you run into challenges you can revert if you have to. We use backup buddy and are extremely happy we do as we have had to restore numerous times over the years while playing with WordPress & Plugin updates.
STEP 2: Click update in the plugin admin or download and add it manually.
STEP 3: Migrate! In order to migrate your events after you activate the plugin, you will need to visit the setting panel and click the “Migrate Data!” button. We have some screenshots of the process on our FAQ.
STEP 4: Reset your permalinks (go to settings > permalinks > hit save). We’ve noticed that a lot of weird issues people have often get solved by this easy step.
STEP 5: Walk through the setting. The place the most people will run into challenges will be with Themes. We have a new theme integration approach that allow you to pick from any page template (screenshot) the theme offers or from the default event templates we bundle with the plugin. Try different options to see what looks best. If we get lucky, your theme will play nicely and one of these will work out of the box. If not, then you have a few options. There is a before / after html set of text areas to allow you to add any divs etc you might need. Often the issue is simply a little missing css on your main content div and can be added to your theme css file. This may take some noodling. We wish the you the best of luck. Feel free to ask the community for help on this step. People have been great. The plugin devs won’t help on this step unless you have uncovered a legit bug with the plugin as supporting the 100k+ themes in the world is basically impossible and we all want them to stay focused on making awesome features.
STEP 6 (OPTIONAL): Dealing with custom templates. If you have been noodling in code, odds are extremely high you are going to have to make some fixes.
The path from open source 1.6.5 to 2.0 has been a long one with years of evolution. As you can imagine the template tags, queries & css have significantly changed over time. The odds of a highly customized theme upgrading cleanly is unlikely. While it may not be a ton of work, some is inevitable. We are actively working on documentation this week and will have it up soon at http://tri.be/support as it comes out. There are already quite a few items in the FAQ and you are welcome to search the PRO forums to find answers as it fills out.
Please let us know where you get stuck as you go through the migration process. While we won’t help you code your site, we are on the active lookout for bugs. The more clarity we can get, the faster we can patch those suckers and get everyone an update.
Hope you all enjoy the significant effort we have put into the new version once you get through the migration and get up and running.
One quick note: PRO WON’T FIX YOUR SITE. If you are having any issues with the free version, adding PRO won’t make any difference. All PRO offers are some additional features to help you accomplish more awesome things.
I’ve asked the WordPress.org admins a few times. They have yet to bestow the honor.
I’ll ask again!
Bummer, sadly, it would seem that making it sticky is not an option (technically not possible to make something sticky for just a tag). I did ask that they add it as a feature request for the next update to the wordpress.org forums.
And yet at the same time they have a strict no-bumping rule. So it’s a complete Catch-22!
Perhaps a once a week “nudge” (rather than a “bump”) would be in order. 🙂 Or various people could just repost the information from time to time. 🙁
Thanks for checking.
LOL – we could just have this conversation about once per week right here.
I guess the “just a tag” thing is the REAL problem. It’s awfully weird that the only way wordpress.org hosted projects are allowed their own subforums is via such a simplistic kludge. Makes it difficult and awkward for ordinary users AND project leaders, I’d imagine.
Hopefully with bbpress 2.0 they will move over and use proper sub forums.
Added a new user primer to the documentation: http://bit.ly/uPiQ7w
Hmm, about time for someone to comment on this important thread.
It would be great if your site search box were not at the bottom of the template. It took me some time to even realize it was there. Some of your pages are really long. I was manually typing ?s=whatever in the URL bar for a while. For example, if I want to find the article Show Your Events in the Main Post Loop I have to search for it. I can’t find it any other way. Just a suggestion.
I added it to the sidebar in the support pages. We’ll add it to the main nav in our next update.
Thanks Shane! Hopefully WP 3.3 will not require any big adjustments to the plugin.
Is there a changelog somewhere on your site? I was looking to see if the problem in v2.0 with using the default permalinks structure has been resolved.
We tested on 3.3 and hopefully caught everything with 2.0.2.
We have not fixed that yet (sorry buddy). Started to tackle it for 2.0.2, but will require a lot more work. It is a high priority issue in 2.1 and we are working on it now.
@ lzevon Thanks for that tip. I think I just managed to remove the error and some final spam leftovers
Events Calendar 2.0 update destroyed my calendar. This is ridiculous. I will not use or recommend any Modern Tribe software again, ever. Do you really think average users have all day to sort through your code and figure out code problems? This is WordPress, not a Hackers organization.
Hey biodrama. This is Rob from Tribe here, and I just wanted to reach out to personally apologize to you for whatever inconvenience you’re facing. I know how crappy it feels to install a plugin just to find it doesn’t work. If you’d be willing to elaborate a bit more on the issues you’re having, I would be happy to take a look or to get a dev on our end to offer up their thoughts. While we do expect that our users will have a basic knowledge of WordPress, nothing in this plugin should be complex enough that you have to hack together code just to get it functional.
Feel free to shoot me an email, rob at tri.be, and I can try to get this sorted out for you. We aren’t able to address every support issue that arises here on the WP.org threads, but yours sounds like a critical item that is definitely not how the calendar is meant to behave. I’d like to see what we can do to make things right…if you’re willing to give us a shot. My apologies once more for your problems.
- The topic ‘[Plugin: The Events Calendar] WALKTHROUGH: The 6 Steps to upgrading from 1.6.5 to 2.0’ is closed to new replies.