Author Archive

Event Espresso 3.1.30 is out! Here’s what’s new.

A new version of Event Espresso is available, packed with fixes and some new features to make your event management a smoother and faster process.

Compatibility with Jetpack

As always with our minor point releases, the focus of Event Espresso 3.1.30 was bugfixes, and the biggest of those was the Jetpack compatibility fixes. If you are a Jetpack user and you’ve had to deactivate Jetpack or downgrade to an older version, you’re in luck. This version of Event Espresso has been tested to work with the latest Jetpack.

Payment gateway updates

Another issue that might have affected some of our Dutch users who are using the iDeal gateway was the conflict with the WooCommerce iDeal gateway. That’s been resolved as well, along with a number of other important updates to the rest of the payment gateways. We also removed some of our old, hard-to-support legacy gateways. The reason these were removed was because those gateways do not provide developer accounts — so we couldn’t test them — and we don’t have a lot of users using those gateways. Instead of trying to invest the time in updating them blindly, without knowing if they actually work or not, we’ve put them up in a public GitHub repository. Anyone interested in taking over updating these gateways, can fork them or submit pull requests.

Language file changes

language-files

Speaking of GitHub, did I mention that our language files are there now? 3.1.30 introduces the new language “side-load” feature, removing the languages from the core plugin (for a smaller package size) and hosting them on GitHub, automatically downloading them to your site if you are using WordPress in another language. Additionally, .30 introduces the ability to upload your modified language files to /wp-content/uploads/espresso/languages.

Cart registration process and other fixes

We made a modification to the Multi Event Registration cart registration process for events that did not have group registrations active. Previously, those events would display a radio button, but that didn’t always send the number of attendees and a radio button, with no other options, isn’t exactly the best use of a radio button semantically. We’ve replaced this with a dropdown, which makes more sense and actually sends a value every time.

3.1.30 also adds a number of security fixes and updates.

New features

We did add some new stuff, too. The EVENT_LIST shortcode now supports multiple categories in one event list. A new System Status page gives you an overview of your server information and what plugins you have active. And we’ve added support for using hooks in WordPress themes for your Event Espresso registration pages to provide more customization options.

Updated Seating Chart

WordPress Event Ticketing Seating Chart

WordPress Event Ticketing Seating Chart

This release also is required for the new version of the Seating Chart alpha. A number of fixes were made to the Seating Chart to fix things like mis-aligned rows, section alignments, and registration prices.

So go update Event Espresso now, or download the latest version in your account area. If you have any questions or problems be sure to let us know in the support forums.

Please note: WordPress 3.5 is required for the latest version of Event Espresso. Please upgrade WordPress before updating to the latest version of Event Espresso.

Tags: , , , , , ,
Posted in Product & News | 9 Comments »

Event Espresso and the GPL

There was quite a stir last week when theme developer, Jake Caputo, posted on his blog that he was disallowed from speaking or volunteering at his local WordCamp because he sells his themes on ThemeForest. If you’re interested in learning about the issue and the discussion, you can take a look at his post and the summary I wrote on my personal blog. This post isn’t going to be about whether or not Jake should be able to present at WordCamps.

We wanted to take a few minutes to talk about the GPL and how it applies to Event Espresso. I tend to be the resident GPL evangelist, so I was asked to be the one to write this post on how the GPL plays into what we do at Event Espresso.

What is the GPL?

GPL stands for Gnu Public License, and it is the software license under which WordPress is distributed. Briefly, it is an agreement between the software developer and the user about how the software can be used and what the expectations of the software may be. There are a few key points that are important to remember when discussing the GPL:

1. The GPL affects distribution.

The GPL license only affects code that you distribute to other parties. Writing code for a web site or client, that never gets released for public consumption beyond that site, does not need to have the GPL license attached to it.

2. The GPL does not include any warranty or guarantee of support.

In fact, the GPL explicitly states that the code might not even work at all!

3. The GPL grants the user (anyone with a copy of the code) the freedom to take, modify and/or redistribute the code.

This means you can take any GPL code and re-release it as you see fit, though you need to put your name on anything you change, so someone can get in touch with you if there are problems.

4. All WordPress plugins and themes must be released under a GPL-compatible license.

