From: Nicola S. <nso...@ti...> - 2004-05-25 16:02:00
|
Alle 18:11, luned=C3=AC 24 maggio 2004, Markus Bertheau ha scritto: > =D0=92 =D0=9F=D0=BD=D0=B4, 24.05.2004, =D0=B2 17:01, Christopher Kings-Ly= nne =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > > ! $lang['strlogindisallowed'] =3D 'Login disallowed for security'; > > --- 27,31 ---- > > ! $lang['strlogindisallowed'] =3D 'Login disallowed for security reaso= ns.=20 > > Please read the FAQ and check the \'extra_login_security\' option in yo= ur > > configuration file.'; > > I think you should revert this change. A string freeze is a string > FREEZE. We have localizations also for people that don't understand > english and those will not be able to read that message. But the main > point is that a string freeze is there for translators to catch up with > their translations in order for the developers to deliver an application > with quality translations. Breaking string freezes does work against > that. I don't like that change very much too, what about applying the simple=20 attached patch? > And I don't see why you don't instead of referring to the faq explain > the issue right here - that message won't be much longer. Our explanation in the FAQ is quite long: "Q: For some users I get a "Login disallowed for security" message. A: Logins via phpPgAdmin with no password or certain usernames (pgsql, postgres, root, administrator) are denied by default. Before changing th= is behaviour (setting $conf['extra_login_security'] to false in the config.inc.php file) please read the PostgreSQL documentation about clie= nt authentication and understand how to change PostgreSQL's pg_hba.conf to enable passworded local connections." BTW, having also the FAQ translated would be a nice feature... Nicola |