{"id":713905,"date":"2015-09-28T23:05:48","date_gmt":"2015-09-28T23:05:48","guid":{"rendered":"https:\/\/wpml.org\/?p=713905"},"modified":"2015-09-29T08:20:45","modified_gmt":"2015-09-29T08:20:45","slug":"migration-for-icanlocalize-clients-to-wpml-3-2-x","status":"publish","type":"post","link":"https:\/\/wpml.org\/he\/announcements\/2015\/09\/migration-for-icanlocalize-clients-to-wpml-3-2-x\/","title":{"rendered":"Migration for ICanLocalize clients to WPML 3.2.x"},"content":{"rendered":"

Finally, after very long (and complex) development, ICanLocalize<\/a> clients can upgrade WPML to its current version and continue to enjoy a streamlined translation workflow.<\/strong><\/p>\n

What's Changed in WPML 3.2? (that took so long)<\/h2>\n

WPML 3.2 includes a complete new interface to translation services. You probably know that now WPML offers more translation options, with great new translation services coming very soon.<\/p>\n

This update meant that WPML now communicates with translation services using a different method than before. Instead of working directly with ICanLocalize, WPML communicates with what we call "Translation Proxy". This middle server is a huge help, as it allows us to monitor the communication and quickly troubleshoot anything that goes wrong. It also means that translation services don't need to directly communicate with individual WordPress sites (which saves a heap of problems with PHP libraries, compatibility, encoding, etc.).<\/p>\n

The problem was, we didn't have a way to move existing ICanLocalize projects from the 'old' way to the new one. Now we do \ud83d\ude42<\/p>\n

How to Update to the Current WPML Version<\/h2>\n

All WPML sites can now move to the current version. If you are using ICanLocalize, you will see a pretty scary message about having to downgrade. This message is from before the time we had this migration plugin.<\/p>\n

\"Message<\/a>
Message about incorrect WPML version. Ignore the on-screen instructions.<\/figcaption><\/figure>\n

Ignore it. Don't downgrade WPML and follow the rest of the instructions here.<\/p>\n

Go to your WPML.org account<\/a> and click on Downloads<\/strong>. Scroll all the way to the bottom and download the plugin called Migrate ICanLocalize Translation to WPML 3.2<\/strong>. Install it on your site and activate.<\/p>\n

The scary message about having to downgrade will go away. Now, go to the new menu that the plugin created for the migration process.<\/p>\n

Go to WPML->Migrate ICanLocalize Translation to WPML 3.2<\/strong>.<\/p>\n

\"Migration<\/a>
Migration plugin admin screen<\/figcaption><\/figure>\n

You will see two buttons. First, click to migrate the account to WPML 3.2. This runs almost instantly. Then, click to migrate the jobs.<\/p>\n

You should be all set. When you go to WPML->Translation Management->Translators, you should see your current ICL translators selected and completed jobs will appear again in WPML's Translation Dashboard.<\/p>\n

\"Completed<\/a>
Completed jobs waiting in the Translation Dashboard<\/figcaption><\/figure>\n

If there are any problems in this migration process (there should not be), the migration plugin will report them on the screen. Create a new ticket in WPML technical support forum<\/a>, copy what you see and paste in the forum thread. Be sure to explain what you are doing and what you are seeing.<\/p>\n

You no longer need the migration plugin. Go to Plugins<\/strong> and deactivate it. The migration plugin does't do anything else. Keeping it active will not cause any problems, but it's not needed for your sites.<\/p>\n

The right order to update WPML and WordPress<\/h2>\n

If you are running an older version of WPML, chances are you are also running an older version of WordPress.<\/p>\n

A safe update process will be:<\/p>\n

    \n
  1. Back up your site's database<\/li>\n
  2. Update ALL of WPML's components to the current version<\/li>\n
  3. Install and run the migration plugin for ICanLocalize clients (obviously, only if you are an ICanLocalize client)<\/li>\n
  4. Update WordPress<\/li>\n<\/ol>\n

    Automatic Version Update for Everyone<\/h2>\n

    This week, we want to see how this migration process goes, so we're letting it run on manual mode. We ran comprehensive testing on this process and it's already running successfully on all our sites too.<\/p>\n

    Next week, we will finally push automated updates for all existing WPML sites to the current version.<\/p>\n

    Questions? Suggestions? Ideas? Leave your comments and we'll get back to you.<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"

    Finally, after very long (and complex) development, ICanLocalize clients can upgrade WPML to its current version and continue to enjoy a streamlined translation workflow. What's Changed in WPML 3.2? (that took so long) WPML 3.2 includes a complete new interface to translation services. You probably know that now WPML offers more translation options, with great […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0,"_uag_custom_page_level_css":"","ep_exclude_from_search":false,"footnotes":""},"categories":[3],"tags":[],"class_list":["post-713905","post","type-post","status-publish","format-standard","hentry","category-announcements"],"spectra_custom_meta":{"_edit_lock":["1443534895:64191"],"_edit_last":["2"],"_alp_processed":["1443514845"],"_views_template":["0"],"ratings_users":["0"],"ratings_score":["0"],"ratings_average":["0"],"_oembed_f56bf1c5a64a315a94e4cbf7a197b2b0":["