Skip Navigation

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
- 8:00 – 10:00 8:00 – 10:00 8:00 – 13:00 8:00 – 13:00 9:00 – 13:00 -
- 11:00 – 17:00 11:00 – 17:00 14:00 – 17:00 13:00 – 17:00 13:00 – 18:00 -

Supporter timezone: America/New_York (GMT-04:00)

Tagged: 

This topic contains 1 replies, has 0 voices.

Last updated by Lauren 7 hours, 32 minutes ago.

Assisted by: Lauren.

Author Posts
July 10, 2025 at 2:45 pm #17224585

Patrick

Background of the issue:
I am trying to enable WP_DEBUG to improve my own plugins. Mine are fine.

Symptoms:
I expected to see no deprecated warnings coming from WPML on the admin panel. Instead, I got several deprecated warnings related to WPML components, such as:

Thank you for creating with WordPress.
Version 6.8.1

Deprecated: WPMLCoreComponentTranslationDomainLinksHandleUpdateTranslation::adjustOnlyOnce(): Implicitly marking parameter $triggerItem as nullable is deprecated, the explicit nullable type must be used instead in /blablabla/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/wpml/src/Core/Component/Translation/Domain/Links/HandleUpdateTranslation.php on line 75

Deprecated: WPMLLegacyComponentTranslationDomainLinksAdjustLinks::adjust(): Implicitly marking parameter $triggerItem as nullable is deprecated, the explicit nullable type must be used instead in /blablabla/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/wpml/src/Legacy/Component/Translation/Domain/Links/AdjustLinks.php on line 22

Deprecated: WPMLLegacyComponentTranslationDomainLinksAdjustLinks::adjustLinksInStringTranslations(): Implicitly marking parameter $triggerItem as nullable is deprecated, the explicit nullable type must be used instead in /blablabla/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/wpml/src/Legacy/Component/Translation/Domain/Links/AdjustLinks.php on line 76

Deprecated: WPMLLegacyComponentTranslationDomainLinksAdjustLinks::revertNameInTranslatedLinks(): Implicitly marking parameter $triggerItem as nullable is deprecated, the explicit nullable type must be used instead in /blablabla/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/wpml/src/Legacy/Component/Translation/Domain/Links/AdjustLinks.php on line 127

Deprecated: WPMLCoreComponentTranslationDomainLinksAdjustLinksInterface::adjust(): Implicitly marking parameter $triggerItem as nullable is deprecated, the explicit nullable type must be used instead in /blablabla/wp-content/plugins/sitepress-multilingual-cms/vendor/wpml/wpml/src/Core/Component/Translation/Domain/Links/AdjustLinksInterface.php on line 12

Questions:
Please update WPML to fix these. While production systems should not have WP_DEBUG enabled, it annoys us plugin developers who use WPML 🙂

July 10, 2025 at 3:24 pm #17224736

Lauren
WPML Supporter since 10/2015

Languages: English (English )

Timezone: America/New_York (GMT-04:00)

I have informed our developers of your findings and we will work to resolve the warnings in a future release. Thank you for getting in touch.