setdbLanguageTag() creates no vmlangSef Update 3.0.12 -> 3.0.14

[Thomas Kuschel]

Hi,
during the update from 3.0.12  to 3.014 the function setdbLanguageTag() line 948 throws a notice "Notice: Undefined index: en-GB in /xxxx/administrator/components/com_virtuemart/helpers/config.php on line 948" on the backend
maybe, I reckon on my website, the frontend languages (content) are en-US (default), de-DE, fr-FR, zh-TW, and zh-CN; the language en-GB is installed but disabled!
Now the function on line 946 e.i.

Code Select Expand

$languages = JLanguageHelper::getLanguages('lang_code'); only gets the active languages from frontend, and on the next line fetches en-GB; because on my backend the default is en-GB.
on line 948 e.i.

Code Select Expand

self::$vmlangSef = $languages[$ltag]->sef; there is no defined array index yet. -> the self::$vmlangSef gets NULL.
To get rid off the error notices, I put an @ in front of this line 948; but the self::$vmlangSef is still set wrong;
HOWTO get this bug:
You can check this behaviour; just install language en-US and disable the en-GB on the "content languages" tab in the backend. Switch to default "en-US" on the "installed languages" page in Joomla.
BR
Thomas OE1TKT

Versions: Joomla 3.5; VM 3.0.14; PHP 5.6.17

[Milbo]

HOWTO get this bug:
You can check this behaviour; just install language en-US and disable the en-GB on the "content languages" tab in the backend. Switch to default "en-US" on the "installed languages" page in Joomla.

I would never do this. From my point of view it is your language setup, which is not correct.

[Thomas Kuschel]

Hi Max,
> From my point of view it is your language setup, which is not correct.
No, the setup is IMHO correct, we use the US language for our content, the language settings at the backend is kept original. I've no idea why this should be incorrect.
In our concern, we publish American English, default path in Joomla is British, that work before 3.0.14

Happy Easter!
Thomas

[Milbo]

HOWTO get this bug:
You can check this behaviour; just install language en-US and disable the en-GB on the "content languages" tab in the backend. Switch to default "en-US" on the "installed languages" page in Joomla.

I would never do this.

The fallback works on en-Gb. Maybe it is enough to uncheck the language fallback in the vm config.

[Thomas Kuschel]

hi,
I unchecked that line in the vm conf, but this didn't change that behavior,
I've no time for this bug at the moment; but I will remember and I'll suggest a solution.
Indeed, it only fails in the backend,
Tom

[Milbo]

What happens, when you just install the en-GB again for the BE?

[Thomas Kuschel]

What happens, when you just install the en-GB again for the BE?

thank you for your respond Milbo, 6 languages are installed, also the en-GB, but the language en-GB is disabled in frontend only, so the array $languages gets no array item with Joomla default language en-GB.
The functionality is okay, virtuemart works, only a notice is thrown because the

Code Select Expand

self::$vmlangSef = $languages[$ltag]->sef; has no valid array of

Code Select Expand

$language['en-GB']; this problem only exists when entering the backend with en-GB language, and it is the default one here.

I added a

Code Select Expand

@ in front of this line:

Code Select Expand

@self::$vmlangSef = $languages[$ltag]->sef;; and the notice is gone.
Note: In Joomla, you can't disable languages for backend; and the en-GB is a must to have!
I can live with this change in VM core.
Thomas