13

WPML 1.7.2 doesn’t contain any new features. Instead, we’ve spent the last few weeks ironing out big and small issues reported in the forum.

If celebrity came of to visit you, what you do? Probably clean up the house and tidy anything you can. This is exactly what we’ve done too.

Next week, WPML is going live in a very high-profile site (more news about that coming). For us, this represents a major milestone and we wanted to prepare as well as possible.

We always keep a close eye on forum issues, but this time it’s special. We decided not to add any new features and instead put all our effort into straightening anything we can see.

Stuff that we fixed in WPML 1.7.2

  • Bullet proof compatibility with WP Super Cache.
  • Fixed bug related to using a revision for a translated page.
  • Fixed language names Magyar, Croatian, Persian, Latvian.
  • Set correct locales for Chinese (traditional and simplified).
  • Fixed potential Cross Site Scripting (XSS) security hole.
  • Sticky links work with single quote links too.
  • Implemented Sticky links for strings.
  • Fixed bug related to special (UTF-8) characters in translation body.
  • Added warning on the reset function, to avoid accidental plugin data reset.
  • Dozens of small PHP / MySQL errors, which could lead to real errors when combined with other plugins and theme functions.

WPML’s professional translation got a major overall in this release. Yup, you guessed right. This major site is using our professional translation and we wanted to make sure it’s all ticking like a clock.

The professional translation now automatically manages links between pages and posts much better (really well). This means that if one page is linking to another, the translations will link to other translations and not to the original.

If you’re translating a large site, you probably know how much hassle this can save.

Planned features for WPML 1.7.3

We’re almost ready with two major features for WPML. They were supposed to go in to WPML 1.7.2, but this house cleaning pushed them to the next release.

  • Language editor – you’ll be able to add and edit languages without hacking the database. So, if you want to have US, British and Australian English, it’s going to be much simpler now.
  • Translation for texts entered in theme admin pages. If your theme lets you enter texts for stuff like your copyright or anything else, WPML will make it possible to translate them.

We love feedback

As always, let us know how it’s working for you.

If anything goes wrong, report it in the forum. And, don’t forget to rate WPML in the download page.

13 Responses to “WPML 1.7.2 – Just Bug Fixing”

  1. Hi, I’ve recently updated the plugin and since then, every time I post I get an error message:
    Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 24 bytes) in /public_html/surrealisrael/wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php on line 3284

    What could be causing this? The post is succesfuly posted, but the workflow is very boring with these messages all the time.

    Appreciate your help and efforts on the development of the plugin, it’s simply GREAT!!

    Best,
    Gabriel

    • The problem you’re seeing is because (as the error says), WordPress has run out of memory.

      You must fix this otherwise things will go seriously wrong. Have a look at WPML’s minimum requirements page for instructions on how to do that.

  2. Thanks a lot Amir, followed you suggestion, is the wp-config.php settings to increase limit of memory.

    changed memory limit by adding the following to the PHP file:

    define(‘WP_MEMORY_LIMIT’, ’96M’);

    Cheers,
    Gabriel

    • I think that we should add a check for this in WPML. Before WPML is fully configured, it takes far less memory, so we can still display a warning and a link for this fix.

  3. Still plenty of love for this plugin. I’m now using it on a new site and running the latest 1.7.2.

    I ran through the beautifully simple set up and to try out stuff. One of the things I did was I selected show post translations ‘Yes’. When I looked at the site I saw the same link appeared twice. I went back to settings to disable the option but this only stopped one of the. I then noticed that I have this option twice under different sections. This isn’t the end of the world, but for a while there I thought that there might be a bug.

    With celebrities coming to visit I thought you might like to know!!

      • I was using the default theme with the wordpress install. And there was no data other than the Hello World entry which I translated to French for testing. Adding WPML was the first thing I did out of the box.

        But now this oddity has gone!! Maybe it only appears on the initial set up and navigating back to the settings page fixes it.

  4. Not sure if it would be caching because the instructions (hide or display) were being taken on board. It was simply that there were two places to choose.
    You’ve been really good in coming back to me on other issues, so let me try this out on a test site. I will let you know what happens…!

    • That’s definitely what it is for me. When you run through the WPML set up you are presented with Finish. I checked Show post translation links ‘YES’ and then ‘Finish.’ After this a new option set appears called “Default – Language selector options” here the post translation links are duplicated.

      I have taken a screen shot for you: asteraweb.co.uk/wpml_bug.jpg

      Because of this two links appear on the page.

      Unchecking either will show only one (as you would expect!). the way that they commit is different:

      I have taken a screen shot for you: asteraweb.co.uk/wpml_bug_2.jpg

      When I navigate away from the page and come back then that new option set disappears. Interestingly, if I leave that second option to show the link selected, when I come back to the page the site no longer shows the link. So I guess you will only notice this if you test in a seperate window/tab before navigating away from the WPML settings page on first set up.

      I hope that this helps.