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.
