Problem: The client is experiencing a timeout issue when trying to automatically duplicate job listings to the default language using custom code from the WPML forums. Despite disabling unnecessary plugins and checking the debug log, the timeout persists. Solution: We recommend using the bulk 'duplicate' feature in WPML for duplicating posts from a secondary language to the default language. This can be done by navigating to WPML->Translation Management, filtering for the posts created in the secondary language, and performing a batch duplication to the default language. If custom code is necessary, we suggest modifying the existing code to prevent duplicate function calls and ensure it targets the specific needs of the site. Here is an example modification:
Ensure that listings are set to 'translatable' in WPML->Settings. If further customization is needed, consider hiring a specialized developer with WPML experience from https://wpml.org/contractors/.
If this solution does not resolve your issue or seems outdated, please check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket at https://wpml.org/forums/forum/english-support/.
Problem: If you're experiencing issues with the resume limit being incorrectly calculated as four times the desired amount due to WPML language settings, this might be due to the way the resume count function is coded in the WP Job Manager - Resume Manager plugin. Solution: We recommend modifying the
resume_manager_count_user_resumes
function within your plugin files. Specifically, us the workaround in the following comment:
This modification ensures that the resume count only includes original language posts, excluding translations, thus providing an accurate count per user. Take note, that the author is informed and will implement this fix in a future version of the plugin. If this solution does not resolve your issue or becomes 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. If further assistance is needed, please open a new support ticket at WPML support forum.
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
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.
