User talk:Aaron Schulz/archive 1


 * I've copied across the three files for Extension:CheckUser into my extensions folder, but when I go to Special:Userrights, the Available group 'checkuser' does not appear. Any suggestions?
 * It would nice if future versions could look-up a user's email address too. -- Ian --84.9.191.165 19:55, 23 February 2007 (UTC)
 * Two things. First, the patch for the newer version (which will be on svn soon) is here. Second, make sure that you add "include_once('extensions/CheckUser/CheckUser.php');" to localsettings.php (assuming you put it in the extension directory). Voice of All 21:08, 23 February 2007 (UTC)
 * Thanks for the quick reply. Indeed I had omitted the "include_once", however, I am now getting an error
 * "Warning: main(/home/752/knowhow/www.plasma-universe.com/public_html/extensions/../ExtensionFunctions.php): failed to open stream: No such file or directory in /home/752/knowhow/www.plasma-universe.com/public_html/extensions/CheckUser.php on line 18"
 * And I can't find any occurrence of ExtensionFunctions.php --84.9.191.165 00:31, 24 February 2007 (UTC)
 * ExtensionFunctions.php should be where localsettings.php is. Make sure that you have latest version of MW.Voice of All 19:09, 25 February 2007 (UTC)

proposal
I suggest a proposal to Pathoschild in metawiki and he guide me to here for Aaron Schulz. further, I suggest another proposal about speed deleting in en.wiki. if anyone will answered to me and want to talk with me about them, write a message in my talk page at fa.wiki. best regards,--Gordafarid 19:06, 17 June 2007 (UTC)
 * Hmmm, I'm not sure how to get that data from users in an efficient and non-obtrusive fashion. Aaron 23:07, 17 June 2007 (UTC)
 * I`m not professional in software science, but heard that admins in the forums use the cookies for adding that extra hardware informations. it maybe not be necessary for en.wiki, but in fa.wiki is enforceability for disturb the bad bands. if you can do it, that`s very well. regards,--Gordafarid 15:04, 19 June 2007 (UTC)

DeletedContributions
Dear VoiceOfAll,

I was thinking of adding a README file to DeletedContributions extension. I created the file, but didn't feel bold enough to submit it as a patch. I'm pasting it here, so you could add it to the SVN if you liked:

DeletedContributions is an extension for MW 1.8 that adds a Special:DeletedContributions page to MediaWiki (see bug 1699).

This page shows all deleted contributions by a user. This page shows the information only to users with the "delete" right, typically members of sysop group. It looks similar to Special:Contributions.

Each entry has, in this order:

- The date - The link to all deleted revs for the page - A link to the specific deleted revision - An m for minor edits - The edit summary

Prerequisites
Run the following SQL query to add a user index to the archive table (deleted revisions) if you are using a version of MediaWiki older than 1.11:

ALTER TABLE `mw_archive` ADD INDEX `usertext_timestamp` ( `ar_user_text`, `ar_timestamp` )

Note, your prefix may not be 'mw', use the appropriate one.

This index is required by the extension. It can be modifidied otherwise, but doing so is not recommended for larger wikis.

Regards, Huji 10:26, 7 July 2007 (UTC)

ConfirmAccount
Hi Aaron, I just wanted to pop in say thanks for the great ConfirmAccount extension. :-) -- Sayuri 18:02, 17 July 2007 (UTC)
 * Thanks. I noticed, though, that this interface is a bit out of date. Aaron 05:27, 18 July 2007 (UTC)

ConfirmAccount
Hi Aaron, I'm experiencing problems with ConfirmAccount Extension. First it didn't find the file ExtensionFunctions.php. i download one and was wrong with it. So i searched again on the net and i found a file that seems to be OK. Now, when i try to connect to mediawiki it says : 404 page Not Found!!!! Really Funny. Any help please.??

ConfirmAccount Extension & Blank Page
Hi Aaron, all I get, as soon as I enable the ConfirmAccount-Extension, is a blank page. I'm on
 * MediaWiki: 1.10.1 (r24786)
 * PHP: 5.0.4 (apache2handler)
 * MySQL: 4.1.13

I have created the tables. Any hints? --Mzeecedric 14:15, 14 August 2007 (UTC)
 * Enable error_reporting for PHP, I don't get blank screens on the sites I've tested it on. Aaron 18:32, 14 August 2007 (UTC)
 * Thanx, I've done that. I get an open_basedir restriction.

