Hello, do we need to keep XMLRPC enabled in WordPress in order to send and receive translations via memoQ software, or for any other reason that you might know related to WPML?
I've just gotten the reply from our proxy team, and the answer to your question is divided into two sections:
1) WPML needs the XMLRPC for retrieving the translation jobs automatically, so when you use a custom URL, the translation proxy server won't be able to communicate with your site.
2) However, you can disable the XMLRPC module and retrieve the translations manually from WPML-> Translation Management when you get the notification of completing the translation job from the translation service. (Kindly check the attached screenshot)
I hope this helps you. If you need further info, please let me know.
"WPML needs the XMLRPC for retrieving the translation jobs automatically, so when you use a custom URL, the translation proxy server won't be able to communicate with your site."
1. If we block public access to the xmlrpc.php file, would WPML still function normally? I'm wondering whether WPML has some sort of privileged internal access to this file, in which case WPML would not be affected if we block public access to the xmlrpc file but leave the file intact and available internally to plugins.
2. Is there a setting in WPML that we may configure with an updated XMLRPC URL, so that the translation proxy server knows where to communicate with XMLRPC if we change the URL?
3. Does XMLRPC affect our ability to send translation jobs to a translation service provider? Or does it only affect our ability to retrieve jobs? (If it matters, we work with Morningside, a translation agency listed on wpml.org, so they integrate directly with the WPML software on our site.)
1) WPML should function normally if you block public access to the file.
2) I'm afraid there is not such a setting in WPML settings.
3) You would be able to send the jobs without any issues, and you can retrieve them manually using the button in my previous reply attached screenshot.
Hi Osama, thank you for the answers, and for your patience with my slow reply.
We're going to test this -- blocking public access to XMLRPC, and then sending test translations -- to test out the functionality as you've explained it.
So thank you. I think we won't have an update on this until the week of August 15th, due to scheduled time off, so feel free to pause this support ticket -- is that a thing? -- or close this request for now, and I can reopen the ticket or create a new one if we run into any problems.
