The client is experiencing an issue where editing a job post in one language results in updates being saved across all language versions, leading to prolonged save times. They seeks a solution to save the job in the original language without automatically updating all the language versions immediately.
Solution:
We informed that due to the nature of WPML and its handling of duplicated posts, any updates to the original post would automatically sync with the duplicates. To manage this, the client can manually set the duplicates to 'Translate Independently' by clicking the Translate Independently button on the duplicate post in the secondary language. This action prevents automatic updates to the translated versions when the original is edited. Later, if needed, the translated versions can be updated manually by selecting the Overwrite with - option.
For detailed steps, please refer to the following documentation:
If this solution does not apply or is outdated, we 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.
The client is developing a site and needs translations only on the frontend. They are looking to improve site speed by deleting unnecessary backend translation strings in WPML.
Solution:
If you're experiencing similar issues, we recommend following these steps to delete unnecessary strings to potentially improve your site's speed:
1. Ensure you have a full site backup before making changes. 2. Navigate to WPML → String Translation. 3. Scroll down to the 'Remove strings by domain' section. 4. Click 'Remove strings'. 5. Select the domains you want to delete and click 'Remove'.
This process will remove all untranslated strings in the selected domains, and they will no longer appear on the String Translation screen.
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 https://wpml.org/forums/forum/english-support/.
Problem: The client is implementing a resume count limit on a multilingual site using WPML. The limit works in the default language but fails in the second language, showing the 'Add Resume' button even when the limit is reached. Solution: We recommend taking a backup of your site and testing the following code to ensure the resume count limit works across all languages:
If this solution does not resolve the issue, we can provide a WPML test site to further investigate and solve the problem.
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.
The client reported an issue where resumes are duplicated like jobs in the WP Job Manager Resumes plugin, and when deleted from the frontend, only the current resume is deleted, not the copies.
Solution:
We recommend following these steps after ensuring you have a full site backup:
Please note that this workaround will delete translations, irrespective of the "When deleting a post, delete translations as well" option.
If this solution does not resolve your issue or 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. If the problem persists, please open a new support ticket at WPML support forum.
Problem: If you're experiencing 404 errors with resumes when the Tax Exception plugin for WooCommerce is enabled, and the errors disappear when the plugin is disabled. Solution: We recommend trying to switch the language settings and then adjusting the permalink settings in your WordPress dashboard. After making these changes, save the settings again. This approach helped resolve similar issues in our tests, even with the Tax Exception plugin activated.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable 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, if you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client is experiencing issues with WP Job Manager and WPML on a development site. Specifically, when switching languages, the URL redirects to a 404 error, and deleting a resume in one language does not delete it in other languages. The client suspects a conflict with the Tax Exemption WooCommerce plugin, which when enabled, causes a 404 error. Solution: We recommend first going to WPML -> Permalinks and temporarily changing the selected option. Save the changes and then revert back to the original setting. If this does not resolve the issue, we suggest deactivating all plugins on a staging site to test and ensure no server-side caching is interfering. If these steps do not resolve the issue, it might be outdated or not applicable 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.
The client was experiencing issues with the WPML setting 'When deleting a post, delete translations as well' not functioning correctly for duplicated posts when deleted from the frontend. The main post would be deleted, but its duplicates would remain.
Solution:
We recommended the following steps after ensuring a full site backup:
1) Navigate to the
1
/wp-content/plugins/wp-job-manager/includes/
folder. 2) Open the
1
class-job-dashboard-shortcode.php
file for editing. 3) Locate line number 466 and replace the existing code with:
This code ensures that when a job post is deleted from the frontend, all its translations are also trashed, regardless of the WPML setting.
If this solution does not resolve your issue or seems irrelevant due to updates or differences in 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 issues persist, please open a new support ticket at WPML support forum.
Problem: If you're experiencing issues with duplicate activity entries in BuddyBoss when adding a new job in WP Jobmanager, and the links for each language in the activity entries are incorrect, this is a known issue. The problem arises because when a job post is created and set as translatable in WPML, translated posts are automatically generated in all languages, leading to multiple activity posts. Solution: Currently, there is no direct workaround from our side as this issue requires adjustments in the BuddyBoss plugin. We recommend monitoring the BuddyBoss updates and checking the related known issues on our site. You can view the specific issue here: https://wpml.org/errata/buddyboss-posts-and-activities-not-filtered-by-language-on-feed-pages/. Additionally, there is a client-suggested workaround that might help, but it could break pagination. You can find more details here: https://wpml.org/forums/topic/filter-by-language-does-not-work-for-activity-feed/page/2/#post-13969021.
If this solution does not apply to your case, or if it seems outdated, we highly recommend opening a new support ticket. Please also check related known issues (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. For further assistance, you can contact us directly at the WPML support forum.
Problem: The client is experiencing slow string translations and some languages not being translated, indicated by a cog symbol. Additionally, there are occasional fatal errors, though clearing the WPML cache resolves these temporarily. Solution: If you're experiencing similar issues with automatic string translation in WPML, first ensure that your translation engine supports the language pair you are translating to. You can check supported languages here: https://ate.wpml.org/mt_langs. Follow these steps to potentially resolve the issue: 1. Navigate to "WPML > Settings" and set the Translation mode to "Translate what you choose". 2. Go to "WPML > Support > Troubleshooting" and click on: - Cancel in-progress automatic jobs - Clear the cache in WPML - Fix element_type collation - Synchronize local job ids with ATE jobs - Synchronize translators and translation managers with ATE - Assign translation status to duplicated content - Set language information - Fix post-type assignment for translations 3. After completing these steps, switch the translation mode back to "Translate Everything Automatically" and send the string for automatic translation again. If issues persist, clear caches on your site and browser, and if possible, temporarily disable any optimization/caching plugins. For errors, check the "WPML > Support > Advanced Translation Editor > Error Log" and provide a screenshot if further assistance is needed.
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 problem persists, please open a new support ticket.
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
1
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.
