Problem: The client is trying to always retrieve the English slug names of a taxonomy for CSS purposes in different languages using the WPML plugin. They are using the
wpml_get_translated_slug
filter but are encountering issues where the slug is not consistently returned in English across different language settings. Solution: We advised the client to ensure they are using the correct parameters with the
wpml_get_translated_slug
filter. For retrieving the English version of a taxonomy slug, the code should look like this:
Additionally, we suggested checking the WPML > Settings > Taxonomy Translation to ensure that the English slug is correctly copied to other languages. If issues persist, we recommended testing the problem on a clean WordPress installation to isolate the issue. Further assistance with custom code, which is beyond WPML support scope, could be sought from certified WPML contractors, available here: https://wpml.org/contractors/
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.
Problem: The client reported an issue with a large number of Elementor templates displayed incorrectly, showing 71 instead of the actual count. Additionally, there were problems with deleting a language and its associated content, which seemed to be stuck. Solution: We recommended the following steps: 1. Ensure a backup of the site is available. 2. Navigate to WPML > Support > troubleshooting and perform the following actions: - Synchronize posts taxonomies (select 'templates' from the dropdown). - Clear the cache in WPML. - Remove ghost entries from the translation tables. - Set language information. - Fix terms count. - Fix post type assignment for translations. 3. Clear the site and browser caches and check the issue again. 4. If the problem persists, check for errors in the browser console and enable WordPress Debug to log any PHP errors. For instructions on enabling WordPress debug, refer to https://wpml.org/documentation/support/debugging-wpml/. 5. If issues continue, manually delete the templates by re-adding the language, navigating to 'Templates' in the specific language, and deleting them in bulk.
If these steps do not resolve the 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 needed, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is using the GDPR plugin Complianz to add custom services that show placeholders in the Buddyboss streams. The client can set the name in the backend and translate it in WPML, but the translations are not displayed consistently across different languages. Only one language appears to be "activated" and is shown for all languages.
Solution: We informed the client that the feature they are looking for is not currently available within WPML settings. We also mentioned that creating a script to handle this feature would require custom coding, which is beyond the scope of our support services. We recommended that the client refer to our documentation for developers and provided links to the WPML Hooks API for further assistance:
The author of the plugin has confirmed that it is currently not working.
If the solution provided here is not relevant to your case, either because it's outdated or not applicable, we suggest opening a new support ticket. 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 contact us in the WPML support forum.
Problem: The client was unable to translate certain strings within their website.
Solution: First, we advised the client to search for the specific string they needed to translate:
You are not currently subscribed to any %s
We also suggested that if the strings were not appearing in the desired language, the client could rename the .po file to force the strings to display in English, making it easier to search for them.
We also instructed the client to scan for strings within the 'BuddyBoss Platform' plugin by navigating to WPML->Themes and Plugin Localizations -> Strings in the plugins, selecting 'BuddyBoss Platform', and clicking on 'Scan selected plugins for strings'. If the provided solution is not relevant due to being outdated or not applicable to your case, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Should you need further assistance, please open a new support ticket.
Problem: The client was unable to find and translate the string "Group by:" in the Buddyboss group using WPML's string translation. Additionally, the client mentioned issues with the translation of a time-related string "vor 2 Monate (bearbeitet)" which should be "vor 2 Monaten (bearbeitet)", and the inability to translate the file upload feature in the timeline.
Solution: 1. For the "Group by:" string, we suggested that it might be coming from the Spacesengine plugin, which is not multilingual at the moment. 2. Regarding the file upload translation issue, we advised the client to wait for Buddyboss's feedback as they had already reached out for support. 3. For the time-related string, we acknowledged that living with "Monate" might be acceptable for the client. 4. We instructed the client to open a sandbox site and replicate the problem with only WPML and the Buddyboss plugin installed for further investigation. 5. Buddyboss mentioned that the "Uploading" is in a javascript file and cannot by translated as a string.
If the solution provided here is not relevant to your case, either because it's outdated or not applicable, we recommend opening a new support ticket. We also highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you need further assistance, please visit our support forum.
Problem: The client was experiencing a 404 error when a user visited a BuddyBoss group in a language different from the default language after the user was accepted into the group.
Solution: We recommended the following steps to resolve the issue: 1. Verify that all groups are visible in all languages and that the strings for the groups are translatable via WPML > String Translation. 2. Set Group Types to "Translatable - only show translated content" under WPML > Settings > Post Type Translation. 3. Go to BuddyBoss > Groups > Edit Group Type and change the translation method to WordPress Editor in the right sidebar. 4. Manually translate the Group Type. 5. Ensure that the group in question is translated and set to translatable.
Regarding the client's question about automatic translation for user-created groups, we informed them that it is not possible to automatically translate groups as soon as they are created by a user. The client would need to manually go to WordPress Dashboard > WPML > String Translation, select the group title and description, and then send it for automatic translation.
If the solution provided is not relevant due to being outdated or not applicable to your case, 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 through the WPML support forum.
Problem: The client is experiencing an issue where the correct product categories are displayed on the Shop page in English, but when switching to German, all product categories are shown. Solution: We recommend the following troubleshooting steps: 1. Back up your site's database. 2. Navigate to WPML -> Support -> Troubleshooting. 3. On the troubleshooting screen, press the following buttons one at a time and wait for each process to complete: -
Disable cache for language switcher templates
-
Clear language information and repopulate languages
(if available) -
Synchronize posts taxonomies
for the relevant post type -
Clear the cache in WPML
-
Remove ghost entries from the translation tables
-
Fix element_type collation
-
Fix WPML tables collation
-
Synchronize local job ids with ATE jobs
-
Synchronize translators and translation managers with ATE
-
Assign translation status to duplicated content
-
Set language information
-
Reset languages
(Only if you haven't added a custom language) -
Fix terms count
-
Fix post type assignment for translations
-
Cleanup and optimize string tables
-
Clear invalid strings
*** Please ensure you have a database backup before proceeding.*** If these steps do not resolve the issue, please provide us with access to your site for further investigation. You can safely share your details with us following our Privacy and Security Policy.
If the solution provided here is not relevant to your case, because it might be outdated or not applicable, we highly recommend checking the related 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.
Problem: The client was experiencing issues with the translation of a Buddyboss profile menu. After syncing, the languages menus were added but appeared empty, and the Buddyboss standard profile was displayed on the front end. Solution: 1. Delete the translated profile menus. 2. Navigate to WPML -> Support -> Troubleshooting. 3. Run the functions one by one. For reference, see the screenshot provided by the support team. 4. Go to WPML -> WP Menu Sync. 5. Sync the profile menu. 6. Edit the translated menus to add the navigation label and appearance settings. For further guidance, refer to the screenshot provided by the support team.
If these steps do not resolve the issue or if the solution seems outdated or not applicable, we recommend opening a new support ticket. We also highly suggest 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. For further assistance, please visit our support forum: https://wpml.org/forums/forum/english-support/.
Problem: The client was unable to see the translated custom link in the main menu, even though all other items were translated.
Solution: 1. We recommended checking the documentation on how to translate custom links in menus: Translating Menus. 2. We advised running the WP Menus Sync and then using String Translation to translate the custom links. 3. We identified issues with the WP Menus Sync on the client's website and resolved them by using the troubleshooting options in WPML. 4. We provided a screen recording demonstrating the solution: Screen Recording.
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. Should you still encounter issues, please do not hesitate to open a new support ticket with us.
Problem: Der Kunde hat mehrere Staging-Seiten mit WPvivid erstellt und stößt auf das Problem, dass nach der Erstellung einer Staging-Seite mit WPML-Einstellungen der WPML Setup Wizard erneut startet und die Einstellungen nicht von der Hauptseite übernommen werden. Solution: Wir haben festgestellt, dass das Problem auftritt, weil eine neue Datenbank anstatt der vorhandenen Datenbank verwendet wird, was dazu führt, dass die Tabelle
wp_options
geleert oder auf Standard zurückgesetzt wird. Um dieses Problem zu vermeiden, empfehlen wir, die vorhandene Datenbank zu verwenden, wenn eine Staging-Seite erstellt wird, damit alle Einstellungen, einschließlich der WPML-Optionen, erhalten bleiben.
Sollte diese Lösung nicht relevant sein, weil sie veraltet ist oder nicht auf Ihr Problem zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu öffnen. Wir empfehlen auch, die Seite mit bekannten Problemen zu überprüfen, die Version der dauerhaften Lösung zu verifizieren und zu bestätigen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben.
Wenn Sie weitere Unterstützung benötigen, zögern Sie nicht, ein neues Ticket im WPML-Supportforum zu eröffnen.
