It's done and it seems to be an incompatibility as there are still THREE PROBLEMS:
1) Although the plugin string itself is translated (WPML confirms because everything is green), let's say the word "Your cart is empty." still remains in England.
2) Although the form is translated (WPML confirms because everything is green), the word "Other" still remains in English.
3) The Spanish version of the form still has the "broken blocks" problem.
I can replicate the issue on the sandbox site and see this. I'm asking our 2nd tier support about this issue and update you here when I have something to share.
Because this plugin is not available in our list of compatible plugins (https://wpml.org/plugin/), I also suggest you contact the plugin author and ask them to join our Go Global program where our Compatibility developers will help them to make their product compatible with WPML. https://wpml.org/documentation/support/go-global-program/
Regarding the third issue, we are using WPML translation editor to translate the form so I think it isn't necessary to edit the form in a second language manually.
Unfortunately, you are wrong about the conclusion for "manually editing the form", because there is a serious problem there.
In short, the WPML translation editor is not able to "pick up" all the content of the form, due to "broken blocks", and you can easily determine this by following the steps:
1) Edit the form with the WPML translation editor, and perform the translation.
2) You edit the form manually, and perform the recovery of each "broken block". A "hidden text content" (in English) will appear on the form itself and in the right admin menu of the form. That content does not appear in the plugin strings, nor in the WPML translation editor strings. Translate it manually, and you will see that the translated content will be "lost" again (because the blocks are "broken" again).
3) The "third" hidden content of the form (details about the debit card) is additionally "interesting" here because it cannot be edited in any way in order to be translated.
Thanks for your details. As I mentioned earlier, this plugin is not compatible with WPML so there are many issues there. I'm discussing this with our Compatibility team and I will update you here once I have any information.
Meanwhile, you can also contact SureCart support if they are aware of this issue.
But there are many forms that can have different structures. So it is important that the plugin author should create a file wpml-config.xml and add it to the plugin folder to translate all blocks of the plugin.
Also, they will need a custom implementation for strings that are not stored in blocks (or regular content).
Refer documentation https://wpml.org/documentation/support/language-configuration-files/#gutenberg-blocks
I recommend contacting the plugin author, reporting this issue and asking them to join our Go Global program where our Compatibility developers will help them to make their product compatible with WPML. https://wpml.org/documentation/support/go-global-program/
I would say that there are still problems there. Namely:
1) The Spanish version of the form in "manual edit mode" still shows "broken blocks".
2) Your custom XML has "picked up" some strings, but not all strings.
-> For example, "Your cart is empty.", "Email".
-> However, there is still a whole series of "hidden" strings. Let's say when one of the options is clicked (eg, it is like $50), new fields are "revealed" (displayed), which are still in English. For example, "Add Coupon Code", and "Recurring Donation". Untranslated English strings for the card (when the processor is connected) would definitely appear here as well.
QUESTIONS
1) Do Broken blocks affect the functionality of the Spanish version of the form or not?
2) Where are the above examples of untranslated strings (because they are not in the XML file)?
1. I do not have SureCart account and Payment Processor as the form required to make a test donation. Can you please help me to set it up and test it on the sandbox site? As I can see the translation strings in Advanced Translation Editor are displayed in Spanish as well.
2. As I mentioned above, those strings are not included in the form setup (Gutenberg block) SureCart > Forms > Donation. They are stored in the plugin files and even translated in String Translation, they are not displayed in the frontend.
For those strings, please contact the plugin author, report this issue and ask them for a custom implementation for strings that are scanned and translated with the gettext function __().
1) I reset all previous settings and reconnected to my new SureCart and Stripe accounts. For that reason, I deleted all other forms except the newly created two forms (one-time and recurring).
2) I translated all strings of the plugin and that's why I attached in previous reply image with the plugin string "Enter An Amount" as that string belongs to the plugin and not to forms. However, it is not successfully displayed on the Spanish page.
NOTE
In the previous reply, I attached other screenshots to display strings from the form that are not translated and displayed.
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
