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
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Europe/Kyiv (GMT+03:00)

Tagged: 

This topic contains 8 replies, has 0 voices.

Last updated by Andrey 2 days, 1 hour ago.

Assisted by: Andrey.

Author Posts
July 8, 2025 at 12:12 pm #17213556

annaT-22

Background of the issue:
I am trying to resolve errors in the debug.log that are exhausting my CPU resources on the website. The issue can be seen on the page: hidden link.

Symptoms:
I am encountering PHP warnings related to 'file_exists()' and 'realpath()' due to open_basedir restrictions. These errors are causing high CPU usage.

Questions:
How can I resolve the open_basedir restriction errors?
What steps can I take to reduce CPU usage caused by these errors?

July 8, 2025 at 12:30 pm #17213880

Andrey
WPML Supporter since 06/2013

Languages: English (English ) Russian (Русский )

Timezone: Europe/Kyiv (GMT+03:00)

Thank you for contacting WPML support.

I’ve reviewed the link you provided, but I didn’t notice any warnings on the page.

Could you please provide more details about why you believe this issue is related to WPML? If possible, share the exact warning message here in the support forum so we can better understand and assist you.

July 8, 2025 at 2:36 pm #17214724

annaT-22

Errors ar in debug.log file

[08-Jul-2025 14:34:57 UTC] PHP Warning: file_exists(): open_basedir restriction in effect. File(WP Endpoints-pl_PL.mo) is not within the allowed path(s): (/home/hcwqbgpzyu/domains/bmhorse.com/public_html:/tmp:/var/tmp:/opt/alt/php81/usr/share/pear/:/opt/alt/php72/usr/share/pear/:/opt/alt/php73/usr/share/pear/:/opt/alt/php53/usr/share/pear/:/opt/alt/php83/usr/share/pear/:/opt/alt/php82/usr/share/pear/:/opt/alt/php71/usr/share/pear/:/opt/alt/php70/usr/share/pear/:/opt/alt/php56/usr/share/pear/:/opt/alt/php74/usr/share/pear/:/opt/alt/php54/usr/share/pear/:/opt/alt/php55/usr/share/pear/:/opt/alt/php80/usr/share/pear/:/opt/alt/php84/usr/share/pear/:/dev/urandom:/var/www/html/waf/:/usr/share/GeoIP/:/usr/local/directadmin/plugins/waf/data/hcwqbgpzyu) in /home/hcwqbgpzyu/domains/bmhorse.com/public_html/wp-content/plugins/wpml-string-translation/classes/MO/Hooks/LoadTranslationFile.php on line 82
[08-Jul-2025 14:34:57 UTC] PHP Warning: file_exists(): open_basedir restriction in effect. File(WP Endpoints-pl_PL.l10n.php) is not within the allowed path(s): (/home/hcwqbgpzyu/domains/bmhorse.com/public_html:/tmp:/var/tmp:/opt/alt/php81/usr/share/pear/:/opt/alt/php72/usr/share/pear/:/opt/alt/php73/usr/share/pear/:/opt/alt/php53/usr/share/pear/:/opt/alt/php83/usr/share/pear/:/opt/alt/php82/usr/share/pear/:/opt/alt/php71/usr/share/pear/:/opt/alt/php70/usr/share/pear/:/opt/alt/php56/usr/share/pear/:/opt/alt/php74/usr/share/pear/:/opt/alt/php54/usr/share/pear/:/opt/alt/php55/usr/share/pear/:/opt/alt/php80/usr/share/pear/:/opt/alt/php84/usr/share/pear/:/dev/urandom:/var/www/html/waf/:/usr/share/GeoIP/:/usr/local/directadmin/plugins/waf/data/hcwqbgpzyu) in /home/hcwqbgpzyu/domains/bmhorse.com/public_html/wp-content/plugins/wpml-string-translation/classes/MO/Hooks/LoadTranslationFile.php on line 85
[08-Jul-2025 14:34:57 UTC] PHP Warning: realpath(): open_basedir restriction in effect. File(/usr/local/bin) is not within the allowed path(s): (/home/hcwqbgpzyu/domains/bmhorse.com/public_html:/tmp:/var/tmp:/opt/alt/php81/usr/share/pear/:/opt/alt/php72/usr/share/pear/:/opt/alt/php73/usr/share/pear/:/opt/alt/php53/usr/share/pear/:/opt/alt/php83/usr/share/pear/:/opt/alt/php82/usr/share/pear/:/opt/alt/php71/usr/share/pear/:/opt/alt/php70/usr/share/pear/:/opt/alt/php56/usr/share/pear/:/opt/alt/php74/usr/share/pear/:/opt/alt/php54/usr/share/pear/:/opt/alt/php55/usr/share/pear/:/opt/alt/php80/usr/share/pear/:/opt/alt/php84/usr/share/pear/:/dev/urandom:/var/www/html/waf/:/usr/share/GeoIP/:/usr/local/directadmin/plugins/waf/data/hcwqbgpzyu) in /home/hcwqbgpzyu/domains/bmhorse.com/public_html/wp-includes/l10n/class-wp-translation-controller.php on line 106

