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 – 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 6 days, 5 hours ago.

Assisted by: Andrey.

Author Posts
August 28, 2025 at 1:44 pm #17355121

sadhinE

Background of the issue:
I enabled automatic translation after the site went down. The English version is working fine, but I am getting an error when trying to access the Arabic version. English URL: hidden link Arabic URL: hidden link

Symptoms:
I am unable to access the Arabic version of the site, which results in an error.

Questions:
Could you please check and advise on the error when accessing the Arabic version?

August 28, 2025 at 2:45 pm #17355709

Andrey
WPML Supporter since 06/2013

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

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

Thank you for contacting WPML support.

The blank page means (or “500 error”) that there is an error in the PHP code that your site runs. When errors are not caught, the server stops everything and returns a page that says “500 error” or an empty page. Different servers are configured to display these errors slightly differently, but they all mean the same – there is an unhandled PHP error in the site’s code.

First, you need to identify the errors. Guessing what might be the problem and trying different solutions may lead to even more trouble. The first step is to enable debugging. You can add a few lines to the site’s wp-config.php file. With the error log enabled, you will see the actual problem.

To enable it, open your wp-config.php file and look for define('WP_DEBUG', false);. Change it to:

define('WP_DEBUG', true);

To enable the error logging to a file on the server, you need to add yet one more similar line:

define( 'WP_DEBUG_LOG', true );

The errors will be saved to a debug.log file inside the /wp-content/directory.

https://wpml.org/documentation/support/debugging-wpml/

Let me know what you see after the debug mode has been enabled.

August 28, 2025 at 2:53 pm #17355745

sadhinE

The Arabic version was working perfectly fine earlier without any issues. The error only started appearing after I enabled the automatic translation feature ON.

I will check the debug information in the meantime. If possible, please also review it from your side. I can share the credentials if required.

August 28, 2025 at 2:58 pm #17355754

sadhinE

Please see below the error message.

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the acf domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/u495886351/domains/demoserver.top/public_html/gharsschool/wp-includes/functions.php on line 6121

Debug Document URL: hidden link

Screenshot 2025-08-28 175547.png
August 28, 2025 at 7:29 pm #17356245

Andrey
WPML Supporter since 06/2013

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

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

Thank you for your feedback.

I can see the following fatal error which causes the issue:

PHP Fatal error:  Uncaught ValueError: Unknown format specifier "Ø" in /wp-content/plugins/bdevs-toolkit/inc/custom-post.php:110

I suspect that some bdevs-toolkit plugin-related strings containing placeholders, such as %s, might be incorrectly translated into Arabic. Specifically, the placeholder might have been translated as just “s” instead of keeping the correct %s format.

To verify this, please follow these steps:
1. Go to WPML → String Translation.
2. Filter by the bdevs-toolkit text domain.
3. Search for strings containing the %s placeholder.
4. Review the Arabic translations and ensure the %s placeholder is correctly preserved.

August 28, 2025 at 7:31 pm #17356251

sadhinE

Thank you for your response. I am checking as per your instructions. Kindly wait.

August 28, 2025 at 7:34 pm #17356255

sadhinE

Hi,
Please see the attached screenshot. Is it correct?

screencapture-gharsschool-demoserver-top-wp-admin-admin-php-2025-08-28-22_32_57.png
August 28, 2025 at 10:31 pm #17356419

sadhinE

I did not receive proper support or response from your side. I tried several workarounds, but the issue could not be resolved.

As a temporary solution, I restored the website to the state it was in before enabling WPML auto translation. After restoring the old backup, the site is now working fine.

August 29, 2025 at 8:22 am #17357067

Andrey
WPML Supporter since 06/2013

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

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

Thank you for your feedback.

Yes, your screenshot is correct. You need to review the strings that are already translated and make sure the %s placeholder is present and correct.

If the error occurs again, please double-check those strings. Should you need further assistance, feel free to let me know, or open a new support ticket if this one has already been closed.