Posts Tagged ‘updates’

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 New Versions | 9 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 Development, New Versions, Features | 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 New Versions | 16 Comments »

Do NOT follow this link or you will be banned from the site!
[gravityform id=81 title=false description=false ajax=true]
  • Would you like to join our newsletter?

  • This field is for validation purposes and should be left unchanged.
[gravityform id=81 title=false description=false ajax=true]
  • Would you like to join our newsletter?

  • This field is for validation purposes and should be left unchanged.
[gravityform id=80 title=false description=false ajax=false]
  • This field is for validation purposes and should be left unchanged.
[gravityform id=69 title=false description=false ajax=true]
  • This field is for validation purposes and should be left unchanged.