Problem: The client is experiencing an issue where switching between the profile and the main page results in being taken to different language versions of the site. Specifically, navigating from the Ukrainian or Russian version to the main page redirects to the English version instead of staying on the same language. Solution: 1. We found that the menu links for the profile were not translated. To resolve this, we recommend creating a Custom Link in the menu for the profile page in each language. This can be done by visiting the profile in each language, copying the page URL, and then adding it as a Custom Link in your menu. 2. If clicking the profile icon redirects to the profile in the default language, this is due to the theme generating the link dynamically based on the user's session. This behavior is not translatable by WPML and would need to be addressed by the Theme Author.
Problem: The client was experiencing an issue where the Members Directory was not properly displaying members in different languages. Specifically, the Member Type for some members was not specified, and students and instructors were not shown at all in Ukrainian and Russian. The issue was related to the API interactions with the "VibeBP" plugin, where the 'member_type' property in the API payload was not reflecting the translated term in languages other than the default.
Solution: We took the following steps to resolve the issue: 1. We navigated to WPML > Settings > Taxonomies Translation and set the translation preference for "Member Types (bp_member_type)" to "Not Translatable." 2. We then removed the Translated Member Types by going to Users > Member Types, keeping only the default ones. These adjustments ensured that all users were assigned the default member types, and the filter began to work properly in each language.
If this solution does not seem relevant to your situation, please do not hesitate to open a new support ticket with us.
Problem: The client is experiencing an issue where a notice does not disappear even after following suggested actions, and the WPML plugin is unable to register due to a 'Site key not matching' warning. Solution: If you're experiencing a persistent notice and issues with WPML registration, we recommend you first try to force a connection to wpml.org by going to Plugins > Add New > Commercial tab and clicking on the "Check for updates" button. If there are no errors and the notice persists, consider it a false positive. Additionally, ensure that WPML URLs are whitelisted in your firewall by checking our troubleshooting registration documentation.
If the issue is related to 'Site key not matching' warnings, follow these steps after ensuring you have a full site backup (mandatory): 1. Visit your account page at https://wpml.org/account/sites/ and delete the key for the site. 2. Navigate to Plugins > Add New > Commercial tab. 3. Click on "Unregister WPML from this site". 4. Refresh the page. 5. Click on "Get a key for this site" and copy the newly generated code. 6. Return to the Plugins > Add New > Commercial tab and register the site with the new key.
