I'm trying to translate my EN page to Bosnian, Croatian, Czech, Danish, Dutch, Estonian, Finnish, French, Hungarian, Italian, Latvian, Lithuanian, Norwegian Bokmal, Polish, Portugese (Portugal & Brazil), Romanian, Slovak, Slovenian, Spanish & Swedish.
I started it on Saturday & since then it only shows, that the translation is running but nothing has changed yet. It's shown, that credits are going to be used (pay-as-you-go-credits).
The page is not shown in my WPML account as well. How can I solve this issue to process the translation?
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+01:00)
Hello!
1) Let's start by meeting WPML's minimum requirements:
Please add the following code in your wp-config.php file, right after the database information lines of code:
define('WP_MEMORY_LIMIT','256M');
2) Go to WPML -> Support -> Troubleshooting and press the following buttons:
• "Clear the cache in WPML"
• "Remove ghost entries from the translation tables"
• "Fix element_type collation"
• "Set language information"
• "Fix post type assignment for translations"
3) It's very likely that the system is stuck because it's still reading if there are more pages to consider since it seems you have selected "translate everything".
i wouldn't recommend you do that before you know that the payment you're going to get for them could be bigger than you expected.
If that's ok by you and it fits your budget, then we can continue using this mode, otherwise i'd suggest you go to WPML > Settings and swith to "translate what you choose" so you can start small, check the translations, maybe translate in 1 language first and have more control over what you translate.
You can still translate in bulk but it will be under your decision.
-------------------
Let me know how you want to continue so i can understand what to do next and what to suggest 🙂
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+01:00)
Hm, ok, if you use "translate everything" mode, the jobs are cancelled automatically, so could it be you were using "translate what you choose" in the past before that or tried to send them again with this one, instead?
Anyways, i cancelled them for you so you can try again. try with "translate what you choose" for now and make sure you check if they finish now.
I also saw you were about to hit the first time limit (when you reach 195.000 for the first time) so you'll have to pay a one time fee of 100usd to continue and will be used later during the billing cycle (June 3rd on your case) and discount the first 195000 credits from your total usage.
Try it out first with one or 2 languages and let me know how it goes.
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+01:00)
Ok, let's see. i see you're sending tons of jobs to translate. remember that if you have 10 languages, each page will become 10 jobs, so if you send 10 pages you'll get 100 jobs.
I had asked you to try with only one page, exactly because of this.
May i have permission to cancel these jobs and try with only one page, one of the pages you wanted to translate, please? that way i can see what's going on.
-----------------
At the same time, if you're using any server-side cache, please flush it and deactivate it while we work on this issue because many times the problem is just that the cache shows you old versions of the site and doesn't retrieve the translations.
for your test, please choose e.g. a product page. since i don't want to translate ALL pages and i want to select afterwards which page should be translated.
but product pages should be all translated, so you can choose a random one
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+01:00)
Please check this video: hidden link
I had translated one page and it worked without issues. it did take a bit before it was retrieved but that has nothing to do with WPML and instead it's all about server resources on your end. however it only took a minute or two instead of a few seconds. the product that i tested here was: "Beamlight UV Lash System S6 - Complete Set"
I then started to record myself and tried to translate another product: Beamlight UV Lash System S6
and this one instead got stuck. i can see on our system that our system received the page, translated it automatically and send it your way but your system couldn't upload the translation.
Iran many tests and i believe the problem is coming from a plugin that might be interfering here with our file upload. Can you tell me if:
- This is a live site?
- You have or can provide a staging environment?
- You have a server-side cache?
because i'd like to run a "minimal test" (Disable all the plugins on your site to try to spot the actual error we get while retrieving the translations) to see if we can fix this problem faster.
If you don't have a staging site nor can provide one, i can give you a space on our servers so we can temporarily create a clone that we can run our tests on without any risk on your end.
i will create a staging site and send you the credentials asap.
a plugin of course can also be the reason, but this is a clone from my other site where i use wpml and it does not have any other plugins active. and the other site works like a charme 🙂
Languages: English (English )Spanish (Español )Italian (Italiano )
Timezone: Europe/Rome (GMT+01:00)
I'm sensing a pattern here. the first time i translate a product, it works. the second time i try, it gets "stuck" and this is usually a sign of cache, but a server-side or database type of cache. are you sure your server doesn't have or use any type of cache on their servers?
However i think that the following will help us out:
- Downgrade PHP to version 7.4. you have a TON of plugins throwing deprecation errors due to php 8.1 and that means that your server is constantly using more resources than it should
- Uninstall WooCommerce and the WPML plugins. download them again from https://wpml.org/account/downloads/ and install them again from scratch, not via FTP but from Plugins > Add New
- Ask your hosting to check your database: the options table is missing either the primary key or the autoincrement option and if this is happening to a default WordPress table as important as the "options" table, then this is very likely happening to other tables.
- What hosting are you using, because they can probably be able to help you out here.
---------------
Once the changes are made on the original site, you can recreate the staging site and let me know so i can try to understand what else is going on.
