This thread is resolved. Here is a description of the problem and solution.
Problem:
A client is trying to use WPML to make template files in a theme multilingual. When they tried to translate text using __(), they ran into an issue where the auto-translate button was not showing up. Solution:
1. We suggested the client to contact their hosting or webmaster to see if external connections or XLIFF file creation is blocked.
2. We suggested them to test on different servers and see if that solves the issue.
3. We recommended that they set their WordPress address (URL) and site address (URL) to be the same in their WordPress settings.
It's possible that this solution is outdated or doesn't apply to your case. If so, please open a new support ticket. We also strongly recommend that you check for related known issues, check the version of the permanent fix, and make sure that you have the latest version of your theme and/or plugins installed. Check for known issues
If you need further assistance, please visit the WPML support forum.
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.
I am reaching out as there has been some progress.
To begin with the conclusion, it seems that the issue is resolved for now.
Regarding s16.n-sitecase.net, we are still requesting an investigation from the server company. This issue has not been resolved yet.
As a test, I set up the site on a different shared server and confirmed that the automatic translation function worked properly.
By the way, I would like to confirm the URL settings for the WordPress installation.
When I used the following settings, some functionalities were unstable (the data retrieval in the translation dashboard remained stuck in a loading state):
WordPress Address (URL): hidden link
Site Address (URL): hidden link
However, with the settings below, there seem to be no issues so far:
WordPress Address (URL): hidden link
Site Address (URL): hidden link
Could this issue also be related to the server?
Ideally, I would like to install WordPress inside the /wp/ directory for operation, but if that is too troublesome, I will install it directly in the document root.
Let us know what and when server support gets back to you.
As for 2nd server where you did some tests, glad to hear it works fine there.
You can install WP in a subdirectory and use it like that, just the WP address and site URL should be the same if possible, I think you can set in URL domain settings to show that subdirectory by default.
Nevertheless, it should not cause major issues with WPML, we have a few reports for other things like language switcher, and SEO, so may be best if you can not use it in that way. If you have any other WPML issue you can always open a new ticket and we would be glad to check it and help further.
Sorry for the delayed response.
I have received the investigation results from the server company.
Here is an excerpt:
**************************
As a result of the investigation, regarding the XLIFF data transmission to WPML,
our server has not implemented any restrictions or blocks on external servers.
Unfortunately, our support team is unable to provide further verification regarding the plugin's operation.
Therefore, we regret to inform you that further investigation on our end is difficult.
**************************
Since I was able to confirm that it works on a different shared server, I suspect there may be an issue with the current server.
However, based on the response above, I will proceed with the understanding that there are servers where it works and servers where it does not.
Also, thank you for your information regarding the WP address and site address.
I will proceed with both the WP address and site address set to be the same.
I apologize that we were unable to resolve the issue.
If anything else comes up, I would appreciate your continued support.
Sorry to hear, that they did not find anything, I still suspect it has to be something with the server blocking access to the WPML server or saving in the database, as you have seen it works fine on another server.
If anything else comes up we would be glad to help, feel free to contact us again.
