Please make sure to update to WPML 4.3.5 and check our list of Known Issues before reporting

Hi, Amit here, I am the WPML Support Manager, our current ticket queue is high, update your WPML plugins and make sure you meet the minimal requirements for running WPML before reporting an issue please - many tickets are resolved doing that

Please look at our updated list of Known Issues and you can also use our support search to find helpful information and of course review our documentation before opening a ticket.

If you do need to open a ticket please make sure to provide us with all the needed information as described in this page

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Our next available supporter will start replying to tickets in about 0.62 hours from now. Thank you for your understanding.

This thread is resolved. Here is a description of the problem and solution.

Finally, after very long (and complex) development, ICanLocalize clients can upgrade WPML to its current version and continue to enjoy a streamlined translation workflow.

Problem :

It wasn't possible to use ICanLocalize translation service with the WPML greater than 3.2, if you have done some translation through the service already.

Solution :

Read carefully this article : https://wpml.org/2015/09/migration-for-icanlocalize-clients-to-wpml-3-2-x/

Just to summarize about how to Update to the Current WPML Version :

1. Take a backup 2. Deactivate and remove an old version of WPML plugins 3. Download the newest ones from here : https://wpml.org/account/downloads/ 4. Install and activate the latest WPML plugins (WPML 3.2.7, WPML ST 2.2.6, WPML TM 2.0.5) 5. Download plugin "Migrate ICanLocalize Translation to WPML 3.2" : https://wpml.org/download/migrate-icanlocalize-translation-to-wpml-3-2/ 6. Install and activate it. 7. Go to the new menu that the plugin created for the migration process WPML->Migrate ICanLocalize Translation to WPML 3.2 8. 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. 9. You no longer need the migration plugin. Go to Plugins and deactivate it.

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, copy what you see and paste in the forum thread. Be sure to explain what you are doing and what you are seeing.

This topic contains 218 replies, has 59 voices.

Last updated by Andrey 4 years, 1 month ago.

Assigned support staff: Andrey.

Author Posts
September 15, 2015 at 12:27 pm #704531

michelv-8

I have the xml problem under an existing item :
https://wpml.org/forums/topic/re-using-wpml-and-yoast-seo-plugin-for-language-specific-xml-sitemaps/#post-704513

September 15, 2015 at 1:08 pm #704593

George Botsev
Supporter

Languages: English (English )

Timezone: Europe/Sofia (GMT+02:00)

@michelv-8 that ticket is long time closed as resolved. Your issue may be caused by a different problem. I would advice you to open a new ticket in the forums.

September 22, 2015 at 11:18 am #709512

harperA

Hi there,

We are using:

WooCommerce Multilingual
Version 3.6.11

WPML Media
Version 2.1.13

WPML Multilingual CMS
Version 3.2.7

WPML String Translation
Version 2.2.6

WPML Translation Management
Version 2.0.5

but have found that menu syncing fails. Could you please forward us a set of these plugins ( older versions ) which will work together and allow us to sync the translations in WPML Multilingual CMS?

We are also using the following plugins:

Advanced Custom Fields
Version 4.4.3 | By Elliot Condon

Advanced Custom Fields: Repeater Field
Version 1.1.1 | By Elliot Condon

Category Order and Taxonomy Terms Order
Version 1.4.6.1 | By Nsp-Code

Contact Form 7
Version 4.2.2 | By Takayuki Miyoshi

Disable XML-RPC Pingback
Version 1.1 | By Samuel Aguilera

Regenerate Thumbnails
Version 2.2.4 | By Viper007Bond

Set email sender
Version 0.1 | By Johan Hedberg, City Network Hosting AB

Simple 301 Redirects
Version 1.06 | By Scott Nellé

Varnish HTTP Purge
Version 3.7.3 | By Mika Epstein

W3 Total Cache
Version 0.9.4.1 | By Frederick Townes

WooCommerce
Version 2.4.6 | By WooThemes

Woocommerce CSV Import
Version 3.0.5 | By Allaerd Mensonides

