Problem: The client is experiencing issues with managing WPML credits across a multisite environment on WPEngine, which includes a main site and a child site, as well as staging and development environments. The client is unsure about the correct workflow for handling WPML credits when copying from production to staging and development environments.
Solution: 1. We requested the client to provide the full addresses of the domains currently available under their wpml.org account, including the protocol and whether they include WWW. 2. After receiving the necessary information, we cleaned up all previous instances of the client's sites, including duplicates and old domains. 3. We then linked all 6 URLs together to ensure that all credits and content are linked, preventing the creation of new instances. 4. We advised the client that no specific workflow is needed when moving sites between different environments, as long as the URLs remain linked.
Problem: The client is experiencing a layout issue on the 'Appearance > Menus' admin page while following the WPML documentation for translating menus manually.
Solution: We recommend updating the WPML Multilingual CMS to the latest version, as the layout issue has been resolved in the update. Before updating, ensure to create a full backup of the website. If the layout issue persists after updating, or if this solution does not seem relevant to your situation, please open a new support ticket with us.
Problem: The client is inquiring whether translations made on the main site of a WordPress multisite environment will automatically apply to the child sites, specifically for the 'Manage Consent' button of the CookieYes GDPR plugin. Solution: We explained that in a multisite setup, WPML treats each site individually. Therefore, translations made on the main site will not be copied to the child sites. The client will need to translate the strings individually on each of the subsites. If this solution doesn't seem relevant, we recommend opening a new support ticket for further assistance. You can do so by visiting the WPML support forum.
Problem: Unable to translate acf checkboxes labels.
Solution: 1. Navigate to ACF->Tools and enable the option 'Scan local fields for changes to translation preferences.' and save the changes. 2. Go to WPML->Strings Translations->Auto Register strings for translations and enable the 'Look for strings while pages are rendered' option. 3. Visit the page on the front-end where the string is shown to automatically register strings from that page. 4. Return to WPML->Strings Translations->Auto Register strings for translations and disable the previously enabled options. 5. Search for the strings in WPML->String Translations and translate all instances that appear.
Problem: The client is trying to translate the labels of an ACF Checkbox field in a multisite environment. The ACF field groups live in the main site and should get translated to a child site in the multisite network. Solution: We clarified that connecting two different sites within a multisite network using WPML is not possible, as each site in a multisite has its own WPML settings and operates independently. Therefore, the client cannot use the main site's ACF field set translations on a child site.
Documentation for Multisites running WPML: https://wpml.org/documentation/support/multisite-support/ If this solution does not seem relevant to your issue, please open a new support ticket with us.
Problem: The client wants the review banner that appears at the top of a translated page to remain in the original language (English) instead of being translated into the review language.
Solution: We have consulted with our second-tier support team and confirmed that the box is designed to appear in the review language, which is the language the page has been translated into. Unfortunately, there is no setting or workaround available to display this box in the default language (English) instead of the review language.
