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.
Problem:
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 resolve this issue? Solution:
The client reported how he solved the issue:
I’ve identified and resolved the alignment issue with the Arabic page. The problem was that the page designed with Elementor, when translated to Arabic, doesn’t automatically apply the same settings as the English page by default. I manually adjusted the settings for the Arabic page, and the issue was resolved. Here are the changes I made:
In the English page, the sidebar was set to "none," but the Arabic page had a sidebar enabled. When I removed the sidebar from the Arabic page, the alignment issue was fixed.
Additionally, the header in the Arabic page was not set correctly. I selected the custom header from the main page (English version), and that resolved the header issue as well.