Woocommerce CSV Import Custom field add-on
Version 1.0.0 | By Allaerd Mensonides

Woocommerce CSV Import variable products add-on
Version 2.0.0 | By Allaerd Mensonides

WooCommerce GestPay PRO (Banca Sella)
Version 20150312 | By Mauro Mascia

WooCommerce Google Analytics Integration
Version 1.3.0 | By WooThemes

WooCommerce Multilingual
Version 3.6.11 | By OnTheGoSystems

WooCommerce Table Rate Shipping
Version 3.6.4 | By Bolder Elements

WooCommerce UPS Toolbox
Version 1.15.26 | By Catman Studios

WooThemes Helper
Version 1.3.0 | By WooThemes

WP-Cron Control
Version 0.7.1 | By Thorsten Ott, Erick Hitter, Automattic

WP-Optimize
Version 1.8.9.10 | By Ruhani Rabin

WPML Media
Version 2.1.13 | By OnTheGoSystems

WPML Multilingual CMS
Version 3.2.7 | By OnTheGoSystems

WPML String Translation
Version 2.2.6 | By OnTheGoSystems

WPML Translation Management
Version 2.0.5 | By OnTheGoSystems

Yoast SEO
Version 2.3.4 | By Team Yoast

We would like to continue to use all the above plugins and would be most grateful if you could provide us with versions of your plugins which will allow us to do this without loss of functionality.

Currently attempts to sync result in '500' errors which are visible in the javascript console and seem to be coming from admin-ajax.php

Many Thanks.

September 22, 2015 at 3:22 pm #709808

Andrey
Supporter

Languages: English (English ) Russian (Русский )

Timezone: Europe/Kiev (GMT+02:00)

@harpera, as far as I can see that we don't have any open issues about "menu syncing fails". So, I can't suggest you any older WPML versions, it should be working as expected.

In order to ensure that your problem gets the attention it deserves, please open a new ticket detailing your issue.

September 23, 2015 at 2:37 pm #710682

charlesS-6

Hello Andrey,

Do you have any information about when a new WPML version ICL - friendly?

In the meantime I am remaining on WPML 3.1.9.7 + String translation 2.1.4

Thanks a lot

Charles

September 23, 2015 at 3:01 pm #710710

Andrey
Supporter

Languages: English (English ) Russian (Русский )

Timezone: Europe/Kiev (GMT+02:00)

@charless-6, development team is working on that version, but I can't give you any updates yet. Once it's coming I let you all know here.

September 23, 2015 at 3:02 pm #710711

charlesS-6

Thanks Andrey 😉

September 29, 2015 at 9:48 am #714259

Andrey
Supporter

Languages: English (English ) Russian (Русский )

Timezone: Europe/Kiev (GMT+02:00)

Finally, after very long (and complex) development, ICanLocalize clients can upgrade WPML to its current version and continue to enjoy a streamlined translation workflow.

Read carefully this article :
https://wpml.org/2015/09/migration-for-icanlocalize-clients-to-wpml-3-2-x/

Just to summarize about how to Update to the Current WPML Version :

1. Take a backup
2. Deactivate and remove an old version of WPML plugins
3. Download the newest ones from here :
https://wpml.org/account/downloads/
4. Install and activate the latest WPML plugins (WPML 3.2.7, WPML ST 2.2.6, WPML TM 2.0.5)
5. Download plugin "Migrate ICanLocalize Translation to WPML 3.2" :
https://wpml.org/download/migrate-icanlocalize-translation-to-wpml-3-2/
6. Install and activate it.
7. Go to the new menu that the plugin created for the migration process
WPML->Migrate ICanLocalize Translation to WPML 3.2
8. 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.
9. You no longer need the migration plugin. Go to Plugins and deactivate it.

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, copy what you see and paste in the forum thread. Be sure to explain what you are doing and what you are seeing.

October 12, 2015 at 3:54 pm #723037

Andrey
Supporter

Languages: English (English ) Russian (Русский )

Timezone: Europe/Kiev (GMT+02:00)

We're closing this ticket, if there are any problems in the migration process, then you will need to create a separate ticket.