How can I make the "Real Name" (or email address for that matter) a requirement when people are creating accounts?

I took a look at SpecialUserlogin.php and templates/Userlogin.php but, I couldn't figure it out (my PHP is not strong)

On 09/07/07, jidanni@jidanni.org jidanni@jidanni.org wrote:

K> How can I make the "Real Name"

All I know is I do $wgEnableEmail=$wgEnableUserEmail=$wgAllowRealName=false; to protect users _against_ leaving their real names and addresses in my politically sensitive http://radioscanningtw.jidanni.org/ , assuming that it might be tapped/eavesdropped/confiscated by the authorities one day.

Great, waste his time by posting the complete anti-solution to his question?

With respect *to the question*, it's not possible out of the box, although you could fairly easily hack the code so that form submission required entry of a real name. This isn't necessarily something we'd want in core, however.

Rob Church

I would look at SpecialUserLogin.php in the includes directory.

I am on 1.10.0 so take these line number references as needed ..

In SpecialUserLogin.php around line 201 is a function addNewAccountInternal(). After the global statements the first bit looks to be sure that the 'domain' in the email is good. If not it kicks it out.

So as a test I added this

##DSIG if( $this->mDomain == '' ) { $this->mainLoginForm( wfMsg( 'wrongpassword' ) ); return false; }

Which is basically the same code except that I am looking at the domain and seeing if it is empty. This forces the process to kick out a null email (no domain no valid email).

You could do the same thing with name and other fields as required.

Note: If you make these changes you will also need to remove the text at the bottom of the create form that says these fields are not required.

This could be made as an extension so that a switch in the localsettings would enable/disable this feature.

Hope this helps

DSig David Tod Sigafoos | SANMAR Corporation PICK Guy 206-770-5585 davesigafoos@sanmar.com

-----Original Message----- From: mediawiki-l-bounces@lists.wikimedia.org [mailto:mediawiki-l-bounces@lists.wikimedia.org] On Behalf Of KAndreou@rccl.com Sent: Tuesday, July 10, 2007 5:25 To: MediaWiki announcements and site admin list Subject: Re: [Mediawiki-l] Require real name?

Thanks Rob, that's what I figured and I agree that in the core we wouldn't want it set by default but, wouldn't you agree it would be nice to have it as a flag?

In any case, were would I make the change to make it a requirement?

mediawiki-l-bounces@lists.wikimedia.org wrote on 10-07-2007 04:00:06:

On 09/07/07, jidanni@jidanni.org jidanni@jidanni.org wrote:

...

K> How can I make the "Real Name"

All I know is I do $wgEnableEmail=$wgEnableUserEmail=$wgAllowRealName=false; to protect users _against_ leaving their real names and addresses in my politically sensitive http://radioscanningtw.jidanni.org/ , assuming that it might be tapped/eavesdropped/confiscated by the authorities one day.

Great, waste his time by posting the complete anti-solution to his

question?

With respect *to the question*, it's not possible out of the box, although you could fairly easily hack the code so that form submission required entry of a real name. This isn't necessarily something we'd want in core, however.

Rob Church

---

MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l

_______________________________________________ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l

Glad it worked for you

DSig David Tod Sigafoos | SANMAR Corporation PICK Guy 206-770-5585 davesigafoos@sanmar.com

-----Original Message----- From: mediawiki-l-bounces@lists.wikimedia.org [mailto:mediawiki-l-bounces@lists.wikimedia.org] On Behalf Of KAndreou@rccl.com Sent: Tuesday, July 10, 2007 11:08 To: MediaWiki announcements and site admin list Cc: MediaWiki announcements and site admin list; mediawiki-l-bounces@lists.wikimedia.org Subject: Re: [Mediawiki-l] Require real name?

Thanks, that was it

I added this snippet: if( $this->mRealName == '' ) { $this->mainLoginForm( wfMsg( 'wrongrealname' ) ); return false; }

I also created the message "wrongrealname" to provide the right error message

mediawiki-l-bounces@lists.wikimedia.org wrote on 10-07-2007 11:07:37:

I would look at SpecialUserLogin.php in the includes directory.

I am on 1.10.0 so take these line number references as needed ..

In SpecialUserLogin.php around line 201 is a function addNewAccountInternal(). After the global statements the first bit looks to be sure that the 'domain' in the email is good. If not it kicks it out.

So as a test I added this

##DSIG if( $this->mDomain == '' ) { $this->mainLoginForm( wfMsg( 'wrongpassword' ) ); return false; }

Which is basically the same code except that I am looking at the

domain

and seeing if it is empty. This forces the process to kick out a null email (no domain no valid email).

You could do the same thing with name and other fields as required.

Note: If you make these changes you will also need to remove the text

at

the bottom of the create form that says these fields are not required.

This could be made as an extension so that a switch in the

localsettings

would enable/disable this feature.

