Amir Helzer

We can work on this together with the author of the P2P plugin.

If you’re listening, contact us and I’ll create an account for you on WPML.org, so that you can access the recent versions.

https://wpml.org/documentation/theme-compatibility/go-global-program/

Yes. Go to WPML->Languages and click on ‘Edit languages’.

Upgrade from WPML 2.0.4.1 to the current versions should be smooth.

However, you should remember that you’re also going to upgrade WordPress itself from 3.0.x to 3.1.x (or higher). WordPress had changed some API and other changes may be required.

This is the reason for WPML 2.0.4.1 not working properly on WP 3.1.x and above.

It appears that you are using WPML 2.0.4 with WordPress 3.1. It’s not compatible.

The author of Subscribe2 is working with us to make his plugin language-aware. I’m not quite sure on the status, but it should be close to ready.

If the widget-logic plugin supports PHP, you can use WPML’s language constants to make widgets appear in the right language.

There’s a queue of requests for non-profit accounts and we’re doing our best to go through them as quickly as possible.

We’re working closely with WooThemes. When there’s a problem, we debug it fully and make sure that it’s fixed either in WPML or in the theme.

Actually, kfawcett, can you point me to the code that does the URL replacements for CDN and the code that creates the minified CSS files?

I’d be happy to debug it, see why it’s not working for us and provide a patch. It would help if I know what I’m looking for.

Thanks Ian,

I’ll check with relative URLs and see if it works. If it does, it’s going to be a big speed improvement for loading the entire page.

We’re done with the changes in NGG and I wrote about it in this blog post.

This is the updated NGG code:
https://wpml.org/wp-content/uploads/2011/03/nextgen-gallery.zip

The changes are pretty simple. We updated the i18n code so that it also accepts a 2nd, optional, $name argument:

function i18n($in, $name = null)


This name tells WPML what the string is for. Then, when users go to translate, they know what they’re translating (like ‘alt’ tag, ‘description’, ‘title’, etc.).

The change doesn’t influence anything else. Other multilingual plugins still use the i18n function just like before. The extra $name argument is only for WPML’s use.

If you want to test it with WPML, you’ll need the current development version. Leave a comment in our post and I’ll email it to you.

Hi Alex,

Good to hear from you. We’ll get it done next week.

The newer versions of WPML run without a single notice.

Have a look here:
https://wpml.org/purchase/why-upgrade/#upgrade-reasons

We applied the security fixes to this update as well.

For obvious reasons, I’m not going to list them out, but they’re applied to 2.0.4.1.

Sure. I understand your point. This is why we came up with two versions, one for personal blogs and the other for full websites.

The ‘blog’ version doesn’t contain the String Translation and Translation Management features. If you’re not using them, you’re not going to miss anything.

Then, if you later decide the upgrade, you can pay the difference ($50) and get access to all the other modules. This upgrade will be available from your WPML account.

This page explains the differences between the two versions:
https://wpml.org/documentation/wpml-core-and-add-on-plugins/

We sent notes about the planned upgrade months ago.

Currently, the version on wp.org says it’s compatible with WordPress 3.0.5 and there’s a big message about the newer version.

I think that it’s better to check that plugins are compatible before upgrading WordPress.

We never upgrade WordPress (even minor version) on the live site. We take a DB snapshot, do the upgrade locally, see that all is fine and then upgrade the live site.