This does not mean that WordPress plugins and themes must be released under the GPL exclusively, nor does it mean that everything in a WordPress plugin or theme must be licensed with the GPL. Internal usage within an organization is totally free and not subject to any conditions. There is no such thing as ‘internal distribution’ that would restrict the usage of your code by requiring it to be GPL’d. It does mean that if you are releasing a WordPress plugin or theme for distribution, that it needs to be — in part or in whole — released under a GPL or compatible license.

What’s a “split-license”?

Matt posted a few days ago a comment in response to Japh, the WP Evangelist at ThemeForest, that there is “no such thing as a split-license”. I’ll therefore avoid perpetuating the misnomer, but clarify what the intended meaning is. A package that is distributed in which one license is applied to one part of the package (e.g. the php files) and another license is applied to another part of the package (e.g. images, css, javascript), has been commonly referred to as a “split-license”, which is what is currently in place on ThemeForest and CodeCanyon. It should be stated that there is absolutely nothing wrong with this — it does not violate the GPL in any way. However, as I point out in my blog post, the reason why it’s an issue when a ThemeForest theme developer volunteers for a WordCamp is because it violates the WordCamp guidelines that have been set out by the WordPress Foundation about who can (and can’t) be involved in the organizing of a WordCamp.

What does that mean for Event Espresso?

As a premium plugin developer, it’s a difficult position to be in. The GPL makes it so anyone can get a copy of your plugin and resell it, or just provide a link to a full version of a piece of software that — in our case — has been the product of literally tens of thousands of hours of development. This is why, when you purchase Event Espresso, you are not buying the code.  You are paying for support and updates for the length of the license — the very things that the GPL implicitly does not provide. People are always finding ways to pirate software, and WordPress themes and plugins are no different. However, as I always like to say, good luck getting support. With Event Espresso, if you found a copy online (outside of our site) you would not be able to access the forums except for the free forums or the translator forums (where it would become obvious pretty quickly that you were not using the free version or had a question relating to the translations based on your version and your questions) and only limited access to our support documentation. And you would have no access to updates of any kind.

We are proud of our dedication to open source software. We are actively seeking new partnerships with other WordPress developers, and the API we’re developing will expand Event Espresso events to sites that don’t even run on WordPress. If you have questions about the GPL, take a look at the Frequently Asked Questions on Gnu.org or feel free to contact me on Twitter — I love talking about the GPL helping people understand what it is and how it works!

Tags: , , ,
Posted in Product & News | No Comments »

Event Espresso pre-release channel

We are happy to officially announce a new feature for Event Espresso users that we quietly rolled out on the website a couple weeks ago: the Event Espresso pre-release channel.

What’s the Event Espresso pre-release channel?

pre release channel downloads

Pre-release channel downloads

The pre-release channel is where we post early versions of Event Espresso and any add-ons for user testing. Since we are just barely rolling this new feature out and switching to a new development schedule all at the same time, the first couple versions we released on the pre-release channel were still very early in the testing. However, our new development cycle goes into effect with the release of 3.1.30, which will include a full month of testing by the support team. After we’ve gone through our testing (the alpha stage), we will post the plugin to the pre-release channel. These should be considered solid release candidates that you can use on your live site, but if you are still nervous, you can hold back, stick with the stable version, which will have had a month of beta testing on the pre-release channel. Any bugs that come up during the beta period (via your testing on the pre-release channel) will be addressed before the final release of Event Espresso.

The great part about the pre-release channel is that it installs into a separate directory on your site, so if there are any issues, you can just switch back to the stable version after reporting the issue.

We need your feedback! We are hard at work on the next version of Event Espresso, and we’d like you to take it out for a spin. When you test out a pre-release edition of Event Espresso you can:

  • Help test the upcoming software release against a wide variety of server environments and WordPress installations
  • Get a heads up on new features
  • Ensure that your customizations will work with the very latest software
  • Influence how the final product will look and function
  • Help contribute to a more stable final product
  • Try out new add-ons before they are officially released

Where to download

If you log into your Event Espresso account page and scroll down to the downloads section and you will see a new checkbox (tickbox) for signing up to the Pre-release channel. You can tick that and agree to the waiver and the Pre-release items will appear in a box below your regular downloads.

Pre-Release Toggle

