Problem: The client reported that the title and location information was missing in the translations of a resume on their staging site. Solution: We recommended the following steps to resolve the issue: 1. Edit the resume in the default language. 2. Scroll down to the Multilingual Content Setup section. 3. Click "Show System Fields". 4. Set the needed fields to Translate or Copy. 5. Click "Apply". 6. Update the resume. 7. Update the translation. After these steps, the missing fields should display correctly.
If this solution does not resolve your issue, or if it 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 the problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client needed help accessing the content of a specific forum entry on WPML's website. Solution: We recommended that the client try to visit the forum entry again. Here is the link to access the content directly: WP Job Manager - Automatic Copy to Default Language.
If this solution does not resolve your issue, or if it 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. Additionally, you can open a new support ticket for further assistance at WPML support forum.
Problem: The client is experiencing issues with job listings visibility across different languages on their website. Specifically, jobs added in German (DE) are not visible in other languages, despite the site's standard language being English (EN). Solution: We explained that the behavior observed is expected due to the configuration settings: 1. The 'fallback to default language' feature functions only when the original post is in the default site language, which is English in this case. This means that for jobs posted in English, they will be visible in all languages without needing a translation. 2. For jobs posted in German, they need to be manually translated into other languages to be visible. We recommend using the Advanced Translation Editor for this purpose, where the automatic translation feature can help streamline the process. For detailed guidance on using this feature, please visit https://wpml.org/documentation/translating-your-contents/advanced-translation-editor/#automatic-translation.
If this solution does not apply to your case, or if it seems outdated, 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. Additionally, if further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client needed guidance on how to disable automatic translation for specific fields like the title and description in a job listing, and also inquired about the implications of setting a custom post type job_listing to "Translatable - use translation if available or fallback to default language" versus "Translatable - only show translated items". Solution: To exclude the post title from the translation editor, we recommended following the workaround provided in this forum post. However, this involves custom code, and if the client is not comfortable implementing it, we suggested contacting one of our certified partners, which can be found here: WPML certified partners. Regarding the translation settings, using the fallback setting "Translatable - use translation if available or fallback to default language" will disable the automatic translation feature. This feature only works with the setting "Translatable - only show translated items", which also means that a job added in a secondary language won't appear in the job list when switching back to the default language, nor will the language switcher show other languages.
If this solution does not apply to your case, or if it seems outdated, 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. Should you need further assistance, please do not hesitate to open a new support ticket or visit our support forum.
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
1
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
1
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:
1
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.
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
