Skip Navigation

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

Problem:
The client is experiencing issues with importing XLIFF 1.2 format files for translation in a WordPress site developed locally using LOCAL by Flywheel. Despite the REST API being disabled, the client receives responses from the server when making HTTPS requests to specific WPML REST API endpoints. Additionally, there is confusion about the automatic naming of XLIFF files for different languages, which complicates the translation process.
Solution:
If you're experiencing similar issues with the REST API and XLIFF file imports on a local server, here are the steps we recommend:
1. If the REST API is accessible and responding to requests on your local server, you can safely ignore any notifications from WPML indicating that the REST API is disabled. This might be a communication issue due to the site running on localhost.
2. Do not change the names or any information inside the header of the XLIFF files. Altering these details can prevent the files from being imported correctly.

Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket.

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.

Tagged: 

This topic contains 3 replies, has 2 voices.

Last updated by Andreas W. 9 months ago.

Assisted by: Andreas W..

Author Posts
July 6, 2024 at 8:57 am #15902594

elisabethL-7

Background of the issue:
Enable REST API
I made https request and I receive response from server (I use localy LOCAL by Flywheel)

Symptoms:

HI,
I am having difficulty importing xliff 1.2 format files in different languages ​​on the site developed locally with 'LOCAL by Flywheel'
You wrote to me in another support ticket that it was because of the REST API which was disabled that it didn't work;
However, when I test https requests on /wp-json/wpml/tm/v1 and /wp-json/wpml/st/v1 and /wp-json/wp/v2/ , I receive responses from my local server (see print screens)

Questions:
how come the REST API responds properly when it is supposedly not activated? I think it's a big bug.
Can U resolve this please?

my site was ready to receive the xliff 1.2 files in the different languages ​​to translate the site, including the pages, menus, header and footer and that all the translations were placed in the right place, and that the menus of the different languages ​​were synchronize as expected; but it doesn't work and I'm certainely not the only one how develop locally with LOCAL BY FLYWHEEL.
THANK YOU

July 6, 2024 at 5:48 pm #15903957

Andreas W.
Supporter

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

Hello,

Do you receive any failure message when trying to import the XLIFF files?

Example:
https://wpml.org/faq/the-uploaded-xliff-file-doesnt-belong-to-this-system/

Best regards
Andreas

July 9, 2024 at 6:58 am #15918280

elisabethL-7

Hi Andreas,

No problem when importing.
But I received new files now and it work fine now.
But REST API is disable and I don't understand why...

I had also a problem with the construction of my site made with Elementor Pro: my page was not a page but a model of page was show on the screen in place of a true page (not sure you'll understand wath I mean)...

The problem came also with automatical creation of xliff files asked for 2 languages in the same time. There's no informations for the translation service to know in wich language files must be translate with the name of job.
Exemple : xliffjob149.xliff and xliffjob150.xliff .
job149 automatically created for English translation and job150 for Dutch. It'll be better at automatically job creation that files inclued language: job149_EnEn and job150_NLBe : simple for everybody to dispatch jobs.
Is it possible to format the name of job automatically with name of language inclueded?

Thanks for support

July 9, 2024 at 3:19 pm #15921724

Andreas W.
Supporter

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

If the REST API is accessible, then the notification on WPML might be a communication issue as the site runs on localhost.

You can ignore this notification in this case.

About the XLIFF file:

You should not change the name of those files. If you change the names or any information inside the header of the files, the import will not work.