Posts Tagged ‘language files’

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 »

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.