July 8, 2025 at 3:17 pm #17215144

Andrey
WPML Supporter since 06/2013

Languages: English (English ) Russian (Русский )

Timezone: Europe/Kyiv (GMT+03:00)

The issue should be resolved with WPML String Translation 3.2.18. Have you tried to clear logs, cache, and double-check the logs?

https://wpml.org/errata/php-warning-file_exists-open_basedir-restriction-in-effect-warning-possible-with-current-string-translation/

I would also suggest reactivating WPML plugins. Deactivate them and then reactivate them.

Before making any changes, please ensure that you back up your database first.

July 8, 2025 at 6:22 pm #17215871

annaT-22

I have String Translation 3.3.3,
Everything has been cleaned multiple times. I'll disable and re-enable the plugin, wait until tomorrow to see if it worked, and let you know.

July 9, 2025 at 6:18 am #17216862

annaT-22

didn't help

July 9, 2025 at 11:52 am #17219063

Andrey
WPML Supporter since 06/2013

Languages: English (English ) Russian (Русский )

Timezone: Europe/Kyiv (GMT+03:00)

Thank you for your feedback.

Based on the debug information, it appears that the REST API might not be enabled on your site. I also couldn’t access it directly. I noticed that the Disable WP REST API plugin is active in your installation — please review this setting, as it could be blocking essential functionality.

WPML relies on the REST API for several features. For example:

wpml/st/v1 – This endpoint is used to import and generate MO files, and to save String Translation settings. Disabling the REST API or the String Translation plugin may prevent these features from functioning correctly.
https://wpml.org/documentation/support/rest-api-dependencies/

The REST API being disabled may be contributing to the issue you’re experiencing.

If the problem persists, please try the following:
1. Temporarily disable all non-WPML plugins.
2. Ensure that the REST API is enabled.
3. Test this again with only WPML plugins active.

Before making any changes, please ensure that you back up your database first.

July 11, 2025 at 8:31 am #17226721

annaT-22

I uninstalled the Legacy REST API and disabled the REST API. I also deactivated and reactivated the WPML plugins, cleared the cache — but nothing worked :/

July 11, 2025 at 8:36 am #17226744

Andrey
WPML Supporter since 06/2013

Languages: English (English ) Russian (Русский )

Timezone: Europe/Kyiv (GMT+03:00)

I need to request temporary access (wp-admin and FTP) to your site—preferably to a test site where the problem has been replicated if possible—in order to be of better help. When you log in to leave your next reply, you will find the needed fields below the comment area. The information you will enter is private, meaning only you and I can see and access it.

Please include the exact steps to reproduce the issue.