Hope this helps

DSig David Tod Sigafoos | SANMAR Corporation PICK Guy 206-770-5585 davesigafoos@sanmar.com

-----Original Message----- From: mediawiki-l-bounces@lists.wikimedia.org [mailto:mediawiki-l-bounces@lists.wikimedia.org] On Behalf Of KAndreou@rccl.com Sent: Tuesday, July 10, 2007 5:25 To: MediaWiki announcements and site admin list Subject: Re: [Mediawiki-l] Require real name?

Thanks Rob, that's what I figured and I agree that in the core we wouldn't want it set by default but, wouldn't you agree it would be nice to

have

it as a flag?

In any case, were would I make the change to make it a requirement?

mediawiki-l-bounces@lists.wikimedia.org wrote on 10-07-2007 04:00:06:

...

On 09/07/07, jidanni@jidanni.org jidanni@jidanni.org wrote:

...

K> How can I make the "Real Name"

All I know is I do $wgEnableEmail=$wgEnableUserEmail=$wgAllowRealName=false; to protect users _against_ leaving their real names and addresses

in

...

...

my politically sensitive http://radioscanningtw.jidanni.org/ , assuming that it might be tapped/eavesdropped/confiscated by the authorities one day.

Great, waste his time by posting the complete anti-solution to his

question?

...

With respect *to the question*, it's not possible out of the box, although you could fairly easily hack the code so that form

submission

...

required entry of a real name. This isn't necessarily something we'd want in core, however.

Rob Church

---

MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l

---

MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l

---

MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l

_______________________________________________ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

KAndreou@rccl.com wrote:

I've installed the latest version of ImageMagick and I've set the appropriate flags in LocalSettings.php: $wgUseImageMagick = true; $wgImageMagickConvertCommand = "/usr/local/bin/convert"; $wgUseImageResize = true;

But, on every image that is resized, I get this error:

Error creating thumbnail: convert: no decode delegate for this image format `/wwwroot/htdocs/mediawiki/images/5/5f/Image1.jpg'.

Sounds like your ImageMagick installation is broken, missing JPEG support. Try recompiling and ensure that JPEG support is included?

- -- brion vibber (brion @ wikimedia.org)

mediawiki-l-bounces@lists.wikimedia.org wrote on 10-07-2007 16:44:11:

mediawiki-l-bounces@lists.wikimedia.org wrote on 10-07-2007 16:24:01:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

KAndreou@rccl.com wrote:

...

I've installed the latest version of ImageMagick and I've set the appropriate flags in LocalSettings.php: $wgUseImageMagick = true; $wgImageMagickConvertCommand = "/usr/local/bin/convert"; $wgUseImageResize = true;

But, on every image that is resized, I get this error:

Error creating thumbnail: convert: no decode delegate for this image

...

...

format `/wwwroot/htdocs/mediawiki/images/5/5f/Image1.jpg'.

Sounds like your ImageMagick installation is broken, missing JPEG support. Try recompiling and ensure that JPEG support is included?

• -- brion vibber (brion @ wikimedia.org)

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGk+rhwRnhpk1wk44RAhzSAJ4jY/+Jwg0i7aTJGK21cWMj1mdBWQCg1Xhr H7ODKSM955YQUKUW4vBC4OU= =Gxo2 -----END PGP SIGNATURE-----

---

MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l

It was configured with JPEG (and other image) support. I get the same error with PNG files and GIFs etc.

I just noticed that the "delegates.xml" file does not contain entries

for

any of these file types. Is this normal? I saw that the one on the ImageMagick website also doesn't have it. _______________________________________________ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l

Ok, I figured out the problem

Apparently, to properly install jpeg-6b you have to do both make install and make install-lib

hope this helps somebody else

Feel free to, obviously it would never be included in the MediaWiki codebase as deleting a user and thus their contributions contravenes the GFDL.

On 09/07/07, Jet jet123.jet123@gmail.com wrote:

I think the developers should design a Deleteuser extension for MediaWiki.

On 7/9/07, Gary Kirk gary.kirk@gmail.com wrote:

...

The short answer is that you shouldn't delete users. If a user has registered an offensive username or something and this is why you want them deleted, you can install the Renameuser extension - search mediawiki.org for Extension:Renameuser.

On 09/07/07, G. Carter gcarter2000@gmail.com wrote:

...

I know as WikiSysop I can block users. However can I delete a user at

the

...

...

MediaWiki level?

Thanks _______________________________________________ MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l

-- Gary Kirk

---

MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l

---

MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Jet schrieb:

I think the developers should design a Deleteuser extension for MediaWiki.

Not gonna happen. Deleting a user is very touchy business. Consider if the user had existing contributions--to whom would they be attributed after deletion? What if he's been blocked or has either log entries pertaining to him? Do they simply vanish, get attributed to someone else, or what?

