I thought it didn't have anything to do with the preferences system itself,
but was a performance issue; the context switching needed to get the
preferences everytime would be too darn expensive. I vaguely recall Domas
mentioning something like that...
Van: [hidden email] [mailto:[hidden email]] Namens Alex
Verzonden: donderdag 6 november 2008 20:49
Aan: Wikimedia developers
Onderwerp: Re: [Wikitech-l] Bug in user prefereces
I don't think there's anyone who thinks that global preferences would be a
bad idea (or if there are, they're a tiny minority). It just hasn't been
done yet. Any global preferences system would probably come after a rewrite
of the current preferences system as it would probably be done in mostly
the same way. Doing it one preference at a time would be rather inefficient.
The main issue is that you may not want the same preferences everywhere.
For example, email notification settings, which also has the issue of not
being consistent across projects. I may want notification for watchlisted
changes on small projects I don't check often, but not for commons and meta,
as I check those often. Or you may not want to use UTC on projects that use
a different default timezone for signatures and such. So the global
preferences would have to be locally overridable.
On Thu, Nov 6, 2008 at 2:57 PM, Siebrand Mazeland <[hidden email]> wrote:
> I thought it didn't have anything to do with the preferences system itself,
> but was a performance issue; the context switching needed to get the
> preferences everytime would be too darn expensive. I vaguely recall Domas
> mentioning something like that...
Domas doesn't want a hit on the global user table for every page view,
IIRC, no. However, there could be implementations that avoid that,
perhaps using memcached, or just stupid denormalization to all the
other databases (a button saying "change this preference on all my
accounts and any new ones").
On Fri, Nov 7, 2008 at 11:18 AM, Aryeh Gregor
<[hidden email]> wrote:
> Domas doesn't want a hit on the global user table for every page view,
> IIRC, no. However, there could be implementations that avoid that,
> perhaps using memcached, or just stupid denormalization to all the
> other databases (a button saying "change this preference on all my
> accounts and any new ones").
We already cache global user objects in memcached, and memcached hits
are cheap, anyway (on the order of a few hundred us).
> 2008/11/5 Timwi <[hidden email]>:
>> I get the following message:
>> Your password is invalid or too short. It must have at least 1
>> character and be different from your username.
>> If the password boxes are empty, the system should not assume that I was
>> trying to change my password.
> If the password boxes are really empty, the system assumes that.
> However, if you use some password-remembering browser (such as
> Firefox), it "helpfully" pre-fills the "current password" box, leading
> to this. At least, that is what happened to me. Be sure to manually
> clear the "old password" editbox before changing other preferences,
> and everything should work fine.
We're still kind of assuming it's something like this problem. :)
The proper thing to do is to move the password reset form out of
preferences to its own form -- it really shouldn't be there anyway.
- -- brion
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org