Skip Navigation

This thread is resolved. Here is a description of the problem and solution.

Problem:
You are experiencing a fatal error when switching your WordPress site to a second language (Arabic) using Elementor and WPML. The error message displayed is:

Fatal error: Uncaught ValueError: Unknown format specifier "�"

. Additionally, the automatic translation feature in WPML isn't functioning as expected.
Solution:
We resolved the fatal error by correcting a string translation issue. Here are the steps we followed:
1. In WPML -> Strings Translation, search for 'New %s'.
2. Ensure that the placeholder '%s' is translated correctly. In this case, it should be translated to 'جديد %s' for Arabic.
This adjustment fixed the fatal error related to the language switch. For the layout issues in the Products tab, we corrected all strings containing '%s' in the Dokan domain within WPML -> Strings Translation.

If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If problems persist, please open a new support ticket.

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.

Tagged: 

This topic contains 9 replies, has 0 voices.

Last updated by yousefifardH 3 days, 7 hours ago.

Assisted by: Itamar.

Author Posts
April 21, 2025 at 7:20 am #16950871

Itamar
WPML Supporter since 02/2016

Languages: English (English ) Hebrew (עברית )

Timezone: Asia/Jerusalem (GMT+03:00)

Hi,

Our second-tier supporter has debugged this issue and reported that the following proceedure should fix this problem on your site.

1. Backup the DataBase of your site in case something goes wrong.

2. Go to WPML → Support → Troubleshooting.

3. Click the button labeled 'Remove ghost entries from the translation tables'.

This will clean up any unnecessary entries from the translation queue.

**** Important! Please make DB backup before you proceed with those steps****

Please let me know how it goes.

Thanks,
Itamar.

April 21, 2025 at 4:46 pm #16952427
yousefifardH

Dear Itamar,

The issue with translations not working was resolved by using the "Remove ghost entries from the translation tables" option. I hope this issue is fully resolved now and doesn’t happen again, because the first time this happened, the translation was completed successfully, and the translated page loaded perfectly without any issues. But after a few minutes, these problems occurred—the fatal error appeared, and translations stopped working. However, after translating and working on the pages this time, the fatal error returned again. I followed your previous advice and searched for the string "New %s" in WPML > String Translation to check the translations, but they seemed fine. I suspect another string might be causing this issue now, but I’m not sure how to find it. Could you please guide me on how to identify the problematic string?

Additionally, after translating the content, the Elementor page is now aligned to the right and lacks balance (as I mentioned earlier). Is there something I need to activate to fix this?

I’m also attaching the debug log for your reference:
text
[21-Apr-2025 16:10:08 UTC] PHP Fatal error: Uncaught ValueError: Unknown format specifier "Ø" in /home/coi7xq4ukqn0/public_html/wp-content/plugins/elementor/core/document-types/page-base.php:181

Looking forward to your assistance!

New threads created by Itamar and linked to this one are listed below:

https://wpml.org/forums/topic/split-the-elementor-page-is-now-aligned-to-the-right-and-lacks-balance/

Screenshot 2025-04-21 163055.png
Screenshot 2025-04-21 162450.png
April 22, 2025 at 4:41 pm #16956656

Itamar
WPML Supporter since 02/2016

Languages: English (English ) Hebrew (עברית )

Timezone: Asia/Jerusalem (GMT+03:00)

Hi,

I fixed the fatal error on the Arabic page. This time it was another string. It was: All %s and it was incorrectly translated as follows: الكل %س. Please see the attached screenshot. So I translated it like this: جميع %s.

I reported this to our second-tier supporters and developers.
We will update on any news regarding this issue.

About the Elementor page, which is aligned to the right and lacks a balance issue, I split this ticket, and we will handle this issue in the new ticket here.

https://wpml.org/forums/topic/split-the-elementor-page-is-now-aligned-to-the-right-and-lacks-balance/

Regards,
Itamar.

April 30, 2025 at 2:44 pm #16984576

yousefifardH

Dear Itamar,

I’ve encountered another fatal error related to translations, similar to the previous issues. Here are the details from the debug log:
text
[30-Apr-2025 14:16:58 UTC] PHP Fatal error: Uncaught ValueError: Unknown format specifier ")" in /home/coi7xq4ukqn0/public_html/wp-content/plugins/dokan-lite/templates/products/listing-status-filter.php:23

It seems that a translation string in the Dokan plugin (likely for the Arabic language) has an incorrect format specifier, where %s or another placeholder has been replaced with ). I tried searching for the ) character in WPML > String Translation under the dokan domain, but I couldn’t find the problematic string. Could you please help me identify which string is causing this error and how to fix it?

I’ve attached a screenshot of the page where the error occurs (the Dokan vendor dashboard in Arabic).

Looking forward to your assistance!

Screenshot 2025-04-30 181351.png
Screenshot 2025-04-30 180305.png
May 3, 2025 at 10:13 am #16991688

