After almost 2 months of hard work, WPML 2.1.0 is ready. This is the first commercial release, so it’s only available from WPML.org.
Almost everything new in WPML 2.1.0 is under the hood. In this release, we concentrated on improving security, stability and performance.
What’s new in WPML 2.1.0
- Split into 5 plugins
- We recognized that WPML is becoming too big for its own good. Hardly anyone uses all of WPML’s features, but everyone had to pay in memory consumption complexity. WPML now consists of 5 plugins: core and 4 add-ons. You can use any of the add-ons to achieve the right blend of features that you need.
- Memory consumption went down by up to 50%
- If you’re running a simple multilingual blog on a shared server, you may be very interested in memory consumption. WPML core takes about half the memory of the big WPML before.
- SQL queries reduced by up to 90%
- The new WPML only hits the database once and then it caches data. It also pre-fetches language data. As a result, it hits the DB about 10% of what the previous versions did. Again, if you’re running on a shared host, you’ll immediately feel the difference.
- Hundreds of bugs fixed
- Some were pretty serious things and some cosmetic. The end-result is that you can now WPML with WP_DEBUG and you see no errors, warnings or notices. But more importantly, the new WPML keeps your database intact. Some of the bugs that we fixed lead to errors that creep into the DB. Sometimes, a category gets the wrong language, sometimes a post and sometimes a comment. Over time, this can accumulate to a serious mess. It’s all fixed now.
- Security holes closed
- We audited WPML for security and found several holes that needed closing. We’re not going to detail what they are (for the benefit of folks who are not updating), but it’s important to realize that security auditing and fixes are a natural part of every product and we’re taking it very seriously.
To get the new version, you’ll need to buy WPML. With any purchase, you also get a year of premium support, which you can later renew before the year elapses for 50%. Anyone who previously purchased our support subscriptions doesn’t need to pay again within the first year of support.
Now that we’ve stabilized and optimized the code, we’re looking forward to the next features to add to WPML.
As I wrote before, we’re very interested in making WPML 100% compatible with other popular and important plugins. This includes caching plugins, SEO, contact forms and e-commerce. We’re already talking with other authors working out how to do it best.
For WPML itself, we’re thinking about several additions.
Language-role management for users
Until now, there’s no way to restrict users from being able to edit in certain languages. Even if you use a dedicated Role Management plugin, that plugin is not going to help, as it has no notion of language.
We can add a way for site Admins to restrict access for specific users to specific languages.
Gallery and Slideshow
Right now, WordPress galleries and slideshows don’t fully run multilingual. They somewhat work, but have links pointing back to the original language. We want to address this.
Another popular request has always been to provide translation for author profiles. Right now, there’s just no way to enter author information per language.
The Links section is not translatable. When you add a link, there’s no way to tell WordPress to link somewhere else in a different language.
If you already purchased the commercial version of WPML, or are planning to purchase, leave a comment, letting us know which features interest you the most. We’re eventually going to add all of them (and it’s not going to take that long), but we want to know what’s best to start with.
You probably know that when you purchase, you also get support and upgrades for a year, so if you buy now, you’ll be getting all these new features, and more, without spending any more money.