We have set a waiver in place because we may also be using this space for new, experimental products that may not be fully stable, however, again Event Espresso core and the current add-ons will have gone through testing by our support staff before being posted to the pre-release channel. Full details can be found in the Pre-release documentation.

How to report bugs and give feedback

If you notice anything that isn’t working please report it in the Pre-release forum. There will be a new thread for each major point release.

We will be posting the beta version of 3.1.30 to the pre-release channel today with a planned release of Monday. That means you can get started with the next version a few days early and let us know in the forums if there are any problems.

Tags: , , , ,
Posted in Product & News | 2 Comments »

Developers wanted!

Are you a WordPress theme or plugin developer? Have you worked with WordPress or Event Espresso enough that you feel comfortable making customizations for clients? Do you want more clients?

If the answer to those questions was “Yes”, we want to hear from you! We’re looking to partner with experienced WordPress developers who are familiar with Event Espresso that want new clients. We get a lot of requests for customization projects that we just aren’t able to work on due to our regular plugin development workload.

Think you fit the bill? Let us know what you specialize in, what your average rates are, and give us an example site that you’ve worked on (preferably a site that’s running Event Espresso). We’ll be adding developers to a Third Party Developers page where we will refer our customers who are requesting custom development projects that we are unable to take on within their timeline. Fill out our Third Party Developer application to get listed in our directory.

Tags: , , , ,
Posted in Product & News | 2 Comments »

Event Espresso live hangout on Google+

Want to get the scoop on the latest developments in the Event Espresso plugin? Have a question about how to set up Event Espresso on your site? Curious about Event Espresso and want to know more about it before you take the plunge? We’ll be starting a new, monthly hangout on the second Tuesday of every month. Our first episode will be next week!

Here’s your chance to hear directly from us. In this regular one hour chat, we’ll cover all sorts of topics in Event Espresso and WordPress in general. We’ll also be featuring customer sites and case studies, and answer questions submitted via Twitter or our IRC channel. If you aren’t already following us on Twitter, do it now, so you can be sure to catch us live when we go on at 9am MST. Can’t make it? Submit your questions via Twitter with the hashtag #EventEspresso or post your questions in the comments below and we will pick select issues or questions that you have. Already a nerd? You can join us on Tuesday on freenode in #eventespresso-support channel.

Topics and format are subject to change — this is our first attempt at doing something like this, but we’re excited and think it will bring a new way to connect with you, our users, and address some topics that you are specifically interested in. So let us know what you want us to talk about! Need a prompt? How about, what should we call the hangout? We thought of Coffee Talk, but your feedback is welcome!

Use the links below to add this to your calendar:
  

Watch it now

Tags: , , , ,
Posted in Product & News | 2 Comments »

Changes to the Event Espresso language files in 3.1.30

language-files

We’re making some exciting behind-the-scenes changes with how we’ll be handling the language files in the next version of Event Espresso and moving forward. Some things will be drastically different but we’re doing this with our users in mind so there will be very little on your end that you need to worry about except in some very specific cases, which I’ll cover in this post.

How we’re currently handling languages

Currently, Event Espresso bundles all of our language files in the plugin. This leads to a very large plugin. Over 25MB is used just for the language files after they are extracted. Some hosts — particularly shared servers with limited resources — will throw script timeout or max_file_upload errors when uploading or installing Event Espresso. The compressed size of Event Espresso is over 7MB currently, which exceeds the 5MB threshold that’s often the default for shared servers. The new compressed size of Event Espresso with this update is just over 3MB!  No more max_file_upload issues. No more script timeouts. The install and update process will be much smoother and faster.

What’s changing?

Starting with the next release, 3.1.30, we will be discontinuing the inclusion of all language files in the core Event Espresso plugin. This will drastically reduce the size of the overall plugin, making installs and upgrades much faster and eliminate a lot of the current issues that people have with their installs and updates.

Instead of bundling the language files in the core plugin, we’re offloading those files to a GitHub repository. If you are using one of the language files (e.g., you have a locale set in your wp-config.php via the WP_LANG definition), Event Espresso will dynamically fetch just those language files from the GitHub repository and download them into your /event-espresso/languages/ directory.

What changes for English (US) language users?

Nothing. If you aren’t using the language files, you won’t notice any changes with the possible exception of updates being faster than they were previously.

