9

We’re ready with the first release candidate of WPML 1.6.0. This version allows translating other plugins, includes a much improved string translation interface and fixes many bugs.

New features in WPML 1.6.0

WPML can translate other plugins too

WPML can now translate everything in your site, include other plugins. You can do that without asking for any .po file, begging the developers to upload translations or anything else.

Just head over to WPML->Theme and plugins localization.

There, you’ll see a list of all your plugins. Click on the check-boxes next to them and WPML will scan them for texts. In so doing, it also imports all existing translations from any .mo files.

Now, you can continue editing yourself. Click on the Translate button, next to each plugin and you’ll land in WPML’s string translation page. You can translate any text to any language without having to go through those dreaded .mo files, poedit or any other barrier.

Know what you’re translating

Ever wonder what “%1 in %s” means when you’re translating?

WPML now shows you where texts come from, both in the PHP source and in the HTML.

Next to each string you’ll see two icons (when available). When WPML scans the PHP, it keeps track of where the texts for translation come from and will show it to you when you’re translating. Now, you can see exactly where in the source strings appear and (if it manages to find it), WPML can also show where in the HTML.

Bugs fixed

Yeah, bugs are a part of life, but we shouldn’t get used to them. Instead, it’s better to report them in the forum.

And since we’ve got great users who report problems and take their time to explain them to us, we can also fix bugs as they’re discovered. These bugs were fixed in WPML 1.6.0:

  • Language fallback for blog posts had a bunch of bugs (broken search, incorrect category pages and tag). They’re all fixed now.
  • Added placeholder for _cleanup_header_comment (for compatibility with WP 2.7 and below).
  • Fixed some bugs with the tags and the tag cloud.
  • Fixed bug with missing comments.
  • Added correct Estonian flag.

So, keep those reports coming and we’ll do our best to fix problems as fast as we can.

If you missed it before, this is the download link: WPML 1.6.0 RC1

BTW – we think that this version is good enough to power production sites. It’s live now on our own WPML.org and icanlocalize.com.

9 Responses to “WPML 1.6.0 release candidate 1”

  1. Hi Amir,

    great to hear, a new version is comming!

    Just one quick question about this Bug:
    Fixed bug with missing comments.

    Does it concern to the problem, that comments are only available to the selected language or is it something else?

    Thanks,
    Daniel

    • There were some issues with assigning languages to translations, so that translations were not visible on public pages.

      We fixed the problems we were aware of. In case there are comments in the database that don’t have languages attributes associated with them (from older versions of the plugin), it might not retro-fix for them, but it’s possible to fix by running an SQL query.

      Do you have a thread in the forum for this problem?

    • Yes. What you do is put it in wp-contents/plugins and unzip there.

      But hold on. On Monday we’re trying to release the final version, which includes some improvements since this RC.

  2. Hi,
    Feature request: Add support for having a non-english default language, and still have translate strings working. See this topic http://forum.wpml.org/topic.php?id=713#post-3426.
    If I set Swedish as default, my second language is English, the translate string feature assumes my theme and all untranslated strings are in Swedish and needs translation to English. But mostly it is English->Swedish that is needed, most themes have English as their base language. So I only see an option to translate to English. Best would be to see both, regardless of base language.

    Anyway, great tool, trying out the beta now.

    • You’re quite right about that. We need to input the theme and plugins language explicitly, defaulting to English, and not assume it’s the site’s default language.

      We’ll see how to do this correctly.

    • That problem you’ve mentioned in the forum appears very isolated and is probably a result of incompatible PHP or MySQL version. I suggest we keep that discussion on the forum and try to identify the source of the problem.

      Right now, we can’t reproduce it and it seems like it’s happening to just the two of you.