Brion Vibber wrote:
Mmm, not exactly. They all use the same base source, but they're duplicated in a series of directories. Each has various settings in LocalSettings.php different, such as language selection, name of database to use, the URL to use for self-links, etc.
Just to be sure, you could change some code in any of the php files in the e.g. german wikipedia only? I though the only file which is language dependend are the Language*.php ones and Localsettings.php.
However, there are two potential pitfalls:
- People using different login _names_ on different wikis would have to
settle on one.
- There might be some cases of duplicate names on different wikis which
belong to different people. We can verify if they're the same by checking that passwords match, but some people may use different passwords, so we can't be 100% sure in that case.
Well, that are problems you got, if you take the easy way. First of all, you save the passwords in clear text in the db? *running to the source* found md5 *wipe* But no salt. Only the hash! *shiver*. I see the urgent reason to get new user accounts and passworts.
I still not shure why we can't have both, Single sign on (I like those buzzwords ;) and different names. A table like this:
create table userid_at_wiki ( newuserid int references user(userid), wikidb varchar(25), olduid int, oldname varchar(255) );
SELECT userid_at_wiki.newuserid, userid_at_wiki.wikidb, userid_at_wiki.olduid, userid_at_wiki.oldname, user.name FROM userid_at_wiki JOIN user ON userid_at_wiki.newuserid = user.newuserid WHERE user.name = 'Smurf'; Result: 11245, 'meta', 1565, 'Smurf', 'Smurf' 11245, 'de', 756, 'Smurf', 'Smurf' 11245, 'foo', 345, 'yawn', 'Smurf' (3 rows)
will get around some of you problems brion, IMHO .
Smurf