Problem: The client has a multilingual site with English and Dutch languages. They noticed that while the content was translated by WPML, the URLs in the static HTML custom "menu" were not updated to point to the corresponding translated pages. The client wanted to know if there is a setting in WPML that automatically redirects users to the translated version of a page when they are on the Dutch homepage and click a link that has a Dutch translation available.
Solution: We informed the client that static HTML cannot be translated by WPML. Only PHP code that includes proper GetText calls can be translated within WordPress. Therefore, to achieve the desired functionality, the client would need to update the static HTML links manually to point to the correct translated pages. We also provided a guide on how to translate themes created by the client, which can be found here:
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also 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 contact us in the WPML support forum.
Problem: The client is experiencing issues when copying their Production environment to the Development environment on a multisite network hosted on WPEngine. After the copy, WPML detects a new address for the site and prompts a migration process. Despite completing the process, the client encounters the same message again, and the Production environment's connected site list grows with each attempt.
Solution: 1. If you're experiencing a similar issue after copying your Production environment to your Development environment, it's important to ensure that you're not forcing HTTPS or a specific domain in your wp-config or elsewhere in your installation. This could cause the site to be accessed with two domains, leading to the repeated migration banner. 2. Follow the instructions in our guide on Using Advanced Translation Editor when you move or use a copy of your site to resolve the issue. 3. Make sure to be using our latest WPML version (4.6.9 at the time of writing this summary).
Please note that the solution provided might be irrelevant if it's outdated or not applicable to your case. We highly recommend checking related known issues on the WPML Known Issues page, 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 with us.
Problem:
The client has a custom post type called "Transaction" with an Advanced Custom Field of type Radio Button with options Yes and No. When using automatic translation, if the radio button is not selected in the original item, WPML incorrectly selects "Yes" in the translated version, allowing it to bypass required fields. This causes issues as the site relies on the Yes/No selection to determine if further fields should be present.
Solution:
We recommend setting all your groups to "Same fields across languages" in "ACF > Field Groups" to use the default configuration for each field type. This usually meets most clients' needs, with text fields being translatable and checkbox fields being copied.
If you need to fine-tune the translation preferences, switch to "Expert" mode for a particular group. You can then see and change the translation preference for each field.
You can find the recommended preferences for each field type here: Recommended Custom Fields Translation Preferences for ACF and WPML
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.
당사는 웹사이트와 서비스를 최적화하기 위해 쿠키를 사용합니다.
사용자의 동의를 통해 탐색 행동과 같은 데이터를 처리할 수 있습니다.
동의하지 않으면 일부 기능에 영향을 미칠 수 있습니다.
기능적
항상 활성화
웹사이트가 올바르게 작동하고 통신하는 데 필요합니다.
기본 설정
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
통계
당사는 이를 사용하여 사이트의 통계를 분석합니다.
수집된 정보는 완전히 익명으로 처리됩니다. 익명 통계 목적으로만 사용되는 기술적 저장 또는 접근입니다. 소환장, 인터넷 서비스 제공자의 자발적인 협조 또는 제3자의 추가 기록 없이, 이 목적으로 저장되거나 검색된 정보는 일반적으로 귀하를 식별하는 데 사용할 수 없습니다.
