[Resolved] Problem with string translation

Hi WPML Support,

we're encountering persistent problems with the String Translation module. Specifically:

The scanning process often freezes or becomes unresponsive, even when all caches are cleared.

We have 53,638+ strings registered (see attached screenshot).

Translations don’t reliably appear in Italian or English, even after saving them.

The debug.log repeatedly shows:

pgsql
Kopieren
Bearbeiten
PHP Notice: Function _load_textdomain_just_in_time was called incorrectly.
This may point to a deeper issue in how strings are registered or loaded – possibly too early in the process – but we can't identify the exact cause.

We’ve already:

Rescanned strings

Cleared transients and caches

Updated all WPML components

Could you please advise:

Whether these _load_textdomain_just_in_time notices are critical?

If our string tables might be bloated or corrupted?

Whether it’s best to disable automatic string scanning for some domains?

Thanks for your help!

Thank you for your response.

As requested, I’ve attached the current .htaccess file located in the root directory of my WordPress installation. Please note that there are two identical # BEGIN WordPress blocks and a few custom rewrite rules for /wp-login.php in different languages (EN, DE, IT).

I’ve left the file unchanged for now so you can review the actual setup before I make any modifications.

The internal server error still occurs intermittently across different language versions (including IT and EN), especially when working in the admin panel or saving translated pages.

Looking forward to your advice on how to proceed.

Best regards, Peter

Ht access:

# BEGIN WordPress
# Die Anweisungen (Zeilen) zwischen „BEGIN WordPress“ und „END WordPress“ sind
# dynamisch generiert und sollten nur über WordPress-Filter geändert werden.
# Alle Änderungen an den Anweisungen zwischen diesen Markierungen werden überschrieben.
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteRule ^en/wp-login.php /wp-login.php [QSA,L]
RewriteRule ^de/wp-login.php /wp-login.php [QSA,L]
RewriteRule ^it/wp-login.php /wp-login.php [QSA,L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

# BEGIN WordPress
# The directives (lines) between "BEGIN WordPress" and "END WordPress" are
# dynamically generated, and should only be modified via WordPress filters.
# Any changes to the directives between these markers will be overwritten.
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress
# BEGIN ShortPixelWebp
# Die Anweisungen (Zeilen) zwischen „BEGIN ShortPixelWebp“ und „END ShortPixelWebp“ sind
# dynamisch generiert und sollten nur über WordPress-Filter geändert werden.
# Alle Änderungen an den Anweisungen zwischen diesen Markierungen werden überschrieben.

# END ShortPixelWebp