Skip to content Skip to sidebar

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- - 9:00 – 18:00 9:00 – 18:00 9:00 – 18:00 9:00 – 18:00 9:00 – 18:00
- - - - - - -

Supporter timezone: America/Lima (GMT-05:00)

This topic contains 2 replies, has 1 voice.

Last updated by Andreas W. 5 days, 19 hours ago.

Assisted by: Andreas W..

Author Posts
April 15, 2026 at 9:01 am #17970646

thomasD-100

(sitepress-multilingual-cms)
318 queries
2.18 seconds DB time

April 15, 2026 at 12:44 pm #17971407

thomasD-100

Checking with query monitor I see the following values:

(sitepress-multilingual-cms)
318 queries
2.18 seconds DB time

Is it possible to reduce the amount of queries?

Another issue:
clicking on "Theme and Plugins Localization" I get the following error:

When seeking help with this issue, you may be asked for some of the following information:
WordPress version 6.9.4
Active theme: Flatsome Child (version 3.0)
Current plugin: WPML String Translation (version 3.5.1)
PHP version 8.3.30

Uncaught Error: Unknown format specifier "t"
in /html/wordpress/wp-content/plugins/wpml-string-translation/classes/translations-file-scan/wpml-st-translations-file-registration.php on line 128

Call stack:

sprintf('https://cdn.wpml.org/html/wordpress/wp-c...l/%textdomain%-%s.mo', 'en_US')
wp-content/plugins/wpml-string-translation/classes/translations-file-scan/wpml-st-translations-file-registration.php:128
WPML_ST_Translations_File_Registration::save_file_info('%TEXTDOMAIN%', '%TEXTDOMAIN%', 'https://cdn.wpml.org/html/wordpress/wp-c...textdomain%-en_US.mo')
wp-content/plugins/wpml-string-translation/classes/translations-file-scan/wpml-st-translations-file-registration.php:87
WPML_ST_Translations_File_Registration::cached_save_mo_file_info(false, '%TEXTDOMAIN%', 'https://cdn.wpml.org/html/wordpress/wp-c...textdomain%-en_US.mo')
wp-includes/class-wp-hook.php:343
WP_Hook::apply_filters(false, array)
wp-includes/plugin.php:205
apply_filters('override_load_textdomain', false, '%TEXTDOMAIN%', 'https://cdn.wpml.org/html/wordpress/wp-c...textdomain%-en_US.mo', 'en_US')
wp-includes/l10n.php:769
load_textdomain('%TEXTDOMAIN%', 'https://cdn.wpml.org/html/wordpress/wp-c...textdomain%-en_US.mo', 'en_US')
wp-content/plugins/wpml-string-translation/classes/MO/JustInTime/MO.php:100
WPML\ST\MO\JustInTime\MO::WPML\ST\MO\JustInTime\{closure}('https://cdn.wpml.org/html/wordpress/wp-c...textdomain%-en_US.mo', 0)
wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/collect/src/Illuminate/Support/Collection.php:228
WPML\Collect\Support\Collection::each(Closure)
wp-content/plugins/wpml-string-translation/classes/MO/JustInTime/MO.php:96
WPML\ST\MO\JustInTime\MO::loadTextDomain()
wp-content/plugins/wpml-string-translation/classes/MO/JustInTime/MO.php:78
WPML\ST\MO\JustInTime\MO::load()
wp-content/plugins/wpml-string-translation/classes/MO/JustInTime/MO.php:50
WPML\ST\MO\JustInTime\MO::translate('License Key')
wp-includes/l10n.php:196
translate('License Key', '%TEXTDOMAIN%')
wp-includes/l10n.php:307
__('License Key', '%TEXTDOMAIN%')
wp-content/plugins/kadence-blocks/vendor/vendor-prefixed/stellarwp/uplink/src/Uplink/Admin/License_Field.php:84
KadenceWP\KadenceBlocks\StellarWP\Uplink\Admin\License_Field::register_settings()
wp-content/plugins/kadence-blocks/vendor/vendor-prefixed/stellarwp/uplink/src/Uplink/Admin/Provider.php:106
KadenceWP\KadenceBlocks\StellarWP\Uplink\Admin\Provider::admin_init()
wp-includes/class-wp-hook.php:339
WP_Hook::apply_filters(NULL, array)
wp-includes/class-wp-hook.php:365
WP_Hook::do_action(array)
wp-includes/plugin.php:522
do_action('admin_init')
wp-admin/admin.php:180

April 16, 2026 at 8:51 am #17973411

Andreas W.
WPML Supporter since 12/2018

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

Hello,

Thank you for reaching out!

For the error:

Please go to WPML > String Translation.

Use the text search to locate the problematic string names %TEXTDOMAIN%.

Then either adjust its translation so it is identical to the original, or delete the string completely.

For the queries:
Please take a backup of your site and provide me with more details about the involved queries. You can use the Query Monitor Plugin for this purpose.

Best regards
Andreas