What changes for everyone else (non-English (US) language users)?

It’s possible that the files don’t download correctly from GitHub. This is a worst-case scenario as it should magically work out of the box when you update. If this happens, you can download the relevant language file from our public GitHub repository and upload it to your /languages/ folder.

With every Event Espresso update, if there have been updates to the language files, they will automatically get downloaded to your /languages/ directory and overwrite the existing language files. If the language files have been updated and you would like to incorporate the updated language files before the next release of Event Espresso is available, you can do so by downloading the files from GitHub.

Special cases (if you’ve modified your language files)

If you’ve modified your language files (for example, to modify a string to display a different message), you will now be able to upload your customized language files to /wp-content/uploads/espresso/languages/. This will override the language files in /event-espresso/languages/. You will be responsible for updating the language file if there are changes to the source.

What this means to translators

For translators, nothing has changed, really, except that you can now download the final .mo/.po files from GitHub once they are added to the repository. However, for people who are familiar with Git and Github, please do not submit pull requests to the GitHub repository. They will be ignored. The proper process is still to get validator access on the GlotPress site and make your translations there. However, you will now also be able to upload customized/modified language files to /wp-content/uploads/espresso/languages/ if, for example, you wanted to test a translation you were making changes to.


Our translation project is 100% community-supported, and we are proud of how it’s grown. There are now 26 language files in development and we hope to continue to watch that figure grow and those translations fill out in 2013 and beyond. If you would like to be involved in one of our translations or to translate Event Espresso into a language we don’t have yet, please fill out our translator application and we will get your account set up.

Tags: , , , , ,
Posted in Product & News | 1 Comment »

Upgrading to WordPress 3.5 and Event Espresso 3.1.29

This week, we’re shipping a new version of Event Espresso — 3.1.29 — to add some new features and bugfixes and correspond with the release of WordPress 3.5. 3.5 is a major release for WordPress, with a lot of stuff happening under the hood. We’ve done our best, working with the release candidates, to catch all the bugs and there are a few key points that we wanted to point out as you prepare your sites for these updates.

CREATE A BACKUP!

I can’t stress this enough: when you are making any major changes to your site (which includes updating plugins or WordPress core), if something goes awry or there is an unforeseen bug that slipped through testing and you are without a backup, you are relying on your host to have a backup of your database — if you’re lucky, they’ll have one within the last week; if you’re less lucky, it may be as much as a month or more old. Backup before you upgrade, that way you have something to go back to immediately after something goes wrong (in the unlikely event that it does). Both WordPress and Event Espresso don’t “roll back” easily — there are still changes made in the database when you update that don’t get rolled back by just removing the newer version and putting back the older version, and you could lose data or introduce new issues by trying to “roll back” your WP or Event Espresso installation. If you are even considering “rolling back” as a failsafe, that’s even more incentive to create a backup before you update.

For more information on how to create a backup, refer to our support document on creating a backup for a guide and additional links.

If you’re upgrading to WordPress 3.5, you need to upgrade Event Espresso

Like some issues we saw last year with the release of WordPress 3.4, there are a few issues that show up after upgrading to WordPress 3.5 if you are using Event Espresso 3.1.28.5 or lower. This is part of the reason we’ve been working long hours testing and bugfixing this version of Event Espresso. If you upgrade to WordPress 3.5, you will need to upgrade Event Espresso to 3.1.29 to prevent a number of front- and backend errors from showing up on your site. Additionally, if you are using the WP User Integration add-on, you will need to update to 1.9.6. Again, before upgrading anything backup your database.

Updates to Espresso Calendar

Similar to the requirement to upgrade the WP User Integration add-on to 1.9.6, you’ll need to update your calendar to 2.0.4. This update went out quietly last week, so if you’ve already upgraded your calendar to 2.0.4, you don’t need to do anything. If you haven’t upgraded to 2.0.4 yet, you’ll need to upgrade when you update WordPress otherwise your calendar will not display at all. The update in 2.0.4 updates the fullcalendar.js library to the latest version to be compatible with the newer version of jQuery included in WordPress 3.5.

Datepicker and other admin javascript issues on some servers

