Jesse Graupmann

Looks like the quick fix is just to check if the value is empty before output.

echo self::output_filename(
empty($mofile['caller']['display']) ? '' : $mofile['caller']['display'],
empty($mofile['caller']['file']) ? '' : $mofile['caller']['file'],
empty($mofile['caller']['line']) ? '' : $mofile['caller']['line'] ); // WPCS: XSS ok.

I was looking into this today for Black-Buddha.com. It seems for Chinese at least, the language code needs to match exactly. ko works, but zh_cn doesn’t match zh_tw.

After reading this post and looking over polylang/frontend/choose-lang.php -> get_preferred_language() : line 85, it might just be a matter of hooking into the ‘pll_preferred_language’ filter.

// allow plugin to modify the preferred language (useful for example to have a different fallback than the default language)
$slug = apply_filters('pll_preferred_language', isset($pref_lang) ? $pref_lang->slug : false);

just make sure the cookie hasn’t been set or you’ll never get that far;

if (isset($_COOKIE[PLL_COOKIE]))
return $this->model->get_language($_COOKIE[PLL_COOKIE]);

This all assumes like Chrystl said, you’ve already set your preference in ‘/options-general.php?page=mlang&tab=settings’ and you’re hitting the homepage;

Detect browser language:	 When the front page is visited, set the language according to the browser preference

@miled – Thanks for this plugin!

You have made my life (and other lives) easier and any work you put into it is appreciated and valuable. 30,000+ active installs isn’t half bad.

I was looking into a similar solution, just a simple query override. Here is my attempt w/the information you’ve provided Chouby. The majority of this code is just checking the query against known supported languages before making the override.

This doesn’t work 100%, 100% of the time – but it get’s pretty close.

The goal would be for anyone, even an FB crawler to specify a locale when linking to a page like https://black-buddha.com/?locale=zh_TW or https://black-buddha.com/zh_tw/watch/mott32-2/?fb_locale=en_US. I’ve been seeing a lot of log entries from facebook.com/externalhit_uatext.php lately and I wonder if this might be helpful.

Either way, I just want to solve this translation override for the login form, so here is a start.

Cheers

/* ==================================================
* OVERRIDE CURRENT PLL LANGUAGE
* ==================================================*/

/**
 * HiJack the pll_language_defined action and override the current language.
 * @param string $slug
 * @param PLL_Language $curlang
 * @example https://black-buddha.com/?l=zh_TW
 * @example https://black-buddha.com/zh_tw/city/臺北/?locale=en_US
 * @example https://black-buddha.com/watch/flask/?fb_locale=zh_TW
 * @example https://black-buddha.com/?lang=zh_TW
 */
function ___pll_language_defined ( $slug, $curlang ) {
	static $override_language = FALSE;
	global $polylang;

	if ( ! $polylang ) {
		return;
	}

	if ( ! $override_language ) {
		$reqs = array( $_GET, $_POST );
		$params = array( 'lang', 'locale', 'l' , 'fb_locale' );

		foreach ( $reqs as $req ) {
			if ( $override_language ) break;

			foreach ( $params as $param ) {
				if ( $override_language ) break;

				if ( ! empty( $req[ $param ] ) ) {
					$override_language = sanitize_key( $req [ $param ] );
					break;
				}
			}
		}
	}

	if ( $override_language ) {

		// validate against known languages
		$supported_languages = $polylang->model->get_languages_list ( );
		foreach ($supported_languages as $lang) {
			if ( FALSE != preg_match( "/($override_language)/i", $lang->locale )) {
				$override_language = $lang->slug;
				break;
			}
		}

		if ( ! $override_language) {
			error_log ( 'FAILED to find language support for ' . $override_language );
			$override_language = FALSE;
			return;
		}

		// try to get the language
		$nLanguage = $polylang->model->get_language( $override_language );
		if ( $nLanguage ) {
			$polylang->curlang = $nLanguage;
			$GLOBALS [ 'text_direction' ] = $polylang->curlang->is_rtl ? 'rtl' : 'ltr';
			stop_checking_language_code_in_url ( );

			// NOTE: setcookie has been called already
			// (PLL_Choose_Lang)$this->maybe_setcookie();
		} else {
			error_log ( 'FAILED to change language to ' . $override_language );
			$override_language = FALSE;
		}
	}
}

// NOTE: do_action called from wp-content/plugins/polylang/frontend/choose-lang.php
add_action('pll_language_defined', '___pll_language_defined', 0, 2);

function stop_checking_language_code_in_url ( ) {
	global $polylang;
	if ( $polylang ) {
		remove_action('wp', array ( $polylang->choose_lang, 'check_language_code_in_url' ));
	}
}
// WARNING: Stops working well when you remove the code in url check...
// if(did_action('plugins_loaded')) stop_checking_language_code_in_url();
// add_action( 'plugins_loaded', 'stop_checking_language_code_in_url', 10 );

ACF has changed the way they get their posts in 5.2.X. It may be because of polylang/frontend/frontend-auto-translate.php; PLL_Frontend_Auto_Translate->pre_get_posts($query); Since the new method for ACF relies on pre_get_posts.

I am ready to launch a multilingual site with PolyLang and ACF in two weeks. I would love to work towards a solution for this.