There seems to be a lot of internal messages missing with various:[quote]Error text not found for this code and locale[/quote]
as well as:[quote]Source string for acquire_lock not found Source string for show_lock_details not found[/quote]
Also for people who are testing 3.6RC1, note that http login is disabled by default ('SQ_CONF_ALLOW_HTTP_LOGIN' => Array('editable' => 1, 'default' => '0')). It may be mentioned somewhere but i couldn't find where. The login error is ' Login Key incorrect' which didn't really help. Quick fix -if http login is acceptable- is to change the value to '1' in data/private/conf/main.inc. I'm assuming that https is the alternative but it doesn't suit my needs.
SQ_CONF_ALLOW_HTTP_LOGIN is a new configuration option that lets the user stored in $_SERVER['REMOTE_USER'] to be logged in automatically (a sort of single sign-on). It has nothing to do with the standard Matrix login box and should remain with its default value of '0' unless required.
Once again, i assumed too much, 
sorry for the misinformation I provided.
Is SQ_CONF_ALLOW_HTTP_LOGIN explained in details somewhere?
With SQ_CONF_ALLOW_HTTP_LOGIN = '0', I can't login using 'root' with password 'root' after a fresh CLI install. Switching it to '1' let's me log in. I don't mind leaving it to the default value if it is recommended, but why is the login failing then?
I have a feeling that you followed the CLI installation instructions provided (or simply followed the procedure for version 3.4.x or earlier) and that did not initially take into account the new localisation features that was put into 3.5/3.6 series. This requires extra installation steps, which have now been added to the first post in the CLI install thread.
If you don’t follow the extra steps, you will end up with all the strings either missing or coming up as “string code for xxxxxx not found” and the like.
Thanks Luke, the new instructions work a treat for the internal messages.
I still cannot log in as 'root' with password 'root' though (and now it seems setting ALLOW_HTTP_LOGIN to 1 still doesn't let me log in).
Now for all those who are wondering how I can tell that the fix worked if I can't log in into the system anymore, here is the trick. Hopefully this will also help to get an answer on the login issue.
I have 3.4.4 installed on the same machine. Both are served through the same virtual host on port 81. I simply change the aliases and restart Apache to get from one version to the other (Don't ask…).
If I log in 3.4.4, then change my Apache aliases to point to 3.6RC1, restart Apache, reload the page on the browser (shows me a login box), I can now happily log in as root (pwd:root).