Custom Work

Problem:
The client is using WPML's translation management to translate their site into French using UABB and Powerpack modules for Beaver Builder. The automatic translation does not work with the content of the UABB module, specifically the Powerpack restaurant module nested within it.
Solution:
The client discovered a workaround for the issue with the UABB module's content not translating automatically. Although the specific steps were not detailed in the communication, the client confirmed that they found a method to enable translation for the Powerpack restaurant module within the UABB module. We recommend checking the client's shared video for a visual guide on the solution: https://www.loom.com/share/8ab3aef2214a4e6c87ab4fd547851b41.

Please note that this solution might be outdated or not applicable to your specific 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 the issue persists, please open a new support ticket at WPML support forum for further assistance.

Problem:
The client is using ACF multilingual with WPML, and they encountered an issue where an image URL in a product category displays correctly in English, but when switching languages, the array containing the image URL becomes just a category ID in the translations.
Solution:
We recommended verifying the method used to call the field, suggesting the use of the approach detailed in the ACF documentation on image fields: https://www.advancedcustomfields.com/resources/image/#customized-display-array. Additionally, we provided a test site for the client to replicate the issue and further investigate the behavior of the image fields in a controlled environment. If the problem persists, we advised the client to adjust their code to check if the image field returns an ID and, if so, convert it to a URL using

.

Please note that this solution might be outdated or not applicable to your specific 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 the issue persists, please open a new support ticket at WPML support forum for further assistance.

Problem:
The client is experiencing an issue with WPML Media Translation where the 'Save media translation' button remains inactive, and despite adding Name, Caption, and Alt text to a different file, the translated image does not appear, but the English image does.
Solution:
We recommend using the

function to ensure that the media ID is correctly translated, which should resolve the issue with the inactive button and the incorrect display of images. Here is a step-by-step guide:
1. Retrieve the original media ID and URL.
2. Use the

function to get the translated media ID.
3. If the original media ID does not match the translated media ID, update the media URL and ID to the translated ones.
4. Verify that the translated media appears correctly in place of the English image.

If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable 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 the problem persists, please open a new support ticket at WPML support forum for further assistance.

Problem:
The client developed custom SiteOrigin widgets on a custom theme and configured the wpml-config.xml to translate widget content. However, the custom widget content is not translating, even though the page content is.
Solution:
We recommend updating your wpml-config.xml with the following XML code to make your widget compatible with WPML:

You can use the following repository as a guide for your other widget compatibility codes:

• SiteOrigin Widgets Bundle GitHub

Please note that this is considered a custom code request and is outside of our support scope. We did our best to show how it is done for one widget but we will not be able to provide code for other widgets. You are welcome to use the resources provided in the reply to find the correct code.

If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, we highly recommend checking related known issues at WPML 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.