Background of the issue:
I was trying to set up WPML String Translation tables, but they didn’t get created. I talked to support and was instructed to proceed with the setup. I did so and autotranslated the site.
Symptoms:
Now, the page gets a critical error when the string translation plugin is activated. If the problem is not solved, I have to restore the site to a healthy state. I will lose the translation credits that I used during this run and I want them back.
Questions:
How can I resolve the critical error when the string translation plugin is activated?
How can I recover or retain the translation credits if I have to restore the site?
i m sorry but yr AI got it all wrong.
I installed wpml on a fresh site, no extra plugins, clean code.
i got a rest api warning.
i contacted yr support. they told its false positive, since we can call it
yr support instructed me to continue setting up
i did
i autotranslate the site and spend 22 euros
the site gets a critical error when the string translation plugin is active.
i get thelog
An error of type E_ERROR was caused in line 70 of the file /home/alexiome/public_html/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/wpml/src/Legacy/Component/Translation/Application/String/Repository/StringBatchRepository.php. Error message: Uncaught WPML\Core\Port\Persistence\Exception\DatabaseErrorException: Table 'alexiome_g3bo1.yhoj_icl_string_batches' doesn't exist in /home/alexiome/public_html/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/wpml/src/Infrastructure/WordPress/Port/Persistence/DatabaseWrite.php:66
now the string translation plugin is inactive. when active the site gets a critical error.
I wanna fix my site and not loose the translations credits used
thanx
❌ Please make a full website backup before proceeding ❌
1.
- With ST inactive, go to WPML → Support → Troubleshooting.
- Run “Fix WPML tables” twice.
- Click “Set language information / Recreate ST tables” options if visible, then “Clear cache in WPML”.
- Try activating String Translation.
2.
If the issue persists:
- Make a full file+DB backup.
- Keep WPML String Translation (ST) deactivated to avoid the fatal.
- Add this temporary code at the end of your (child) theme’s functions.php :
function wpml_fix_missing_icl_tables(){
if ( function_exists('icl_sitepress_activate') ) {
icl_sitepress_activate(); // Re-runs WPML installer and creates any missing tables
}
}
add_action('wp_footer','wpml_fix_missing_icl_tables');
- Visit the site’s homepage once while logged in (this triggers the installer).
- Remove the snippet.
- Go to WPML → Support → Troubleshooting and run, in order:
“Fix WPML tables” → “Clear cache in WPML” → “Remove ghost entries from String Translation tables” (if present) → “Recreate ST MO files”.
I followed your instructions: with ST inactive I ran Fix WPML tables twice and cleared WPML cache, then triggered the installer once via a one-shot MU plugin calling icl_sitepress_activate(), reinstalled WPML String Translation, and verified the missing schema—yhoj_icl_string_batches now exists (indexes added). WPML and ST are working, no more critical errors, translations are fine. The only remaining issue is the wizard still shows “The WordPress REST API must be enabled,” but hidden link
returns 200 JSON and includes wpml/v1. Please take a look into that issue, should not exist on a well written simplke site with such topnotch code like wpml. thank you so much 🙂
i will work tonigjht on the site , if something is ubnormal a will ask u again so far no more fatal errors but the rest api issue must also be solved
New threads created by Otto and linked to this one are listed below:
