This thread is resolved. Here is a description of the problem and solution.
Problem: The client is experiencing frequent fatal errors due to an ArgumentCountError in the WPML String Translation plugin. Additionally, there are issues with the automatic translation of the homepage into Bulgarian using DeepL, where certain sections like the video title, footer, and contact form are not displayed correctly.
Solution: For the fatal error, it appears to be a bug related to the sprintf function in the WPML String Translation plugin, which misinterprets URL-encoded characters as formatting placeholders. We recommend creating a staging copy of the site and providing access to our support team for further investigation and to potentially escalate the issue.
Regarding the homepage translation issues, these are likely due to the ACF configuration. The homepage must be translated manually using the WordPress Editor, not via the Translation Editor, due to the ACF configuration settings. Specific steps include translating the footer menu and contact forms as outlined in our guides (Translating Menus and Using Contact Form 7 with WPML). Additionally, ensure all images and logos are set to copy for the slider to function correctly in the translated version.
If these solutions do not resolve the issues or if they seem outdated or irrelevant to your case, please open a new support ticket. We highly recommend checking related known issues (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. For further assistance, visit our support forum at WPML Support Forum.
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.
I'm getting this kind of error frequently, can you please investingate. I have already updated all the plugins and themes and core files. still getting the error.
What caused the issue?
In /wp-content/plugins/wpml-string-translation/classes/translations-file-scan/wpml-st-translations-file-registration.php around line 128, WPML uses the sprintf function to inject the language locale (like en_US) into a translation file path.
If the file path it is scanning happens to naturally contain % symbols (e.g., %20 for spaces or other URL-encoded characters), sprintf mistakenly interprets these as formatting placeholders that require arguments. Since the path being scanned had 65 % characters and sprintf was only provided with 1 argument (the locale), it threw an ArgumentCountError: 66 arguments are required, 2 given and crashed your site.
--> it would be great if you fix the issue from the plugin and release the patch officially. thanks.
I agree that this looks like a possible bug in our code. However, before I can escalate it to our 2nd-tier support team, we need to reproduce the issue and document the exact steps.
Could you please do the following?
1.- Create a staging copy of the live site and share temporary WordPress admin and FTP/SFTP access in your next reply. I have enabled the private reply fields for this.
Alternatively, you can share access to the live site and explicitly authorize us to create a copy for debugging.
2.- Please describe the exact step-by-step process to trigger the error on the site.
Apologies for the late reply. Let’s leave that issue for now, as I currently have another priority issue.
Could you please check the Bulgarian version of the homepage: hidden link
I used DeepL auto-translation for the homepage content in Bulgarian, but some sections are not being translated or displayed correctly. For example:
* Video section title and description are missing
* Footer area is empty
* Contact form is not showing
* Some other content is still untranslated
Could you please check why the entire page translation is not appearing properly?
Site should not go down, please take care of it.
[REMOVED]
so when WPML >> Translation Dashboard >> Pages >> select Home >> and translate the page using credits. it translate successfully but some pasrt are missing.
To translate the homepage, you have to use the WordPress Editor (manual translation) due to the ACF configuration. In this link, you can translate/update the translation of the Bulgarian version: hidden link
Note: I had to remove the credentials you shared because they were publicly accessible.
Before I have only two language but now I want 10+ language to translate so it will take too much time to manually translate.
what should I do if I want to translate homepage auto using DeepL?
Also please check the (ACF > Field Groups), around 86 Field Groups, and almost every group is duplicated 2 or 3 times (e.g., three copies of "Article Single", three copies of "Case Studies", three copies of "About Us").
I kindly ask you to focus on solving one issue. As per the support forum's policies, we can only solve one issue per ticket; new issues will require me to split the tickets to handle them individually.
To answer your latest question: I don't know exactly what steps you followed to set up the ACF groups, but the behavior you are describing corresponds to changing the ACF Group custom post type from translatable to non-translatable in WPML -> Settings -> Post type translations.
Previously, I was using manual translation, but now I want to use auto-translation. The problem is that it’s still not translating properly. Please provide the best approach for handling translations so I can translate pages efficiently into 10+ languages.
In each message, you have asked different questions, and I explained that we can only solve one issue per ticket. I kindly ask you again to focus on only one issue that we can solve in this ticket, and then we can move on with the other issues or questions you may have.
Your latest message seems to be related to another problem, or lacks context to understand precisely what is the section you are referring to.
Could you please read the messages in this ticket and elaborate more on your latest message so I can have a better understanding? What section are you referring to? What technical explanation are you looking for?
Could you please check the Bulgarian version of the homepage: hidden link
I used DeepL auto-translation for the homepage content in Bulgarian, but some sections are not being translated or displayed correctly. For example:
* Video section title and description are missing -
German Page: hidden link
Bugarian Page missing: hidden link
* Footer area is missing some menus -
German Page Footer: hidden link
Bulgarian Page Footer: hidden link
* Contact form is not showing:
German Contact Form: hidden link
Bulgarian Page missing Contact form: hidden link
* Slider section above the footer in German: hidden link
* Slider section above the footer in Bulgarian is missing: hidden link
Could you please check why the entire page translation is not appearing properly?
so when WPML >> Translation Dashboard >> Pages >> select Home >> and translate the page using credits. it translate successfully but some pasrt are missing.
German Homepage: hidden link
Bulgarian Homepage: hidden link
1.- When editing the homepage in German (default language), I can't find the section missing on the Bulgarian version, the one starting with "Für ein großes Bauteilspektrum: Zwölf Modelle".
Can you tell me where I can edit that content in German?
2.- You can translate the footer menu into these links:
- hidden link
- hidden link
- hidden link
- hidden link
Let me know if you find any issues with these steps.
3.- To translate and show the contact forms created with Contact Form 7, you need to:
- Go to WPML -> Translation Dashboard -> Contact Forms section -> Select and translate the form
- Then you need to edit the homepage in the secondary language (for example, in Bulgarian: hidden link) -> Paste the contact form shortcode in their respective fields
4.- There is a JavaScript error in the console when visiting the Bulgarian version of the homepage that seems to be related to the slider. The first step is to set all the logos and image files to copy (I tried to set most of them) and make sure the Bulgarian version contains the images so the slider can work correctly.
If you continue seeing this issue after the steps mentioned above, then we will take a look at this separately.
Summarizing: Yes, some parts of the translated homepage are missing because they are set to be non-translatable or copy-once. Also, the homepage must be translated manually, not via the Translation Editor. When you edit the homepage in German: hidden link, you will find an alert message at the top that reads: "You need to translate this post manually because the field groups attached to it use different translation options." and it is because of the ACF configuration.
