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.

This topic contains 7 replies, has 2 voices.

Last updated by vorakarnw 3 weeks ago.

Assigned support staff: Bruno.

Author Posts
July 19, 2019 at 2:07 pm #4246927

vorakarnw

I brought the plug-in yesterday and I fill up the automate advance translation work for USD 49. I have problem on translation gear appear all the time then I delete the plug-in and roll back my database as it was crashed. I install everything again and I lost all the "word" that I brought. MY publisher package invoice is ATE-001582 that you are following?
- and brought another USD 9 wanted to finish my work and it doen not work. The auto translator always stuck at preview page at attached image.

July 19, 2019 at 9:27 pm #4248315

Bruno
Supporter

Languages: English (English ) Portuguese (Brazil) (Português )

Timezone: America/Sao_Paulo (GMT-03:00)

Thank you for contacting us. What kind of page are you trying to translate? Is it a page created with some Page Builder?

I'll need to request temporary access (wp-admin and FTP) to your site - preferably to a test site where the problem has been replicated if possible - in order to be of better help.

You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.

Note:

*** Please let me know exactly what steps should I follow to see the problem. For example, what page is this problem happening to?

*** Please, can I install the Duplicator plugin (or All in One Migration) to make a copy of your site and install it on my test environment? This will help me debug the problem.

*** Note: Please make a full backup of your site.

Privacy and Security when Providing Debug Information for Support: https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/

Thank you.

July 22, 2019 at 6:10 pm #4260713

Bruno
Supporter

Languages: English (English ) Portuguese (Brazil) (Português )

Timezone: America/Sao_Paulo (GMT-03:00)

Thank you. Apparently, the problem is only happening in Chinese. In Russian, the content was displayed correctly.

I will contact 2nd tier support so they can check what may be happening in the preview of Chinese content. Soon I will contact you as soon as I have a 2nd tier support response.

Thank you.

July 23, 2019 at 4:18 pm #4267971

vorakarnw

Thank you Bruno. Today I finished translating Russian language.

for chinese, do you still need to access my administration back end?

As I have changed the server today. Please sent me the form again if you needed.

Thank again for you support

July 23, 2019 at 10:07 pm #4269151

Bruno
Supporter

Languages: English (English ) Portuguese (Brazil) (Português )

Timezone: America/Sao_Paulo (GMT-03:00)

Hi,

>>> for chinese, do you still need to access my administration back end?

Yes, 2nd tier support will probably need the credentials to access your site and test. Your next message will be private again.

Thank you.

July 24, 2019 at 8:01 pm #4277353

Bruno
Supporter

Languages: English (English ) Portuguese (Brazil) (Português )

Timezone: America/Sao_Paulo (GMT-03:00)

Hi,

Thank you. This is already escalated to the 2nd tier support. Soon 2nd tier support will check this out and we will contact you.

Thank you.

September 21, 2019 at 3:20 am #4615121

Bruno
Supporter

Languages: English (English ) Portuguese (Brazil) (Português )

Timezone: America/Sao_Paulo (GMT-03:00)

Hello,

My sincere apologies for the delay. According to 2nd tier support, this was a bug but it has already been fixed. Please, could you check if ATE is working correctly now for the secondary language?

Please, let me know if I can help with any other questions you may have about it. I'll be happy to help.

Thank you.

September 24, 2019 at 1:15 am #4626969

vorakarnw

My issue is resolved now. Thank you!