PHP Warning: main [function.main]: open_basedir restriction in effect. File(/usr/share/php5/ConfirmAccount.i18n.php) is not within the allowed path(s): (/srv/www/vhosts/domain/httpdocs:/tmp) in /srv/www/vhosts/domain/httpdocs/wiki/extensions/ConfirmAccount/SpecialConfirmAccount.php on line 39 [client 89.49.229.19] PHP Warning: main(ConfirmAccount.i18n.php) [function.main]: failed to open stream: Operation not permitted in /srv/www/vhosts/domain/httpdocs/wiki/extensions/ConfirmAccount/SpecialConfirmAccount.php on line 39

PHP Fatal error: main [function.require]: Failed opening required 'ConfirmAccount.i18n.php' (include_path='/srv/www/vhosts/domain/httpdocs/wiki:/srv/www/vhosts/domain/httpdocs/wiki/includes:/srv/www/vhosts/domain/httpdocs/wiki/languages:.:/usr/share/php5') in /srv/www/vhosts/domain/httpdocs/wiki/extensions/ConfirmAccount/SpecialConfirmAccount.php on line 39 Line 39 is require_once( 'ConfirmAccount.i18n.php' ); Do you have an idea how to solve this? Or do I have to change the basedir restrictions on my server? --Mzeecedric 11:30, 15 August 2007 (UTC)

Hi Aaron, this is what I had to change to avoid the php errors listed above. Have a look at the diff:

--- ConfirmAccount_new/SpecialConfirmAccount_new.php	Wed Aug 22 20:15:22 2007 $wgGroupPermissions['bureaucrat']['confirmaccount'] = true;
 * ConfirmAccount/SpecialConfirmAccount.php	Wed Aug 22 20:22:31 2007
 * 36,43 ****
 * 36,43 ****

# Internationalisation - require_once( 'ConfirmAccount.i18n.php' );

function efLoadConfirmAccountsMessages { global $wgMessageCache, $wgConfirmAccountMessages;

--- 36,43  $wgGroupPermissions['bureaucrat']['confirmaccount'] = true;

# Internationalisation + require_once dirname (__FILE__). '/ConfirmAccount.i18n.php' ; function efLoadConfirmAccountsMessages { global $wgMessageCache, $wgConfirmAccountMessages;

# Register special page if ( !function_exists( 'extAddSpecialPage' ) ) { ! 	require( dirname(__FILE__) . '/../ExtensionFunctions.php' ); } # Request an account extAddSpecialPage( dirname(__FILE__) . '/ConfirmAccount_body.php', 'RequestAccount', 'RequestAccountPage' ); --- 70,81  # Register special page if ( !function_exists( 'extAddSpecialPage' ) ) { ! 	if (is_file(dirname(__FILE__). '/../ExtensionFunctions.php')){ ! 		require( dirname(__FILE__) . '/../ExtensionFunctions.php' ); ! 	} ! 	else { ! 		die ('ExtensionFunctions.php required! See http://www.mediawiki.org/wiki/Manual:Extensions#Installing_an_extension'); ! 	} }  # Request an account extAddSpecialPage( dirname(__FILE__) . '/ConfirmAccount_body.php', 'RequestAccount', 'RequestAccountPage' );
 * 70,76 ****
 * 70,76 ****

All changes are based on your Revision 25064. --Mzeecedric 18:37, 22 August 2007 (UTC)
 * I've modified the file requiring lines a tad. Aaron 00:18, 23 August 2007 (UTC)

Improving the Documentation
In the current documentation, it says: "Older versions of MediaWiki may not show the link to Special:RequestAccount at the user login form. You can edit MediaWiki:loginprompt to remedy this.:

However, there is no information about how to edit the MediaWiki:loginprompt. This should be added, because otherwise the entire extension is really not very useful for installations which get this error.

Extension:FlaggedRevs - Not technically a page action
True enough. Do you have a recommendation for an implementation type? Or do you feel that you have used so many different techniques to pull Extension:FlaggedRevs together that this is really a general user interface extension and shouldn't be subcategorized beyond user interface? Egfrank 04:57, 18 September 2007 (UTC)
 * I'm wondering if we need a "review" implementation type - is this really an implementation type? Egfrank 11:57, 18 September 2007 (UTC)

Extension:FlaggedRevs with diffenrent groups
Hi, will it be possible to make different groups that can review and validate different articles? I just can read that groups can validate and review every article. But I want some special right.

For example:
 * Group A can review every Article in Category B but not in Category C
 * Group B can validate every Article in Category C but not in Category A

Is that possible? Would be helpfull for zertification. You can mail me here if you want. --GKittlaus 07:42, 25 September 2007 (UTC)
 * Too much complexity, not really worth coding. Aaron 23:13, 25 September 2007 (UTC)