WordPress compresses and merges all the admin and front-end javascript into a single minified file. We saw during testing on some servers running WordPress 3.5 (though not all servers) that this caused javascript issues in the markup and prevented the datepicker and other js elements (like the TinyMCE buttons for the visual editor) from working. This is discussed somewhat on a post to the WordPress development blog with the following explanation:

Since compression from php can be problematic on some hosts there are several “switches” (constants) that manage it: define(‘CONCATENATE_SCRIPTS’, false); would turn off both concatenating and compressing of all scripts.

The solution, as alluded to above, is to add the following line to your wp-config.php file:

define('CONCATENATE_SCRIPTS', false);

This will disable the javascript compression which will resolve the issue. We consider this a workaround, however, since javascript compression is beneficial for a number of performance reasons. We will continue to look into a resolution for this issue in the next updates.

We will be adding more documentation in our documentation pages for this new feature, but we are proud to announce the release of a new option to display featured images in your event lists. This works similarly to Featured Images elsewhere in WordPress, though we are not using the same system, so if you are familiar with WordPress theme development, this will still be somewhat different than what you’re used to.

featured-image-1

Featured image in the event list

featured-image-2

Featured image in the event

Add to calendar feature

This has been on the back burner for a long time and we finally were able to add it to this release. 3.1.29 introduces another new feature to add the event to your calendar as an .ical file (compatible with Apple, Google and Outlook calendars). The feature is also activated by default, but you’ll need to re-save your Template Settings to turn it on.

ical

reg-ical-example

Add to calendar link

Event added to Calendar

Automagic Payment Status in Attendee Payments Admin Page

When submitting a payment in the new Attendees Admin, Payment Status is automagically set depending on the relationship between Amount Paid and Amount Owing as such:

  • Amount Paid < Amount Owing = Payment Status PENDING
  • Amount Paid = Amount Owing = Payment Status COMPLETED
  • Amount Paid > Amount Owing = Payment Status OVERPAID

So if you are trying to set the Payment Status to COMPLETED while there is STILL monies owing, then the system will override and set it to PENDING.
In other words, the only way to set Payment Status to COMPLETED is to set the Amount Paid equal to the Amount Owing.

Thousands of attendees or events? We’ve got you covered.

Event Espresso 3.1.29 addresses issues that have been experienced by people with thousands of events or attendees in the Event Overview. We revamped the administration area for managing events and managing attendees so that it loads MUCH faster if you have a lot of attendees or events in your system. The 500 record at a time limit has been removed and replaced with a new setting to only retrieve a specific number of records from the database at a time, and to paginate to the next group of results. This is better for performance than what was happening previously which occasionally caused significant server lag running huge database queries to return your results.

Recent changes to promo codes and Groupon codes

This actually isn’t new to 3.1.29 but we haven’t made a formal announcement; coupon codes now work with Multi Event Registration. To get started, set the new “Allow discounts in the shopping cart” option to Yes. Discount codes will only apply to the events that accept them (previously, coupon codes would apply to all events in the cart, which led us to disable the promo code box by default).

shopping-cart-discount

Another change to the way promo codes are handled is that the standard fixed price promo code will apply to each ticket. For example, a promo code good for $5 off previously would discount $5 off the entire order, now it will discount $5 for each ticket.

Groupons have been modified so that one Groupon code will apply to all the tickets for one event (similar to how promo codes used to work in the shopping cart).

Front-end edit user profile shortcode

The WP User Integration update includes some fixes to the payment confirmation page for WordPress 3.5. It also includes a major new feature we think you’ll find useful. We know how difficult it is to deal with editing user profiles for WP User Integration if you don’t want to give your users access to the WP backend. We minimized this somewhat with the addition of a My Events front-end shortcode recently, bringing the My Events page to the front end of the site. But users would still need to access the backend to update their user profile and add their address information to have those things saved for their next registration. This is why we built a shortcode that creates an edit user profile page and includes the Event Espresso profile fields. The only other way to bring these profile fields to the front end would be to code your own page or modify a plugin like Theme My Profile.

The edit user profile page also uses themeroller styles, so if you have themeroller active in your template settings, the edit profile fields will be styled accordingly. Be sure to check our documentation pages for documentation on how to use this new shortcode.

Update your add-ons

