Amir Helzer

There are no known bugs in the commercial versions. We’ve cleaned over 300 bugs going from WPML 2.0.4 to these versions.

Yup, now just waiting for an OK from NextGen author. As soon as we get it, we’ll write the code.

WPML 2.0.4 (which you can download from wp.org) runs fine on WordPress 3.0.5, but not on WordPress 3.1. If you look at the plugin information box, you’ll see that it says “Compatible up to: 3.0.5”.

The current (paid) versions, available from WPML.org are tested and working fine with newer WordPress versions and come with guaranteed support.

It’s a known problem with WPML 2.0.4 and is fixed in the current versions.

WPML comes with GPL license, like other WordPress plugin.

We give free accounts to other developers and would be very happy to work with you and make sure that Subscribe2 and WPML are fully compatible:
https://wpml.org/purchase/theme-and-plugin-developers/

I can see it too on our site. We’re getting it fixed in WPML 2.1.2, which will be available from WPML.org.

There is a large number of other issues with WordPress 3.1 which have already been fixed in WPML 2.1.0 and 2.1.1.

The missing + icons is more cosmetic, as you can add translations from the ‘edit’ screen. The other problems that were fixed are critical and may not have simple work-arounds (but to upgrade).

All WPML development has moved to WPML.org.

We’re not maintaining two versions, a free and a paid one.

WPML 2.0.4 which you can get from the WP plugins repository is the last version that we released before making the plugin commercial.

It works on WP 3.0.5 but has numerous bugs on WP 3.1. At the time WPML 2.0.4 was written, WP 3.1 didn’t exist, not even as Alpha, so we couldn’t test it.

Great. I’m glad to see you’re doing fine with that. We can probably mark this thread as resolved.

WPML 2.x.x introduces new translation management.

This translation management system stores information of who translated what and when. It’s very important for larger sites who work with teams of translators. Admins can assign jobs to translators and get a complete picture of what’s already translated, what needs update and who’s doing what.

The upgrade logic from pre 2.x.x to 2.x.x adds this information to the database. It’s a complex operation and may fail under different conditions. This is why we recommended doing a DB backup before any such upgrade.

Just downgrading the code might work, but it’s going to leave the translations database in a very messy situation. In the long run, this will lead to lost translations and lost content in WordPress. It’s pretty similar to what will happen if you upgrade WordPress to 3.0.5 and then use that database on WordPress 2.8. It’s going to appear working, but will become messy pretty soon.

Additionally, in WPML 2.1.0 (which is a paid version), we fixed numerous bugs all over the place. Some bugs were in the upgrade logic. These bugs affected special cases that usually don’t exist.

We cannot apply these bug fixes to previous versions as they are spread across many PHP files.

WPML 2.0.4 works pretty well. We provide technical support for newer versions in our support forum.

https://wpml.org/2010/06/fixing-you-do-not-have-sufficient-permissions-to-access-this-page/

Can you give me a quick push and post a list to where that filter is described?

This feature was added to WPML 2.1.0. It’s available from https://wpml.org.

All these notices and warnings are fixed in WPML 2.1.0.

It’s available from https://wpml.org.

We’re working on it as fast as we can, but you should test the beta version (on a test site) and see if it lets you translate NextGen.

Look at WPML language setup under ‘Admin language’.