Home›Support›English Support›[Resolved] Advanced Product Fields Pro for WooCommerce Dependencies not working
[Resolved] Advanced Product Fields Pro for WooCommerce Dependencies not working
This thread is resolved. Here is a description of the problem and solution.
Problem: If you're experiencing issues with conditions being stripped from HTML code during translation in WPML, specifically with the '==' and '!=' conditions in Advanced Product Fields Pro for WooCommerce, this might be due to limitations in the Advanced Translation Editor (ATE).
Solution: We recommend switching to the Classic Translation Editor for cases where specific conditions like 'equal' are not appearing correctly in ATE. Here’s how you can do it: 1. Navigate to WPML > Settings and switch to the Classic Translation Editor. 2. When translating a product, use the 'Copy all fields from original' option, then manually translate text fields while leaving rule-based fields unchanged. 3. Manually add the 'Equal' condition in the translated product to ensure it functions correctly. 4. If using ATE and encountering issues with automatic translations, you will need to manually update the condition rule for 'equal' in the translation. 5. For issues like the required field marker appearing incorrectly, manually save the translated product to ensure that changes propagate correctly.
If these steps do not resolve your issue or if the solution 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 further assistance is needed, please open a new support ticket 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.
Background of the issue:
We use Advanced Product Fields Pro for WooCommerce and WPML translates it well. However, when we use dependencies in the product fields, some conditions seem to be stripped away during the translation process. For one product, we have a product option which is hidden and is only displayed if the option value of another product option is set to a specific value. The condition works if it tests for 'any value' or 'empty' but it doesn't work if tested for 'equal' or 'not equal'. In the HTML code of the translated page it can be seen, that the values '==' and '!=' are stripped from the code which leads to this error.
Symptoms:
Dependencies in product fields are not working correctly after translation. Specifically, conditions using '==' and '!=' are stripped from the HTML code of the translated page.
Questions:
Why are the '==' and '!=' conditions being stripped from the HTML code during translation?
How can we ensure that these conditions are preserved in the translated product fields?
Hello There,
Thanks for contacting WPML Support. Sorry for the delay in responding due to the weekend.
I understand the issue you're facing. It appears that the translation preference for the field where you're setting the condition is not configured correctly, which is why the condition is not being copied to the translation.
If you can identify the field name in the product editor that is storing the condition (by inspecting the field), you can set the translation preference for that field to "Copy" by navigating to "WPML > Settings > Custom Field Translation." If the field isn't visible in the results, click on the "Show System Fields" link below the Custom Field Translation section and then search for the field again.
Please let me know if that helps or if you need any further assistance or clarification. I'll be happy to help.
So this is the content of the field _wapf_fieldgroup.
I contains both conditions and text which needs to be translated.
If we set the field to "translate", certain conditions are stripped away, like "==" and "generated", probably due to security reasons.
If we set the field to "copy", it is not translated.
If we could somehow translate manually after it is copied, we would need to recreate all conditions in target languages if we changed those in the original language.
So the best solution for us would be to somehow whitelist this field or set allowed field contents so that parts are not stripped.
If the field is set to "Copy," could you please verify whether the text content within that field can be translated via WPML > String Translation? If the translation is possible, kindly check the frontend after translating to ensure that the translated content is displayed correctly and that the conditions are working as expected.
If it still doesn't work after that, I kindly request you to try replicating the issue on our sandbox site. The autologin link to our sandbox is given below.
- hidden link
WooCommerce, WPML, and their addons are already installed in the sandbox. Please complete the initial setup first. After that, install the Advanced Product Fields plugin, create a product, and configure it exactly as you have on your main site. Then, check if you can replicate the issue.
If you're able to replicate the issue, please let me know the steps in your next response. I will review them and let you know the next steps.
The sandbox environment is useful for isolating an issue in a minimal setup. If the issue persists there, we can easily escalate it to our 2nd tier team for further investigation. So, please give it a try and update me on the results. I will be happy to help further.
Unfortunately I cannot find the text to be translated in WPML > String Translation.
I have rebuilt the issue in the test store.
Here is the product in the original language: hidden link
If you select "S" for "Größe", another option will be displayed below. If you select "M", "L" or "XL", the other option will be hidden. This is the intended behavior.
Here is the translated product: hidden link
As you can see, the option does not behave in the same way. If you select "S" for size, the other option will not be displayed.
If you check the source code of the translated page, you can see that the condition value of "==" has been removed (search for wapf[field_66cd78f512e78] and check the data-dependencies attribute which contains the field "condition").
Hello Rico,
Thank you for trying to replicate the issue on the sandbox.
I checked and noticed that only the equal condition (==) does not appear in the Advanced Translation Editor, while other conditions like "Empty" or "Not Empty" display correctly. Additionally, the Size element also appears correctly in the Translation Editor.
The ATE has a known limitation with displaying certain symbols and punctuation marks. To work around this, you can set the condition in the translation by following these steps:
- Edit the translated product and manually add the condition. Simply select the "Equal" condition without making any other changes. I tested this in a sandbox environment and can confirm that everything works properly, including the translation.
- Switch to the Classic Translation Editor by navigating to "WPML > Settings" and then try to translate the product. In this editor, the equal sign appears correctly for translation. You can see an example in this screenshot: hidden link. Just copy the value of the condition fields into the translation and then proceed to translate the rest of the content. This approach ensures that the condition functions properly in the translation.
I hope you can understand. Please try and let me know how it goes. If you need further assistance or clarification, feel free to let me know. I'll be happy to help.
Unfortunately it seems there are still some issues.
1) When we use the Classic Translation Editor we cannot use the automatic translation, right? That is very inconvenient. Can we just use the Classic Editor on a case-by-case basis, like only on products with custom options?
2) When I translate a new product using the Classic Editor, I click on "Copy all fields from original" and afterwards manually translate all text fields and just leave the rules based fields as they are.
But this leads to a strange behaviour.
Please check this test product: hidden link
In the original language I set the fields to "required" but also set the option to not show that they are required (the "*" should not be shown).
This seems to correspond to the field-_wapf_fieldgroup-2-mark_required set to false as can be seen in the translation editor. This field is set to "false" both in the original and in the translation.
However, in the translation the field is marked by "*" while in the original it is not. Please check the attached screenshots.
There are even some more of this kind of issues when we use the Classic Translation Editor in our store, this is just one example.
We could low level hack this problem by not translating some custom fields but we had to remember which ones and for non-coders this is not a valid solution.
This is a new problem with the Classic Translation Editor, it doesn't occur when we use the Advanced Translation Editor.
Yes, indeed, automatic translation cannot be used with the Classic Translation Editor; it only works with the Advanced Translation Editor. If you prefer to translate content automatically, you'll need to keep the Advanced Translation Editor enabled. However, in that case, you'll need to manually update the condition rule (only the equal condition) in the translation.
Regarding the required field marker issue, I checked the translated product from the editor and, upon inspecting the button that shows/hides the required marker, I found that the value to keep the marker hidden was added correctly to the button. However, for some reason, the button remained active. Please check the attached screenshot. It seems the button value doesn’t get updated correctly until the user interacts with it.
However, when I manually saved the translated product, the value propagated correctly to the button, and the required marker no longer appeared on the frontend. For your information, I saved the translated product without making any changes.
If you prefer to continue using the Classic Translation Editor, you may need to manually save the product to ensure that the changes propagate correctly. If you choose to use the Advanced Translation Editor, you'll need to update the condition rule in the translated product manually. Given the limitations of ATE, this is the only way to ensure that the product field functions correctly in translation.
Additionally, you also have the option to completely manually update advanced product field data in the translation. To do this, set the "_wapf_fieldgroup" to 'Copy-Once'. Then, make a small change to the default product and update its translation. The default data will be copied to the translated product and you can then manually update the data in the translated product as needed.
I hope you can understand. Please feel free to let me know if you have any other questions or need clarification. I will be happy to help.