Renameuser is about the closest we have to "deleting" a user (other than scrubbing the db to remove him), and it seems more than sufficient for this purpose.

- -- Daniel Cannon (AmiDaniel)

http://amidaniel.com cannon.danielc@gmail.com

I've been thinking about this. I think the best solution is to allow the deletion of a user, with all of the user's edits assigned to a single special user (say, "Trash" or "Junk" or whatever). That way, the references all over wiki would be intact, i.e. they would still point to somewhere (in this case, the special user) and there would be no need to rename dozens or hundreds of accounts to things like "renamed-spammer-1" - the deletion script/specialpage would do the reassignment automagically.

Filip

On 09/07/07, Jet jet123.jet123@gmail.com wrote:

I think the developers should design a Deleteuser extension for MediaWiki.

I think you should first read the archives of this mailing list, particularly with respect to what's been said about deleting rows out of tables, before you start making silly comments like this.

Rob Church

On 11/07/07, Ashley Price (asprice) asprice@cisco.com wrote:

Hi Everyone, I was wondering if anyone knows what section of the code and/or where to find the code that determines whether or not to generate a Table of Contents and then generates the TOC if required? I have hopes to actually put the table of contents into a portlet (like navigation and the toolbox are) -Ashley

TOCs are auto-generated when 4 or more ==headings== exist, I believe. You can force a TOC to appear on a page by inserting the magic word __TOC__ (this will put the TOC wherever you put that magic word)

and likewise you can force a TOC to not appear on a page by inserting the magic word __NOTOC__

Apparently there is also __FORCETOC__. From http://meta.wikimedia.org/wiki/Help:Section#Table_of_contents_.28TOC.29

It's possible for users to turn off TOCs in their preferences - the 'showtoc' option ("Show table of contents (for pages with more than 3 headings)": default is enabled==yes) under 'Misc'.

I think you'll find it tricky to put the TOC into the sidebar like the navigation and toolbox. You can put it to the side by inserting

<div align="right"> __TOC__ </div>

on each page (or putting this in an appropriate template, and using it on each page).

cheers Brianna

On 10/07/07, Ashley Price (asprice) asprice@cisco.com wrote:

Hi Everyone, I was wondering if anyone knows what section of the code and/or where to find the code that determines whether or not to generate a Table of Contents and then generates the TOC if required? I have hopes to actually put the table of contents into a portlet (like navigation and the toolbox are)

The Parser is responsible for generating the table of contents, using magic words present on the page to override this behaviour, e.g. __TOC__, __FORCETOC__ and __NOTOC__. Tables of content are generated for all users, and suppressed for those users who don't want them using CSS.

The actual table is generated in Parser::replaceHeadings(), although there are various other little bits of code dotted around which handle the above magic words, e.g. setting placeholders if the position is being overridden, or if a table is being suppressed for the whole page, etc.

Rob Church

But Web sites such like Google and Yahoo can delete users.

Google and Yahoo are not wikis, they don't have history pages that list contributors. The closest you get is their forums - what do they do with forum posts when you delete your account?

Agreed. The best approach would be to rename the user to some kind of "username-removed" and block it indefinitely.

This discussion around deleting/renaming got me thinking. Is a history kept of user renames?

mediawiki-l-bounces@lists.wikimedia.org wrote on 09-07-2007 16:13:13:

The main problem with deleting users is that it breaks all of their contributions. Every contribution is made by a user - I don't know if the code could handle that user not existing.

---

MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Jet schrieb:

I don't think so. these Web sites like Yahoo! do delete users.

Jet, you're not listening. Yahoo, Google, MySpace, etc., can delete users because they don't have to worry about preservation of page-histories, accreditation of contributions, GFDL-compliance, or anything of the sort. MediaWiki is a wiki, not a webforum; what works on a forum or a blog does not necessarily work on a wiki.

- -- Daniel Cannon (AmiDaniel)

http://amidaniel.com cannon.danielc@gmail.com

It doesn't appear to be part of the standard installation. I would guess simple implementation would be to create a trigger on the User table that will fire on update and insert the before value into a history table.

mediawiki-l-bounces@lists.wikimedia.org wrote on 09-07-2007 16:47:05:

Isn't there a Special:Log/rename ? That extension is disabled on Xinki wikis at the moment so I can't check myself.

On 09/07/07, KAndreou@rccl.com KAndreou@rccl.com wrote:

...

Agreed. The best approach would be to rename the user to some kind of "username-removed" and block it indefinitely.

This discussion around deleting/renaming got me thinking. Is a history kept of user renames?

mediawiki-l-bounces@lists.wikimedia.org wrote on 09-07-2007 16:13:13:

...

The main problem with deleting users is that it breaks all of their contributions. Every contribution is made by a user - I don't know

if

...

...

the code could handle that user not existing.

---

MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l

---

MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l

-- Gary Kirk

---

MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l