I’m happy today to announce that GigPress 2.0 (formerly known as GigPress 1.5) is available for download. This is a major upgrade that has seen most of the plugin rewritten and a tonne of new features added, and I’m pretty excited to finally have it out the door.
Some of the new features have already been covered in the previous post, but I’ll recap here and touch on some of the other additions as well.
I do strongly encourage you to read the updated documentation — it explains the new shortcode parameters, templating and other features in more detail. Please also note that GigPress 2.0 requires WordPress 2.6.5, and that due to the scale of the rewrite, this release only includes localizations for Bulgarian, Dutch, French, German, Norwegian, Russian, and Swedish. Hopefully more translations will come in soon.
GigPress now supports multiple artists — perfect for record labels or booking agencies. If you’re using GigPress for a single artist or performer, don’t worry — the multi-artist feature won’t get in your way. If you only have a single artist in the database, GigPress won’t needlessly display your artist name.
Venues are now saved in the database — no more re-entering data for shows played at the local clubs or anywhere else. You can easily add new venues on-the-fly when adding a new show as well, and edit venue info at any time.
GigPress is now completely template-driven — customize some or all of GigPress’ output using modular templates for both the main shows display and the sidebar widget. From small language changes to complete rewrites of the HTML, it’s up to you. All of your changes are safe from plugin upgrades, so customize-away.
More calendar-iffic-ness — GigPress now includes both Google Calendar and iCal download links for each show, plus an iCalendar feed for all shows, each artist’s shows, and each tour’s shows. RSS feeds have also been added for each artist’s shows and each tour’s shows.
Import from CSV — import a history of past shows, or move shows between GigPress installations using the built-in CSV export. Artists, venues and tours will be matched-up and/or created during the import process, and duplicate shows will be skipped.
Some other changes of note:
- The age restrictions menu is now customizable — add any type of age restrictions you like to the “Age restrictions” dropdown.
- You can now control the title of automatically-created related posts using simple tokens which represent the artist, date, city and venue of the related show. Plus, you can choose to publish the related post on the day of the show (for those using a future-posts plugin.)
- You can now optionally display full country names instead of country codes.
As always, please review the changelog for the blow-by-blow.
A note about tours in GigPress 2.0
The behaviour of tours has changed somewhat in version 2.0. First, tours no longer have a display order — instead, they are dynamically grouped within the list of shows, with a heading, and then with a CSS class applied which makes them visually distinct from the other shows. Because of this, the “group by tour” option is gone, as tours are always grouped, but within chronological order.
So if you have 3 shows, then a tour of 5 shows, then a break with 2 one-off shows, then the tour resumes with 5 more shows, all of the dates will be in proper order, with two groups of shows for the tour, each with an inline heading, each visually distinct from the non-tour shows.
Those of you who have been using “tours” as “artists” pre-2.0 can automatically migrate all of your tours into artists by visiting a special URL on the new “manage artists” screen, like so:
Also of interest
I’m now handling all support for GigPress through Get Satisfaction. This will hopefully help GigPress users learn from each other by searching the support history there, and subsequently cut down on support emails.
I’ve also setup a Twitter account for GigPress, so you have another avenue by which to get news of updates and pending features — or cool examples of GigPress in the wild — pushed your way.
And lastly, you’re reading this on the newly-designed GigPress website. Not really my usual design aesthetic for sure, but I thought this would be a good place to play with a slicker design style, and use some progressive-enhancement with CSS3 properties and transparency. I hope you like.
I welcome your feedback as always. (As well as your donations!)