21

This version doesn’t include any functional changes or new features. Instead, it fixes bugs that were reported in the last two weeks.

Da Bugs

  • Multiple posts returned in single.php – this happened when URLs had Asian or Russian characters and on specific themes.
  • PHP notices when sending custom posts to translation.
  • Admin Texts selection didn’t get strings to the String Translation screen.
  • Problems in the XML Language Configuration file could have caused PHP fatal errors.
  • Language switcher didn’t work on custom post archives.
  • PHP warnings when editing languages (to create custom languages).
  • Language of posts lost when future posting is enabled.
  • PHP warnings in multisite mode due to using a deprecated WordPress function.
  • Cannot access pages using HTTPS.

Thanks again for everyone reporting these problems in the forum and for taking the time to test the beta versions (we sent those to people reporting bugs).

This upgrade is recommended for everyone using WPML. To get it, log in to your Admin Dashboard, click on Plugins and upgrade normally. If you’re migrating to the commercial versions for the first time, have a look at the upgrade instructions.

21 Responses to “WPML 2.2.1 – Bugfix Release”

  1. Hello there!

    Thanks for the bug fix release! However, I’ve noticed that after upgrading, WPML still thinks it hasn’t upgraded, showing the following message: “You have version 2.2.1 installed. Update to 2.2.1.” 🙂

    Should I update it twice to get rid of the message? (I haven’t so far, for fear of hopelessly confusing things beyond repair)

    • I got this too yesterday after upgrading our own site (wpml.org). Then, the message vanished today. We’re checking what goes on inside there.

        • The upgrade message was visible yesterday at my admin panel, but had disappeared today even though I did not upgrade the plugin(s) as I think it is far to complicated when the bug fixes do not bring anything for me.

          My habit with all other plugins is to upgrade to latest release immediately, and it would be great to have an automated upgrade for WPML paid licenses as all other plugins (unpaid!) in WordPress can easily now be upgraded like modern software should. Hope you find a way to enable automated upgrades soonest!

  2. I´m working on a multilangual site and I have to say it´s problematic that you don´t have any easy way to export and import the translations in the website. I would like to have an option to easy switch eg. between wordpress and wordpress multisite.
    Or reinstall wordpress without needing to mess with phpadmin.

    • The native XML export in WordPress is not very reliable and it gets even less reliable when you have non-English characters in the database. I strongly suggest using DB backup and restore instead of these XML transfers.

      Also, the XML files can be huge, causing PHP to timeout. We’ve seen plenty of that too.

  3. Hi, WP dash board…clicked upgrade automatically for WPML Multilingual CMS – Installed version (2.2.1) and it appears to be upgraded. I then went to WPML Support link when logged into WP and posted below what is shown. When clicking on upgrade automatically for any of then add-ons WP just revert back to PLUGINs screen and only displays add-on clicked on. The upgrade does not work for add-ons. Your help fixing this is appreciated.

    ++++++++++++++++
    Visit our forum

    WPML CMS Nav – Installed version (1.2.0), version 1.2.1 is available | Download | Upgrade automatically
    WPML Multilingual CMS – Installed version (2.2.1) | Download
    WPML Sticky Links – Installed version (1.1.0), version 1.1.1 is available | Download | Upgrade automatically
    WPML String Translation – Installed version (1.2.0), version 1.2.1 is available | Download | Upgrade automatically
    WPML Translation Management – Installed version (1.2.0), version 1.2.1 is available | Download | Upgrade automatically

  4. i got a white screen backend after upgrading to 2.2.1. returned to 2.2.0 and everything works fine.

    • Make sure that all of WPML’s file are uploaded correctly. I suggest that you delete the entire directory and upload again.

  5. @Amir
    If I delete and reinstall won’t I loose all the work I spent a long time working on?
    I paid $79 I hoped for a better answer.

    • You’re not going to lose anything. This procedure is identical to plugin updates and is completely harmless for your data.

      When I say delete, I mean to remove the plugin’s directory, not manually delete any tables from the database.

  6. JS bug bug bug….

    to the admin page, for the widget translation (string translation), when you try to open the translation, it closing directly, so i cant do anything on the admin page, so… i work to the .po file.

    display: none; every time…

  7. Greetings,

    Trying to upgrade.

    1. I am told on the dashboard “Your WPML subscription details are required” I click and subscriptions details are there. (date of expiry and my login and password hidden, which I have tried several times to update)
    2. I try to “Upgrade automatically” get back to plugin page in WP with “Automatic update is unavailable for this plugin.”

    Anything I can do? I have tried this in several browsers and after emptying cache.

    Thank You

    • Make sure that your subscription information is exactly as appears in your WPML.org account. Log in to your account and check what email we have registered for you.

  8. Hello!

    I have a bilingual site but I want my blog to bypass the translation and show all articles regardless of whether they’re in French or English.

    I thought using the option « All posts (display translation if it exists or posts in default language otherwise) » would fix it but it’s not working at all. French shows all posts but English shows nothing.

    Was this corrected in the current release ?

  9. I cannot find registration to forum so i try to post bug report here: those are notices with wp-debug to true

    NOTICE: wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php:4859 – Undefined index: cs
    NOTICE: wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php:4880 – Undefined index: cs
    NOTICE: wp-content/plugins/wpml-sticky-links/inc/sticky-links.class.php:357 – Undefined index: path
    NOTICE: wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php:4859 – Undefined index: en
    NOTICE: wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php:4880 – Undefined index: en

  10. and one more

    P.s.: please test everything with wp-debug to true. not only because it is good programmer practice but e.g. we got rules that we cannot use such buggy plugins for security reasons

    P.S.: I’m using latest paid version

    Notice: get_bloginfo was called with an argument that is deprecated since version 2.2! The home option is deprecated for the family of bloginfo() functions. Use the url option instead. in /var/www/vhosts/elektrickeauto.cz/httpdocs/wp-includes/functions.php on line 3387
    Notice: Undefined property: WP_Query::$queried_object_id in /var/www/vhosts/elektrickeauto.cz/httpdocs/wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php on line 3910

    Notice: Undefined property: WP_Query::$queried_object_id in /var/www/vhosts/elektrickeauto.cz/httpdocs/wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php on line 3910

    • Obviously, we develop with WP_DEBUG enabled.

      These notices are coming in combination with your theme. WPML works differently with different themes. You should report these in our forum. It has a SPAM protection, so if you’re posting multiple links with very little text, Akismet might trigger and delete your post.