yousefifardH

Dear Itamar,

I’ve encountered a new fatal error related to translations. I’m still waiting for a response on the earlier issue I reported in the previous ticket, and I’d like you to review this new problem alongside it. Here are the details from the debug log:

New error:
[03-May-2025 10:05:57 UTC] PHP Fatal error: Uncaught ValueError: Unknown format specifier " " in /home/coi7xq4ukqn0/public_html/wp-content/plugins/dokan-lite/templates/settings/store-form.php:84

Screenshot 2025-05-03 075132.png
Screenshot 2025-05-03 074509.png
May 4, 2025 at 2:45 pm #16993351

Itamar
WPML Supporter since 02/2016

Languages: English (English ) Hebrew (עברית )

Timezone: Asia/Jerusalem (GMT+03:00)

Hi,

I'm sorry that this problem occurred again.

I could find those strings. They come from the Dokan Lite plugin. So I did the following:

1. In hidden link I scanned the Dokan Lite plugin for strings.

2. Then, in String Translation, I could translate them correctly. Please see the attached screenshot (for the second error).

I reported this to our second-tier supporter. I asked to implement a workaround that hopefully would stop this from happening.

I'll update you here when I have news.

Regards,
Itamar.

May 4, 2025 at 4:52 pm #16993575

yousefifardH

Dear Itamar,

Thank you for resolving the previous issues. However, I’ve encountered another fatal error related to translations in the Dokan plugin. Here are the details from the debug

log:
[04-May-2025 16:41:08 UTC] PHP Fatal error: Uncaught ValueError: Unknown format specifier ")" in /home/coi7xq4ukqn0/public_html/wp-content/plugins/dokan-pro/templates/products/edit/bulk-edit-form.php:72

I’ve tried searching for the problematic string in WPML > String Translation, but I couldn’t find it. Could you please help identify which string is causing this error and fix it?

Screenshot 2025-05-04 200333.png
Screenshot 2025-05-04 200230.png
May 5, 2025 at 6:50 am #16994548

Itamar
WPML Supporter since 02/2016

Languages: English (English ) Hebrew (עברית )

Timezone: Asia/Jerusalem (GMT+03:00)

Hi,

I also fixed this issue on your site. Please let me know if it is OK now.

While fixing it, I recorded a video demonstrating what needs to be done. In short, you need to find the file and the line mentioned in the error message, and there you will see the string with the problem. Then, in WPML -> Strings Translation, you can fix this string. Please watch my video here.

hidden link

Regards,
Itamar.

May 5, 2025 at 7:29 am #16994767

Itamar
WPML Supporter since 02/2016

Languages: English (English ) Hebrew (עברית )

Timezone: Asia/Jerusalem (GMT+03:00)

Hi,

In addition to my last reply, our second-tier supporter also informed me that he applied a workaround from our side. So please check and tell me if the problem persists.

Regards,
Itamar.

May 5, 2025 at 7:44 am #16994860

yousefifardH

Dear Itamar,

Thank you for the update. I’ve checked the issue after the workaround applied by your second-tier supporter, but the problem still persists. The fatal error remains:

Screenshot 2025-05-05 111233.png
Screenshot 2025-05-05 111152.png
May 5, 2025 at 10:23 am #16995639

Itamar
WPML Supporter since 02/2016

Languages: English (English ) Hebrew (עברית )

Timezone: Asia/Jerusalem (GMT+03:00)

Hi,

Can you please send me the link to the page with this problem?

Thanks,
Itamar.

May 5, 2025 at 11:52 am #16995997

yousefifardH

hidden link

May 6, 2025 at 6:23 am #16999195

Itamar
WPML Supporter since 02/2016

Languages: English (English ) Hebrew (עברית )

Timezone: Asia/Jerusalem (GMT+03:00)

Hi,

I also fixed this string.
Please see the attached screenshot.

Regards,
Itamar.

2025-05-06_09-22-05.jpg
May 6, 2025 at 7:01 am #16999387

yousefifardH

Thank you for fixing the string and sharing the screenshot. However, I’ve checked the issue, and the problem still persists. The page appearance is still broken, and the fatal error remains:

[06-May-2025 06:47:26 UTC] PHP Fatal error: Uncaught ValueError: Unknown format specifier ")" in /home/coi7xq4ukqn0/public_html/wp-content/plugins/dokan-pro/templates/products/edit/bulk-edit-form.php:155

Please check the previous link again:

hidden link

Screenshot 2025-05-06 062831.png
Screenshot 2025-05-06 062428.png
May 6, 2025 at 7:23 am #16999489

Itamar
WPML Supporter since 02/2016

Languages: English (English ) Hebrew (עברית )

Timezone: Asia/Jerusalem (GMT+03:00)

Hi,

Can you please tell me the steps to trigger the error?
In other words, what do I need to do to make the error happen?

Thanks,
Itamar.