ussue #148

qtranslate_utils.php

@@ -365,7 +365,7 @@ function qtranxf_external_host_ex($host,$homeinfo){
 	global $q_config;
 	//$homehost = qtranxf_get_home_info()['host'];
 	switch($q_config['url_mode']){
-		case QTX_URL_QUERY: return $homeinfo['host'] != $host;
+		case QTX_URL_QUERY:
 		case QTX_URL_PATH: return $homeinfo['host'] != $host;
 		case QTX_URL_DOMAIN: return !qtranxf_endsWith($host,$homeinfo['host']);
 		case QTX_URL_DOMAINS:
@@ -418,6 +418,8 @@ function qtranxf_startsWith($s, $n) {
 
 /**
  * @since 3.2.8
+ * $s - string to test
+ * $n - needle to search
  */
 function qtranxf_endsWith($s, $n) {
 	$l = strlen($n);

readme.txt

@@ -85,7 +85,7 @@ Developers: please drop new topics here, the text will be moved to [qTranslate-X
 * Upgrading from other qTranslate forks also painless with an additional steps of configuration import and using 'Convert Database' option. One may also go back at any time using configuration export and 'Convert Database' option.
 * Former page and post translations are untouched and preserved in any case, except when using 'Convert Database' option.
 * Upgrading from other multilingual frameworks will require custom re-configuration. We suggest to search for a plugin, which may be already implemented to transfer the translations to qTranslate or to qTranslate-X. If a plugin works for one, it should work for other too, since qTranslate-X and qTranslate share the same database structures.
-* **Important**: Read [migration instructions](https://qtranslatexteam.wordpress.com/2015/02/24/migration-from-other-multilingual-plugins/).
+* **Important**: read [migration instructions](https://qtranslatexteam.wordpress.com/2015/02/24/migration-from-other-multilingual-plugins/).
 
 ## Screenshots ##