Because of recent changes to how the folder names for some of the add-ons have changed and how that ties into the automatic update system, you may not be receiving update notifications to some of the add-ons. Be sure to check your user account page for the current versions of each add-on and your Plugins page to see which versions you have installed. If you are using an older version and not receiving the update notifications, the easiest way to resolve this is to deactivate and delete the add-on from your Plugins, then download the zip file from your user profile page on eventespresso.com. Once you have the zip file, upload it to your server to install.

With great features comes…template changes

This is another thing that we say with every major release, but it bears saying every time: anyone who has templates in /wp-content/uploads/espresso/templates will need to update their templates or all kinds of things will break if they update the plugin and do not update their templates. Every release we see errors relating to template files that are outdated. Making customizations to the templates is a powerful thing — and like all development projects, when the core software changes, the files that are dependent upon the core software need to be updated to accomodate. With WordPress plugins and themes, this means replacing deprecated functions with new functions. With Event Espresso template files, this means replacing outdated function references with filters and hooks and new features that have been added. In the case of Event Espresso 3.1.29, the major changes to the template files deal with the features I just talked about — featured images and ical links, but there were also fixes added to registration_page.php and confirmation_display.php.

We hope that you’ll take a look at the changelog to see all the things that have been updated and that you enjoy the new features that have been added. In addition to what I’ve described above, we’ve also added the Eway Rapid 3.0 gateway, and many bugfixes. As always, if you have any questions or issues, let us know in our support forums. Downloaded WordPress 3.5 and Event Espresso 3.1.29 already? Let us know your favorite features in the comments!

Tags: , , ,
Posted in Product & News | 16 Comments »

Behind the scenes: the tools we use at Event Espresso

We’ve been at this for over 3 years and in that time, we’ve used a ton of different tools to get the job done. Event Espresso has gone from being a one-man show to a team of 10+ and in that time we’ve learned, largely through trial and error, ways to effectively communicate to each other and our users. Here are a few of the tools we use internally and for EventEspresso.com.

Operating Systems

We’re predominantly Mac users with a few holdouts running Windows 7 and Linux. The apps covered here will be a mix of the popular votes from across all three platforms as well as web-based apps or systems.

IRC

We’ve been using IRC internally for the past year. It has successfully enabled us to communicate better as a team and respond to issues that come up in the forums and as we are developing code much faster. It’s hard to imagine how we managed to do things before we were using IRC. We have one closed channel we use for internal and development communication and another channel we’re planning on opening up to VIP members soon. To keep our private channel closed, we’re using IRC access restrictions. We also have a bot running Phergie that is able to do helpful things like pass messages to other team members who are away from their computers and Google searches, or not so helpful things like tossing each other a cookie, beer, wine or cocktail.

MrEspresso

Phergie is also feeding posts from our P2 site (mentioned below) to keep the team updated on new comments and discussions happening there.

As far as apps go, for Mac, most of us started off with Colloquy before moving on to other things like LimeChat and Adium. For the Windows users among us, we’re predominantly using mIRC, and Xchat is the most commonly used client for Linux, though a Windows version also exists.

Twitter

In the last month we’ve started trying to use Twitter for both internal and external communications. Everyone at Event Espresso was already on Twitter, and Event Espresso has it’s own Twitter account. On our personal accounts, we use the #EventEspresso hashtag for general Event Espresso-related tweets and #eesupport or #eedev for support or development-related tweets. Not only can we keep each other in the loop with what we’re doing, but this gives our users a level of transparency about what we’re up to as well. So, what are we using to manage Twitter? For OSX, there’s the native Twitter app in the App Store or, for everyone, the cross-platform web app TweetDeck.

Browser

To the developers out there, it should come as no surprise that Chrome and Firefox are our browsers-of-choice. The powerful tools of Chrome’s built-in inspector and Firefox’s Firebug extension are invaluable to developing and testing markup. For the Mac users among us there’s Parallels and Oracle’s VirtualBox for Windows virtualization for testing Internet Explorer.

Screenshots & annotations

Formerly, the popular favorite for screenshots with annotations was Skitch. Recent changes to the platform have been universally less well received by our team, and some of us have begun looking elsewhere. The Awesome Screenshot extension for Chrome is…awesome…for browser-based screenshots and Droplr and Screencast.com have also been used by some of us for sharing screenshots. I wrote up an Alfred* extension to replace the timed screenshot feature that Skitch dropped from their app.

