Is that really useful, considering how easy it is to set up a yahoo/hotmail/gmail/whatever else account?
Gabe
-----Original Message-----
From: mediawiki-l-bounces(a)Wikimedia.org [mailto:mediawiki-l-bounces@Wikimedia.org] On Behalf Of Mischa Peters
Sent: Monday, December 05, 2005 12:28 PM
To: MediaWiki announcements and site admin list
Subject: Re: [Mediawiki-l] Email approval before login
Hi Kent,
[snip]
> I apologize if this is really off topic for this list -- but you kind
> of brought up the subject by assuming that Mischa was against 'open' editing.
> I don't know what his wiki is about or what his policies are, but I
> don't think enforcing a valid email address conflicts with 'open editing.'
I am running different wiki's, one is more open then the other. But I would still like to know who is adding what and not just know their "nickname".
Mischa
_______________________________________________
MediaWiki-l mailing list
MediaWiki-l(a)Wikimedia.org
http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
Hi,
I installed MediaWiki 1.5.3 and everything went smoothly. But now it
wont let me past the installation successful page when I go to
index.php, index.php/, or even just the directory /. I have moved the
LocalSettings.php file from /config to the wikis root by downloading
it and re-uploading it. Any ideas?
Thanks, Gary.
--
*** I call it the "Sproose Moose"! ***
On 12/5/05, Kent S. Larsen II <kent(a)lusobraz.com> wrote:
> At 3:36 PM +0000 12/5/05, Rob wrote:
> >By default, no it's not enforced, and that's because Wikimedia is
> >about open editing, etc. You'll have to hack at the code to enforce
> >email addresses.
> >
> >
> >Rob Church
> >
>
> Rob, I don't think that restricting editing is the reason why so many users
> are looking for email verification. Its more to reduce fraud and slander
> and increase the ability to trace who is saying what.
>
How can you reduce fraud and slander and increase the ability to trace
who is saying what without restricting editing? If you can think of a
way to do this, I'd like to hear it.
> You may have seen the following horror story:
>
> http://www.usatoday.com/news/opinion/editorials/2005-11-29-wikipedia-edit_x…
>
Someone posted something false about someone else on the internet. At
least, I think it was false. The opening paragraph seemed completely
true. I don't particularly see the "horror", though.
> Personally, I like the collaborative nature of mediawiki, and I have argued
> elsewhere that Wikipedia is so large now that it simply can't be ignored by
> those online (I argued this to an academic community -- many ended up
> accepting the fact). But the fact that an anonymous person can post a lie
> or misrepresentation or rumor to Wikipedia or any wiki without disclosing
> their identity makes it a tough sell to anyone worried about liability, let
> alone the quality of the information they provide. FWIW, the biggest
> problem that academics have with the Internet in general, and Wikipedia in
> particular is that it can't be verified and authenticated.
>
You say this as though academics in general have this problem with the
Internet. That's very far from being true. The Internet certainly
facilitates anonymous communication, but many if not most academics
see this as a good thing.
> Since it is already possible to restrict editing mediawiki to regisistered
> users, seems like a simple, useful thing to add authentication of the email
> address.
>
I agree. It'd be a useful feature. And according to Rob Church it's
a feature already in the system. It's not the default, because
mediawiki is *wiki* software, and it's not a very wiki-like thing to
restrict editing.
> I apologize if this is really off topic for this list -- but you kind of
> brought up the subject by assuming that Mischa was against 'open' editing.
> I don't know what his wiki is about or what his policies are, but I don't
> think enforcing a valid email address conflicts with 'open editing.'
>
> Kent
I don't see how it's not obvious how enforcing a valid email address
conflicts with "open editing". In one instance, anyone can edit
without restriction. In the other, people can only edit after they
have had someone "approve their email address". That the former is
more "open" than the latter falls pretty much from the definition of
openness, "Accessible to all; unrestricted as to participants". This
isn't a value judgement as to whether closed or open is better. It's
just a fact that wikis (at least historically) try to be as open as
possible.
Anthony
I just did something very similar for my company. Here's my circumstances, and how I did it. Hope it helps.
I have a situation where the user name is known by apache before I log on. I can get the user name from Apache. This means something that may be unique to my situation- when the user gets to my page, he is already logged in.
Logins are all handled by the User::loadFromSession function. It returns a user object, or a blank user if not logged in. My solution was simple- anytime it returned a new User();, I had it instead return the results of a new function- loadFromOutside()
loadFromOutside takes the user name, and goes
$user=User::newFromName($name)
If(0==$user->getID){
$user->addToDatabase();
$user->setPassword($pass);
$user->setEmail($email);
$user->setReadName($name);
$user->setOption('rememberPassword',1);
Else{
$user->loadFromDatabase();
}
$user->setCookies();
$user->saveSettings();
Return $user;
What this does is try and load the user from the DB. If it can't, it creates a new user. This code *is* working. The only think you need to do is fill in $name, $pass, and $email. If you don't get a password from the server, randomizing one is fine- they never need it.
Gabe
-----Original Message-----
From: mediawiki-l-bounces(a)Wikimedia.org [mailto:mediawiki-l-bounces@Wikimedia.org] On Behalf Of Chris McIntosh
Sent: Wednesday, November 16, 2005 10:09 AM
To: mediawiki-l(a)Wikimedia.org
Subject: [Mediawiki-l] Intranet Single Signon
I am modifying the source code to allow our internal Intranet users to automatically log in to the wiki based on their username applied by apache.
I do this by using mod_ntlm to get their NTLM credentials and then want to seemlessly log them in.
The problem I am having is setting up the user variable (wgUser) properly. I have tried the following.
For now I have it near the bottom of Setup.php just to test around line 300.
if ( $wgUseRemoteUser)
{
if ($userid = $wgUser->idFromName($wgIP)) { $wgUser->setId($userid); $wgUser->loadFromDatabase(); } else { $wgUser = $wgUser->newFromName($wgIP); $wgUser->setId($wgUser->getMaxId());
$wgUser->addToDatabase();
}
$wgUser->setToken() ;
$wgUser->setCookies();
}
The problem with this approach is I can't change any preferences for this user. Everything else seems fine but if I try and change a setting like Underline links, the preference page won't save. I have tracked that down to the edit token not being set properly, but I am not sure how to set it. If I remove the check in SpecialPreferences where it calls matchEditToken then everything works fine.
Any advice?
Thanks
Chris McIntosh
_______________________________________________
MediaWiki-l mailing list
MediaWiki-l(a)Wikimedia.org
http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
I would like to operate a MediaWiki installation that has two points of
failure instead of the one that you get with a MySQL master/slave setup.
Is it possible to run MediaWiki using a MySQL cluster as its database
storage engine?
If this can't be done, why? What would need to be changed to allow
hosting on a MySQL cluster to be doable? If it can be done, what are
the drawbacks to doing it and why doesn't WikiPedia operate a MySQL
cluster instead of a master/slave replication setup.
Gregory Szorc
gregory.szorc(a)case.edu
We got this working by using IIS to map a virtual directory to a directory
in our file system.
eg. A virtual directory "docs" in mapped to c:\docs
To access the file c:\docs\abc.txt from the mediawiki interface we then
use [{{SERVER}}/docs/abc.txt abc.txt]
Works well and we use NTFS file permissions to restrict access to sensitive
files to authorised users.
We couldn't use file:// as most browsers block that by default now.
Cheers,
Al.
-----Original Message-----
From: Reiser, Markus [mailto:Markus.Reiser@automation.siemens.com]
Sent: Monday, 5 December 2005 11:26 p.m.
To: mediawiki-l(a)Wikimedia.org
Subject: [Mediawiki-l] link to windows network drive possible ?
Hi folks,
is there a possibility in MediaWiki to create an external link to a windows
network folder like
\\server\folder1 ????
It does not work using syntax of external or internal links ;-(
Hope you can help me !
Thanks
Markus
_______________________________________________
MediaWiki-l mailing list
MediaWiki-l(a)Wikimedia.org
http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
http://meta.wikimedia.org/wiki/MediaWiki_FAQ#Is_it_somehow_possible_to_u
se_a_.22file.22_URI-qualifier_for_local_intranets_e.g._.5Bfile:.2F.2Floc
alhost.2FC:_C-Drive.5D.3F
Turns out it's in the fantastic manual! I don't have time to try it out
right now but when I do I'll let you know my results.
-----Original Message-----
From: mediawiki-l-bounces(a)Wikimedia.org
[mailto:mediawiki-l-bounces@Wikimedia.org] On Behalf Of Ben Arnold
(DSLWN)
Sent: Tuesday, 6 December 2005 11:06 a.m.
To: MediaWiki announcements and site admin list
Subject: RE: [Mediawiki-l] link to windows network drive possible ?
Normally you'd be able to do this with a file URL.
[file://server/folder1 the text to link from]
Notice how the Windows backslashes become slashes in a file URL.
This doesn't seem to work on MediaWiki. This is probably a good thing in
general since there's not much use for it outside of a shared
filesystem. It could also be a security risk.
Others might be able to tell you how to hack MediaWiki to get this to
work. If you find out, let me know. I'd be interested in doing this on
my wiki too.
-----Original Message-----
From: mediawiki-l-bounces(a)Wikimedia.org
[mailto:mediawiki-l-bounces@Wikimedia.org] On Behalf Of Reiser, Markus
Sent: Monday, 5 December 2005 11:26 p.m.
To: mediawiki-l(a)Wikimedia.org
Subject: [Mediawiki-l] link to windows network drive possible ?
Hi folks,
is there a possibility in MediaWiki to create an external link to a
windows network folder like
\\server\folder1 ????
It does not work using syntax of external or internal links ;-(
Hope you can help me !
Thanks
Markus
_______________________________________________
MediaWiki-l mailing list
MediaWiki-l(a)Wikimedia.org
http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
_______________________________________________
MediaWiki-l mailing list
MediaWiki-l(a)Wikimedia.org
http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
I have a few quick questions about the 1.5 database schema...
What exactly is the role of the recentchanges table? If I had to take a
stab at it, I would say that it is basically rehash of data already in
the revision and logging tables and it exists purely for performance
improvement reasons.
Once upon a time when I upgraded MediaWiki, somehow my recentchanges
table got truncated. So now, I have records starting at about
rc_id=4000. I do have database backups that have all but 30 or so of
the old records. Is there a benefit to importing these missing records
into the recentchanges table? I would assume
maintenance/rebuildrecentchanges.php would reconstruct these records,
but it doesn't. It just seems to truncate the table even more. Which
leads me back to my original question, what is the purpose of this table?
Second, I did a fresh install of 1.5.2 this weekend and chose the
experimental MySQL 5 layout. For curiosity sake, I did a structure
compare to an existing installation (1.5.2 upgraded from 1.4.x). I was
surprised to see that the text table in the fresh install only has 3
fields (old_id, old_text, old_flags) as opposed to the 11 or so that the
existing install has. Is it safe to delete these non-existent fields
from the old database? On quick glance, these fields in the old
database don't seem to be populated anymore, so I would assume yes, but
what do I know.
I'm sorry to bother everyone on this list with this question, but the
database documentation on meta is horribly out of date. I would update
it myself, but there are a few areas that I just don't know enough
about. Perhaps the developers could find time to update the
documentation...
Gregory Szorc
gregory.szorc(a)case.edu
Is there an easy way to shift certain special pages to only be
administrator accessible? I'm specifically interested in making the
recent changes private.
(No, I'm not interested in removing it from the sidebar.. that's been
done. I also maintain a manual change news page)
Hi,
One simple inquire: can I use .htaccess on any folder or it has to be placed
in the root folder? Or it can be set up to be used in one or other way?
Thanks, mauro
-----------------------
Server: * PHP Version 4.3.11-dev;
* Mediawiki: 1.5.2;
* shared hosting account with www.Godaddy.com,
on Linux/Apache 1.3.33
Client station: * Win XP Home Edition SP2;
* Browser FireFox;
* Extensions: Wikipedia 0.5.2 + Google Bar.
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.362 / Virus Database: 267.13.10/189 - Release Date: 11/30/2005