This extension leads to an error in Vanilla 1.1:
Notice: Undefined property: Context::$LanguageSelectorArray in .../extensions/LanguageSelector/default.php on line 68

Fatal error: Call to undefined function BuildLangArray() in .../extensions/LanguageSelector/default.php on line 71

I have not downloaded 1.1, yet.
My own application is closely related to Vanilla so I have to check it out with some time ahead.
But I'm rather confident, seeing the message above that the answer to icouto question is NO.
And then, to Tex: do the required changes.

@ Max_B:
Well, I will try to do. If I succeed (what I doubt right now), I will let you know.

With Vanilla 1.1.1 the problem seems to only occur for guests and if members are browsing to their own account.

I don't know what you mean with patch my install, sorry. To use this extension, I did nothing more than upload and activate it so far.

Shame on me!

How could I forget about this? Sorry for messing up this discussion. If anybody wants to delete all my junk here, please go ahead. Thank you, Max, for your patience! I am sorry.

Max, please note that in default.php the name of the extension has to be changed from "Language Selector" to "LanguageSelector" (without space in between), for it to be compatible with the new update-checker of Vanilla 1.1.x.

@JDW: you can delete that yourself, if you want to - I have deleted it in mine, and it now works. I'm sure that Max will fix it with the next release, though.

Corrected the space typo and added the following readme note:
**************************************
INSTALLATION, conf/language.php option
**************************************
Recent releases of Vanilla inversed the order of language files include.
This opens an alternate installation method, if you do NOT use conf/language.php for extensions translations.
Just insert the above LanguageSelector include line in the conf/language.php files.

Note: Using conf/language.php for extensions translations is NOT a good choice for a true multilingual setup.
It does not allow on-fly extension switching. There is no alternate STANDARD method yet (Vanilla 1.1.2).
My own method is to store extension translation in separate files and add specific includes in conf/extensions.php.
Exemple :
@include($Configuration['EXTENSIONS_PATH']."CategoryJumper/{$Configuration['LANGUAGE']}.php");
include($Configuration['EXTENSIONS_PATH']."CategoryJumper/default.php");

Was this a mocking comment?
I'm still waiting to read a comment in French, without a single typo, from a native English speaker after he worked to release some useful extension…

My comments are never written to mock others. I do to others as I would like done to myself.

Max, please reflect on the fact that you were the one who initiated dialog about "typos." Had you not done that, I would not have made any suggestions to you at all concerning other spelling errors that I myself had found. I think that is quite clear though because if you search for every post I have made to date, you will not find any others from me that talk about spelling errors, even though I have found many spelling and grammar errors in many Vanilla extensions.

Your native language is not an issue here. The facts simply are that: (a) you willingly created an extension in English of your own accord, and (b) you were the one who opened dialog about spelling. Having read your "typo" comment, I simply offered some advice on how to correct, without having made any attempts to mock you or your native tongue. And if I myself were to ever venture into creation of French language extensions, I would certainly hope that kind souls such as yourself would assist me in making the language as perfect as it could be. Goodness knows my friends here in Japan do that with regard to my written Japanese!

Thank you, Max, for an excellent extension. And please know that a spelling error here or there does not detract from the fact you are an excellent Vanilla Extensions developer!

This is a great extension, thanks for your hard work.

I use it on my forum: www.twingoloversclub.com

Hi all: I'm getting the same errors as ryanopaz:
===========
Notice: Undefined property: Context::$LanguageSelectorArray in /home/.xxxxxx/jrpg/xxxxxx.com/kaikan/extensions/LanguageSelector/default.php on line 84

Fatal error: Call to undefined function buildlangarray() in /home/.xxxxxx/jrpg/xxxxxx.com/kaikan/extensions/LanguageSelector/default.php on line 87
============
Same lines. This is a first install, and I'm using Vanilla 1.1.4, and trying to get Japanese to work.

I get the above error when I click on my Account page and click on "Languages". It immediately gives the above instead of a lang select area.

I followed all the instructions in the readme, including adding the include lines to all the noted appg "init*.php" files.

Is it incompatible with Vanilla 1.1.3/1.1.4?

-Andy

1. isn't it possible to make Mark and other Vanilla core developers to implement some standard nice and clean way allowing install extensions without core hacks?

I would recommend to create an empty /path/to/vanilla/conf/init_language.php and in /path/to/vanilla/appg/init_*.php to have:
// DEFINE THE LANGUAGE DICTIONARY
include($Configuration['APPLICATION_PATH'].'conf/init_language.php');
include($Configuration['LANGUAGES_PATH'].$Configuration['LANGUAGE'].'/definitions.php');
include($Configuration['APPLICATION_PATH'].'conf/language.php');
instead of:
// DEFINE THE LANGUAGE DICTIONARY
include($Configuration['LANGUAGES_PATH'].$Configuration['LANGUAGE'].'/definitions.php');
include($Configuration['APPLICATION_PATH'].'conf/language.php');

the conf folder is editable by Vanilla itself so it would be possible to install the necessary code there by extension self.
I'm already adding some code to conf/language.php by an extension but I think if there is more extensions altering conf files code, then I could write an extension managing install/uninstall code into conf/*.php files (except settings.php, extensions.php and database.php)

You think it is possible to convince the Vanilla team? :) I really don't like core hacking :)

2. I need LanguageSelector to allow to set multiple languages and with a drag&drop list able to specify a priorities of languages loaded.
I'm going to alter your code and add this functionality there as an option.
Are you interested and open to add my patches and doing a release?
Or should I upload it as a new extension? :-)

Thanks! Check this post. There is a summary of my thoughts :-)