Hi Mike,
I am in the same situation needing to be able to run a multilingual with your core applications and the Jobify theme.
When I read on the Jobify marketing page on themeforest it Saids that it is WPML compatible and the theme recommends WP job manager so I really tohught it would Work.
What exactly is that dont Work ?
I only need the users to be able to change the language for the static text. The dynamic text in add and resumes does not need any translation in my case.
Best regards,
Nicolai
@nh123 At the moment, some users are having trouble with it not pulling the jobs for a language they are viewing. Some other users want it to copy jobs to all languages when posted, but WPML doesn’t do this. Finally, some users are having trouble when they have jobs in different languages with a different base permalink.
Hi Mike,
Any update on the issue that you described above?
Thanks
ISC
@theisc WPML never replied. We did add compatibility in that it will show jobs from the current language. Anything beyond that, such as duplicating jobs to all languages, will require customisation and help from WPML directly.
Hi Mike and friends,
WPML answer me today this:
If your theme is not compatible with us, Please feel free to invite the theme author to join our “Go Global” program to make theme fully compatible with WPML:
=> http://wpml.org/documentation/theme-compatibility/go-global-program/
I don’t know why they don’t answer you Mike… but I trust in your effort
@alexmanc they pinged me again today 🙂
Hey Mike,
I’m in the same situation here. Running latest WPML and using English and French. I have all taxonomies and categories translated. When viewing the French [jobs] page, only English jobs show up even when French taxonomies are selected.
Have you heard anything back from WPML on this? Do you know of a temporary workaround to get this off the ground in the meantime?
Thanks!
Hi Mike,
I solved my own problem temporarily. This is by no means a great fix, but at the very least fixed my issue for now.
Under the get_endpoint() method in wp-class-job-manager-ajax, I added a conditional to check the current language. After which I change the $endpoint var.
/**
* Get JM Ajax Endpoint
* @param string $request Optional
* @param string $ssl Optional
* @return string
*/
public static function get_endpoint( $request = '', $ssl = null ) {
/* Temporary workaround for WPML */
$current_lang = get_locale();
if($current_lang == 'fr_FR')
{
$endpoint_prefix = '/fr/';
}else
{
$endpoint_prefix = '';
}
if ( strstr( get_option( 'permalink_structure' ), '/index.php/' ) ) {
$endpoint = trailingslashit( home_url( '/index.php/'. $endpoint_prefix . 'jm-ajax/' . $request, 'relative' ) );
} elseif ( get_option( 'permalink_structure' ) ) {
$endpoint = trailingslashit( home_url( $endpoint_prefix . '/jm-ajax/' . $request, 'relative' ) );
} else {
$endpoint = add_query_arg( 'jm-ajax=', $request, trailingslashit( home_url( '', 'relative' ) ) );
}
return esc_url_raw( $endpoint );
}
This is again a temporary fix for all who suffer from this issue currently.
It wasn’t for me. Perhaps my setup is different in some way? I analyzed the headers and my _icl_current_language was set correctly to ‘fr’ everywhere except the [jobs] page. Once an AJAX call was made, the response headers reset the _icl_current_language cookie back to en.
Modifying the AJAX endpoint was the only permanent (until update) solution that fixed it for me. Any ideas? It seems to work fine now.