* covered later…

Email

Event Espresso uses Google Apps extensively, so many of us just use the Gmail interface for mail. However, the Sparrow for Mac is hands-down the best desktop email client and also has an iOS app replacement for Apple Mail. Speaking personally, Sparrow makes me actually enjoy looking at my email inbox. It’s definitely worth downloading the free (ad supported) version and convincing yourself it’s worth the ten bucks to use it without the ads.

FTP

While the cross-platform workhorse of FileZilla is definitely a favorite, some of the Mac users among us cling to Transmit, by Panic (who also make Coda), which also allows file transfers to Amazon S3 buckets (which we’re using as our CDN).

IDE

A good IDE is important when you’re spending all day staring at it. Sublime Text 2 gets our popular vote with some runners up being Coda and NetBeans. (If you’re looking for a good IDE or have just gotten started with Sublime, this is a great resource that goes through a lot of the amazing built-in features of the program as well as the plugins that can be added.) Windows users (that don’t want to deal with NetBeans) can either grab a copy of Sublime as well, or take a look at the free Notepad++.

Version Control

Version control is essential for any development project, large or small. Even if you aren’t part of a team of developers, version control is invaluable in being able to “roll back” changes to an earlier version when something breaks. Having a solid, reliable version control system (and app) is a required part of ensuring that everyone on the team is looking at the same — and the correct — version of the code. Event Espresso currently uses Subversion for our version control (though we plan to eventually move to Git). Most of us Mac folk started out using Versions but have since migrated to Cornerstone. For Windows, there’s TortoiseSVN and for Linux, we recommend RapidSVN (if you’re not just more comfortable using the commandline). For Git, we recommend Tower (for Mac), the GitHub Git client (for Mac/Windows) or TortoiseGit (for Windows). Alternately, if you’ve already started using Sublime, there are excellent Git and Subversion extensions for Sublime, and NetBeans also has integrated SVN support as well as a plugin for Git support.

Other tools

What other programs and apps are we using? Here are a few of our favorites:

  • P2 – we have an internal P2 blog that we use to announce and discuss issues with the entire team
  • Codebase – where all our SVN repositories are stored and for internal issue tracking
  • Asana – for support issues and other non-coding-related task- and project management
  • Google Drive and Dropbox – cloud storage
  • Codebox, Gist, Piratepad, jsfiddle (and, recently Koding) – storing and sharing code snippets
  • Alfred (Mac) – all-purpose productivity app (some of the automation features of Alfred — such as the previously-mentioned timed screenshot extension) are simply amazing and well worth the cost of the Power Pack add-on)
  • Textexpander (Mac) – keyboard shortcuts for commonly-used text (or code) blocks
  • TotalFinder (Mac) – Finder add-on/replacement that enables tabs in Finder windows

WordPress Plugins

But what about the plugins we use for WordPress, you ask? We use a combination of custom-built plugins, premium plugins and free plugins from WordPress.org. Here are the ones that are most frequently used or most essential to the site:

…as well as custom-built plugins handling the 404 pages, new bbPress topic notifications, testimonials, showcase sites, product features, and various Plugin Update Engine tweaks and add-ons. We’re also using a Google Custom Site Search for our search pages with a custom template and modified searchform so searches go to the Google search.

What are your favorite tools to use in your business or on your website? Let us know in the comments!

Tags: , , , , ,
Posted in Product & News | No Comments »

Template changes in Event Espresso 3.1.28

In an attempt to clean up, clarify, beautify, and increase design consistency across all of the forms throughout the registration process, there have been some significant changes to the HTML and CSS in the various templates.

Anybody upgrading to 3.1.28, especially those with customized templates, should check over ALL of their registration pages to ensure that the new changes don’t have a negative impact on their site’s design.

As well, if anybody has issues on the Payment Options page with images for the payment method buttons (gateways), then they should go to their Payments Settings page in the WordPress Admin and update their settings for the affected gateway. IF the image is still not showing up, then they should use the “Add an Image” button to locate the correct image on their hard drive, then resave their settings.

Any other questions?

Tags: , , , , ,
Posted in Product & News | No Comments »

Event Espresso