Problem: The client is developing a site using WP Job Manager with the Application plugin and is facing an issue where the resume is shown in all languages on the application form. Solution: We recommended checking the errata page for a known issue with WP Job Manager where resumes are displayed in all languages in the dropdown list. The correct errata that addresses this issue can be found here: WP Job Manager Applications - Resume shown in all languages when using application form. We applied the fix from this errata to resolve the issue.
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. If the issue persists, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
Please note that this solution might be outdated or not applicable to your specific case. If this does not resolve your issue, 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: You are developing a site using WPML where users can apply for jobs in different languages. You want to ensure that if a user applies for a job in one language, they cannot apply for the same job in another language. Additionally, you want all applications to be visible in the job dashboard across all language versions. However, users are currently able to apply for the same job in different languages, and applications are shown separately in the job dashboard for each language version. Solution: We have identified that this behavior is expected since jobs are translated and have different post IDs, making them distinct posts in each language. Therefore, Job Applications are also treated separately for each language. We recommend leaving the Job Application translatable and allowing users to apply in both languages. If this solution does not meet your needs, you may consider submitting a feature request to the WP Job Manager authors for the desired functionality. You can submit this request through their support or GitHub at https://github.com/Automattic/WP-Job-Manager/issues.
Please note that this solution might be irrelevant if it's 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 issue persists, please open a new support ticket at WPML support forum.
Problem: The client is experiencing issues with automatic string translation in WPML, where the translation process is stuck, showing only the cog symbol. Despite attempts to delete the automatic translation jobs in troubleshooting, they are not being successfully removed. Solution: We recommend trying the beta versions of WPML, which include changes to the string translation process. These beta versions can be tested on a staging site or a separate copy of the site to avoid affecting current work. You can download the beta packages from https://wpml.org/account/downloads/.
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 problems persist, please open a new support ticket at WPML support forum for further assistance.
You are developing a site using WP Job Manager and WPML and have encountered an issue where the application form in the job edit form displays in all languages instead of only the form of the current language.
Solution:
To resolve this issue, we recommend modifying the code to ensure the application form displays only in the current language. Please follow these steps after making a full site backup:
function get_application_forms() {
$posts = new WP_Query(
array(
'post_type' => 'job_application_form',
'posts_per_page' => - 1,
'suppress_filters' => false, // replace true with false
'orderby' => 'title',
'order' => 'ASC',
)
);
$default_form = WP_Job_Manager_Applications_Default_Form::get_default_form();
if ( $posts->post_count < 1 ) { // replace <= with <
return null;
}
$application_forms = [];
/* comment out this part if you don't want to see the default form in other languages
if ( array_key_exists( 'ID', $default_form ) ) {
$application_forms[ $default_form['ID'] ] = $default_form['post_title'];
}*/
foreach ( $posts->posts as $post ) {
$application_forms[ $post->ID ] = $post->post_title;
}
return apply_filters( 'job_application_forms', $application_forms );
}
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 do not hesitate to open a new support ticket at WPML support forum.
If you're experiencing a 404 error when a non-admin user tries to access a resume in a different language on your site using WP Job Manager's Resume Manager, it might be due to the translation of the resume post type's slug. Admin users do not face this issue because they bypass certain permission checks.
Solution:
We recommend following these steps to resolve the issue:
4) Go to WPML>>Settings>>Slug translations and ensure that "Translate custom post and taxonomy base slugs (via WPML String Translation)." option is selected. 5) In the "Post Types Translation" section, translate the Resumes Post Type slugs. 6) Navigate to Settings>>Permalinks and resave the settings.
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. If issues persist, please open a new support ticket.
The client is developing a site using WP Job Manager and WPML and encountered an issue where the dropdown list for selecting resumes shows all language versions instead of just the current language version.
Solution:
We recommended the client make specific changes in the code to ensure the dropdown only displays resumes in the current language. Here are the steps:
Please ensure to back up your site before making these changes. If this solution does not resolve your issue or seems 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 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/.
