Symptoms:
The new product is not translating automatically via WPML. An error is visible under WPML → Support → ATE Error Log: 'The uploaded XLIFF file doesn't belong to this system.'
Questions:
Why is the new product not translating automatically via WPML, even though we followed the recommended steps to delete and recreate the product, as mentioned in the links?
What does the error 'The uploaded XLIFF file doesn't belong to this system' mean?
We have newer versions of our plugins.
WPML 4.8.2
Strings Translation 3.4.1
WPML Multilingual & Multicurrency for WooCommerce 5.5.2.1
Please update our plugins and check if the problem persists.
You can check for updates on your site here: hidden link
Please click the Check for Updates button.
If it doesn't help, and you need further assistance with this, please share the access details to your site with me. Please also send me the link to the product that is experiencing the problem. I'm enabling a private message for the following reply.
Privacy and Security Policy
We have strict policies regarding privacy and access to your information. Please see: https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/ **IMPORTANT**
- - Please back up the site files and database before providing us access. --
-- If you have a staging site where the problem can be reproduced, it is better to share access to the staging site.--
While we are still waiting for your reply, I've discussed your case with my supervisors. Since you have a large site with multiple secondary languages, we recommend that you refrain from updating WPML on your production site at this time. Instead, it is better to try it on a staging site and see if everything works correctly. In any case, we are still waiting for the access details from you. Please specify the new product you created that you were unable to translate.
Could you please share the access details to your site with me?
I'm enabling a private message for the following reply. Privacy and Security Policy
We have strict policies regarding privacy and access to your information. Please see: https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/ **IMPORTANT**
- - Please back up the site files and database before providing us access. --
-- If you have a staging site where the problem can be reproduced, it is better to share access to the staging site.--
Peter here. Then initial message was from our developer Prakash
We currently not able to give you access to our production site as our Hosting provider Contabo will move it to another data center from tonight till tomorrow morning.
Prakash will install and test the plugin updates at our staging site, however this will take some time.
We only have this problem with one product that was deleted and setup with a new id, besides that translation seems to be working.
We keep on getting the error “The uploaded xliff file doesn't belong to this system.” (WPML Job ID 89381 / ATE Job ID 161281907) with random interval ( 1 – 10 minutes). We have of course cancelled all translation jobs. Is there a way we can get rid of this repetitive error message (e.g. by deleting the xliff file)?
I have a feeling this might be the reason we are not able to translate the product.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Hello,
The job that is showing that issue is hidden link for the language pair: English-Bulgarian
I can see that job was sent on Sept. 30th, so is that any of the ones you cancelled?
I cancelled it on our end because that means the system was still requesting it.
----------------
Can you let me know if you are using a server-side cache? because if you are, that could be part of the problem and if that's the case, then could you let us know the configuration you're using and which type so we can try to recreate it and see if there's something we can do about it?
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Hello,
The page you're linking here seems to have been sent last on Oct 2nd, If you resent it again after the WPML update, then there's definitely something off.
And yes you have Server-side caching enabled (OPCache). Flush it or disable it, cancel the jobs via WPML > Support > Troubleshooting > Cancel "In Progress" Automatic jobs and then resend the page via WPML > Translation dashboard so it gets unstuck.
Let me know if that works (I'm trying to recreate the problem but it's proving to be impossible so far because there must be something that first triggered the job to get stuck and it's not something easy to even find out without any sort of site access).
I flushed and disabled OPcache, followed the steps to cancel the jobs via WPML > Support > Troubleshooting > Cancel 'In Progress' Automatic jobs, and then resent the page via WPML > Translation Dashboard, but the translation job is still stuck.
Please send me a private message, and I’ll provide you with site access so you can take a look at the issue.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Thanks for the access! I'm sure it will help a lot.
You can add the credentials now. If there's a reference page I should test in, please let me know and if possible let me:
- Add a file manager plugin (Or provide FTP access which is even better). I just need to enable the debug.log and check it out when testing.
- Allow me to create private pages if needed to test there
- Tell me if I can make minimal edits (a period or something small that won't affect the front-end) when testing.
What I'll proceed to do is test live what happens when I send a job from your site vs what we get.
since there are server-side caching, then allow me to flush it or temporarily disable them while testing to ensure they don't get in the way (if they are a problem, we'll then know what to do).
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Ok, I think I found the issue you have, we actually were investigating this last week and one of our devs should get to the bottom of the situation soon.
Please do not remove my access, We're not going to use it for now but please don't cancel the jobs I sent (I added extra credits in case it charged you anything), we're using this to track what's going on in your site.
I may have to access from time to time when the devs instruct me to, but I won't make any change, at most cancel and resend the same job you sent me as a reference: hidden link
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Hello!
The problem should be solved. We did a patch on our WPML Multilingual for WooCommerce plugin to make sure it doesn't intrude in your products (it was indeed a small compatibility issue due to something added by an extension, but it was failing on our end).
The change is the following:
Edit wp-content/plugins/woocommerce-multilingual/inc/class-wcml-tp-support.php and update line 158 from
I noticed that we are encountering a site key error in the WPML settings. You can find the details under WPML -> Support -> Advanced Translation Editor -> Error Logs. Please see the attached screenshot for reference.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+02:00)
Hm, my last message didn't go through.
I had mentioned then that this is a temporary issue caused by the migrations when you select "this is a copy of my site" option in the migration. This shouldn't affect the translations, more the credit transfer when you do it from WPML.ORG which you're not doing, currently so you can ignore this (we're changing this anyways and quite soon too).
if you do want to get rid of it, delete the domain that has the issue, from your WPML.ORG account and then create and assign a new one.
