Extension talk:ConfirmAccount/LQT Archive 1


 * Archive 1
 * Archive 2

Misc Bugs
--84.63.27.64 12:22, 19 March 2011 (UTC)
 * In MySQL acr_bio and acd_bio may not be null, but empty bios are stored as NULL -> change table definition (done locally) or save 'em as empty strings
 * acr_email's type is tinytext although it's stored in a index -> change to varchar
 * In i18n: it's de_formal - not de-formal
 * Wishlist: Add support for disabling biographie

Some clarifying instructions for noobs because that's basically what I am.

 * If you don't see the file ConfirmAccount.php in the folder /ConfirmAccount but you see instead SpecialConfirmAccount.php, make sure you download the Development Version instead of 1.16x version.
 * Many shared web hosting accounts will not give you shell access to run update so you need to import ConfirmAccount.sql using phpMYAdmin. But if you are using a database prefix, you must first edit this file using notepad.
 * I use MW_ as a prefix so I made the following changes: CREATE TABLE mw_account_requests and down further in the file: CREATE TABLE mw_account_credentials.
 * -If it's cPanel based hosting, you usually have access to cronjobs. Set a temporary cronjob to run say, every five minutes, for the update.php script. Let it run and then disable the cronjob again. This is a slightly cleaner way than requiring the manual editing of the sql file. Ashimema (talk) 08:18, 11 April 2012 (UTC)


 * Now go to phpMYAdmin, select your database so it shows on the top as localhost > yourdb_name.
 * Note the number of records in this database. It will increase by 2 if you are successful.
 * Click the import tab and browse to your local folder where you have modified your ConfirmAccount.sql file and import.
 * Now go to the structure tab and you should see the two new files created as mw_account_requests and mw_account_credentials if your prefix is mw_.

Once installed correctly, account creators will see a new screen when they click create account. Users will no longer be able to create accounts directly but must request an account. This is nothing more than an email confirmation. No admin action is required at this point. A confirmation email will be sent to the user and when the user confirms, the user will be placed in a approval list which must be acted on by an admin. Once the account is approved, the user will be sent another email confirming the account creation.

Personally, I think these steps are too demanding and intrusive and will drive away registered users. I recommend turning this on only in rare occasions when your wiki is under a spam attack. As you can see from my block list, I was receiving dozens of spam registrations per day. This extension brought that to a halt immediately.

Error sending mail: mailer error
I can't figure out what this error even means, or where it's coming from. I grep'ed for the text and didn't find anything in the folder containing the ConfirmAccount code. What's the cause of this error? How can I fix it?

155.99.202.108 23:41, 19 October 2010 (UTC)

"efCheckIfAccountNameIsPending failed to return a value; "
Seems like I'm missing something obvious here, but so far not seeing it. Have upgraded wiki to latest release (1.15.4), and re-installed fresh versions of both ConfirmAccount and ConfirmEdit. ReCaptcha is not being used. Here's what I get when a user clicks the "submit" button:

Internal Error Detected bug in an extension! Hook efCheckIfAccountNameIsPending failed to return a value; should return true to continue hook processing or false to abort.

Backtrace:


 * 1) 0 /var/www/w/extensions/ConfirmAccount/RequestAccount_body.php(239): wfRunHooks('AbortNewAccount', Array)
 * 2) 1 /var/www/w/extensions/ConfirmAccount/RequestAccount_body.php(74): RequestAccountPage->doSubmit
 * 3) 2 /var/www/w/includes/SpecialPage.php(559): RequestAccountPage->execute(NULL)
 * 4) 3 /var/www/w/includes/Wiki.php(229): SpecialPage::executePath(Object(Title))
 * 5) 4 /var/www/w/includes/Wiki.php(59): MediaWiki->initializeSpecialCases(Object(Title), Object(OutputPage), Object(WebRequest))
 * 6) 5 /var/www/w/index.php(116): MediaWiki->initialize(Object(Title), NULL, Object(OutputPage), Object(User), Object(WebRequest))
 * 7) 6 {main}

This looks like something reported below that was supposed to be fixed, so I'm assuming I probably have something out of sync, but I can't find it -- any guidance would be most appreciated. On a bit of a deadline here, of course ;)

Thanks!

Ok, got this working ... here's what I had to do with MW 1.15.4 to get it working.

(1) install latest ConfirmEdit.

(2) install latest TRUNK version of ConfirmAccount -- NOT the 1.15 release (this has not been fixed, apparently).

(3) Hand edit the ConfirmAccount.sql file to specify database table prefix, then run maintenance/update.php -- note this is different from install instructions...

(4) follow install instructions for 1.16 -- not 1.15 -- in other words, use the extensions/ConfirmAccount/ConfirmAccount.php in LocalSettings.php, NOT SpecialConfirmAccount.

At this point, every thing seems to be working, will report back if not.


 * Installed 1.15 version on MW1.15, also using manual sql update (step #3), but above error came up. Removed files of CA1.15 and placed files of CA1.16, worked perfectly.
 * Under MW 1.15.5 I get problems with TRUNK and 1.15 BRANCH.  Branch gets above error and trunk fails to show correct login / request register dialog.


 * I'm running Mediawiki 1.15 which still is considered the stable version on Debian Squeeze. I had the same problem with this extension, but then I just installed ConfirmAccount for Mediawiki 1.16 which is working perfectly. Leif B. Kristensen (talk) 23:35, 31 October 2012 (UTC)


 * I fixed this in Squeeze (1.15 + downloaded the extension (corresponding version) from the page). According to error_log, ConfirmAccount/SpecialConfirmAccount.php:247 requires that the user is passed as a reference. The call from extensions/ConfirmAccount/RequestAccount_body.php:239, however, passes the user as a value. I changed this:
 * To this:
 * (note the ampersand before . Probably a compatibility bug. --Felipe Franciosi 17:21, 30 December 2012 (UTC)
 * (note the ampersand before . Probably a compatibility bug. --Felipe Franciosi 17:21, 30 December 2012 (UTC)
 * (note the ampersand before . Probably a compatibility bug. --Felipe Franciosi 17:21, 30 December 2012 (UTC)

Using template on "bio" section"?
Hi! First of all: This extension is great! But I have a little problem. I´m trying to use an existing wiki template on the "bio" section. Is this posible? The goal is that the information that the new users inputs on the bio (and, the template), they can get their "users profiles" almost ready. Thanks!!! --Tango granada 01:04, 5 October 2009 (UTC)

Any ideas??
Same issue, I putzed around with the PHP, but now it loads the 'template' I created at load-time and at submit time, so even if the user requesting the account filled in the details as needed, it gets replaced by the template text.


 * It would be a great feature to add to this extension.. I see it working best as an integration using the hooks availabel in semantic forms. Ashimema (talk) 12:40, 7 August 2012 (UTC)

Bureaucrat's do not have permission to confirm an account.
Permission error when trying to confirm an account with User 'bureaucrat'. I see the file "SpecialConfirmAccount.php", and this has a line of code to configure the group bureaucrats. In file: $wgGroupPermissions['bureaucrat']['confirmaccount'] = true;
 * 1) Grant account queue rights

The account then I try confirm is the admin of wiki. They have bureaucrats group add. So, i have something more to do?

Email sent with password contains line I would like to remove
The email sent out with username and password contains the line "Welcome to the forums. Thank you for your interest in joining our forum." by default. How do I remove this? I've tried looking at MediaWiki:confirmaccount-email-body (2,3,4,5,6) but that line doesn't appear to be present and I would like to remove it. --90.192.146.115 13:06, 26 October 2009 (UTC)

Installing reCAPTCHA with ConfirmAccount
Just a little public service for those trying to do what I've done:
 * 1) Create a private wiki using these guidelines: Manual:Preventing_access
 * 2) Use Extension:ConfirmAccount to set up an account request queue
 * 3) Use Extension:reCAPTCHA to keep the bots from filling up my account request queue

First off, after adding Extension:ConfirmAccount and Extension:reCAPTCHA to my installation, I went to test. Starting at my Main_Page, I clicked log in, then clicked the Create an account link to request an account. But it took me right back to Main_Page. Clearly, not the desired effect. After cursing a little and pondering the meaning of life, I recalled that when I worked on LocalSettings.php to restrict viewing, editing and account creation, those configuration flags included $wgWhitelistRead (see Manual:Preventing_access). Naturally, "Special:UserLogin&type=signup" (usually called "Special:RequestAccount" on standard MediaWiki installs) wasn't in the list. Duh. Added that in to LocalSettings.php, FTP'd it over to the server and voilà! Fixed. Sort of.

After figuring out how to let an anonymous user get to the account request page, I moved on to a more serious issue. I was getting an error on the screen that pointed to Extension:ConfirmEdit as the culprit. The errors looked pretty much like this:
 * Extension_talk:ConfirmAccount

While Extension:reCAPTCHA was installed (but not working), Extension:ConfirmEdit wasn't. The Extension:ConfirmAccount and Extension:reCAPTCHA gurus know this (of course, I didn't), but Extension:reCAPTCHA is really a combination of some .php files from the reCAPTCHA people at Carnegie Mellon University and some other .php files for Extension:ConfirmEdit. You can either run Extension:ConfirmEdit (with it's very basic text CAPTCHA implementation) or the more sophisticated Extension:reCAPTCHA (with graphical CAPTCHAs), but not both.

After much trial n' error, Googling and a piecing together comments HERE, HERE and HERE, I figured out that I needed to use the ConfirmEdit.php file from Extension:ConfirmEdit instead of the file with the same name supplied with the reCAPTCHA download. I also needed to add the ConfirmEdit_body.php file from Extension:ConfirmEdit as this file is not in the Extension:reCAPTCHA package.

I re-downloaded both Extensions just to make sure I had clean, un-edited .php files (I had been experimenting with several files as I did my trial n' error), then replaced the ConfirmEdit.php and ConfirmEdit_body.php files in the Extension:reCAPTCHA package with those from the Extension:ConfirmEdit package. I deleted the /your_wiki's_root/extensions/recaptcha directory on the server, FTP'd over a new /recaptcha directory with the correct files and everything came up as desired.

Hope this helps someone else down the road.

Problems using this with SQLite
I'm having a bear of a time getting this to play nice with an SQLite backend. To start, the .sql script is for MySQL. That is mostly solved except for the account_credentials table having two primary keys, which isn't supported in SQlite.

Then, for some reason none of the database requests work. I can submit a request, it gets committed to the database, but it won't be read/counted properly for some reason.

Anyone got experience using it with SQLite?

Got it working with SQLite
To get this extension working with SQLite, I had to edit ConfirmAccount.sql: CREATE TABLE /*$wgDBprefix*/account_requests (   acr_id INTEGER PRIMARY KEY AUTOINCREMENT,    acr_name varchar(255) NOT NULL default ,    acr_real_name varchar(255) NOT NULL default ,    acr_email tinytext NOT NULL,    acr_email_authenticated BLOB(14) default NULL,    acr_email_token BLOB(32),    acr_email_token_expires BLOB(14),    acr_bio mediumblob NOT NULL,    acr_notes mediumblob NOT NULL,    acr_urls mediumblob NOT NULL,    acr_ip VARCHAR(255) NULL default ,    acr_filename VARCHAR(255) NULL,    acr_storage_key VARCHAR(64) NULL,    acr_type tinyint(255) default 0,    acr_areas mediumblob NOT NULL,    acr_registration char(14) NOT NULL,    acr_deleted bool NOT NULL,    acr_rejected BLOB(14),    acr_held BLOB(14),    acr_user INTEGER NOT NULL default 0,    acr_comment varchar(255) NOT NULL default ,    UNIQUE (acr_name),    UNIQUE (acr_email),    UNIQUE (acr_email_token)  ); CREATE INDEX acr_type_del_reg on /*$wgDBprefix*/account_requests(acr_type,acr_deleted,acr_registration); CREATE TABLE /*$wgDBprefix*/account_credentials (   acd_id INTEGER PRIMARY KEY AUTOINCREMENT,    acd_user_id INTEGER NOT NULL,    acd_real_name varchar(255) NOT NULL default ,    acd_email tinytext NOT NULL,    acd_email_authenticated BLOB(14) default NULL,    acd_bio mediumblob NOT NULL,    acd_notes mediumblob NOT NULL,    acd_urls mediumblob NOT NULL,    acd_ip VARCHAR(255) NULL default ,    acd_filename VARCHAR(255) NULL,    acd_storage_key VARCHAR(64) NULL,    acd_areas mediumblob NOT NULL,    acd_registration char(14) NOT NULL,    acd_accepted BLOB(14),    acd_user INTEGER NOT NULL default 0,    acd_comment varchar(255) NOT NULL default '',    UNIQUE (acd_id)  );

I saved this to a file (e.g., ConfirmAccount_SQLite.sql) and loaded the new tables to the SQLite database with: sqlite3 wikiDB.sqlite < ConfirmAccount_SQLite.sql

To get it working, I also had to make one small edit to the code. Apparently, SQLite doesn't like to set a default value for NOT NULL columns. So, I added this line to the account_requests insert query in RequestAccount_body.php (around line 384):

'acr_deleted' => 0,

I haven't tested everything, but the basic functionality seems to be working now.
 * Updates made to /trunk. Aaron 21:00, 7 April 2011 (UTC)

Problem with "position" titles starting with the same letter
I am experiencing a problem that is preventing me from having the "position" labels starting with the same letter. Basically, you can not have two position titles that start with the same letter. (Example: "Reader" and "Reviewer")

Sample synerio:
 * A user requests an account with the position of "reviewer."
 * Admin navigates to Special:ConfirmAccounts to confirm the pending account.
 * Admin clicks "open requests" for "reviewers" (second queue listed) you are brought to the "readers" queue.

I noticed that the url that you are sent to is represented by the first letter of the position. Example: xxxxx/Special:ConfirmAccounts/r&ShowHeld

NOTE: If there is only one default position group (array is commented out) then you are sent to: xxxxx/Special:ConfirmAccounts/reviewers&ShowHeld

Can the "open request" links be formatted to always use the entire position name, not just the first letter?

Sorry for the over explaining..I know it is a strange sounding problem.

Thanks in advance,

-Dgennaro 21:09, 13 January 2010 (UTC)
 * How did you set $wgAccountRequestTypes? Aaron 21:38, 13 January 2010 (UTC)


 * $wgAccountRequestTypes = array('reader', 'reviewer');


 * Thanks! Works great! -Dgennaro 13:12, 22 January 2010 (UTC)
 * Just for good measuere, I also tried it:


 * $wgAccountRequestTypes[0] = 'reader';


 * $wgAccountRequestTypes[1] = 'reviewer';


 * -Dgennaro 14:28, 14 January 2010 (UTC)
 * I think you want:

Aaron 20:35, 14 January 2010 (UTC)


 * This does not work. And I am not certain why you are putting an array inside another array.
 * -Dgennaro 21:03, 14 January 2010 (UTC)


 * Never mind, I thought you wanted something different. The above code would make a 'reader' queue and the approved users are in the 'reviewer' group. If you want a 'reader' and 'reviewer' queue, then you want:

Aaron 21:29, 14 January 2010 (UTC)

Thanks for this useful example (perhaps add it to the page?). What does autotext do? The note, "The optional autotext value is added to the end of the user page of new accounts" is quite confusing. What is the 'user page of new accounts'? Cheers, excellent extension!--Dmb 10:10, 5 October 2011 (UTC)

Error when confirming email account
I am receiving an HTTP 500 Internal Server Error when a potential user clicks the link provided in the "Email Confirmation" email.

I am running MediaWiki 1.14.0 with ConfirmAccount 1.46 (x1.15).

Any ideas?

Thanks in advance. -Dgennaro 22:18, 21 January 2010 (UTC)


 * I've heard Zend Optimizer can cause 500s. Redirects to invalid URLs can cause thus too. The apache and PHP error logs may have useful info. By the way, did you ever fix the $wgAccountRequestTypes value? Aaron 04:06, 22 January 2010 (UTC)


 * Yes, I did. The advice worked perfect! I must have forgotten to post.


 * I tried using the 1.14x version of ConfirmAccount also with no success. My next step today was to check out the PHP and IIS error logs. I am determined to make this extension work for me! I will post an update with my findings.


 * Just to recap...what is happening is: the user requests an account and they receive an email to confirm their email address and when the user clicks the link within the email they receive a HTTP 500 error, but when I look in the database their email address has been confirmed. This would be fine, but I added the bit of code in that enables the "admin" to receive an email when there is a pending user account for approval...this step is not happening. I am assuming that the HTTP 500 error is not allowing this step to happen since the email confirmation step was not "fully completed." Do you think I am on the right track?


 * Thanks again! -Dgennaro 13:20, 22 January 2010 (UTC)

Problem with latest 1.15 release of ConfirmAccount
I'm getting the following error report: Internal error Detected bug in an extension! Hook efCheckIfAccountNameIsPending failed to return a value; should return true to continue hook processing or false to abort. Backtrace: Herwin 15:58, 8 February 2010 (UTC)
 * 1) 0 /Users/harryerw/Sites/mediawiki/extensions/ConfirmAccount/RequestAccount_body.php(239): wfRunHooks('AbortNewAccount', Array)
 * 2) 1 /Users/harryerw/Sites/mediawiki/extensions/ConfirmAccount/RequestAccount_body.php(74): RequestAccountPage->doSubmit
 * 3) 2 /Users/harryerw/Sites/mediawiki/includes/SpecialPage.php(559): RequestAccountPage->execute(NULL)
 * 4) 3 /Users/harryerw/Sites/mediawiki/includes/Wiki.php(229): SpecialPage::executePath(Object(Title))
 * 5) 4 /Users/harryerw/Sites/mediawiki/includes/Wiki.php(59): MediaWiki->initializeSpecialCases(Object(Title), Object(OutputPage), Object(WebRequest))
 * 6) 5 /Users/harryerw/Sites/mediawiki/index.php(116): MediaWiki->initialize(Object(Title), NULL, Object(OutputPage), Object(User), Object(WebRequest))
 * 7) 6 {main}

The console shows this: PHP Warning: Parameter 1 to efCheckIfAccountNameIsPending expected to be a reference, value given in /Users/harryerw/Sites/mediawiki/includes/Hooks.php on line 117, referer: http://crowan-scat.sunderland.ac.uk/~harryerw/mediawiki/index.php/Special:RequestAccount Herwin 16:09, 8 February 2010 (UTC)
 * The 1.15 version does not have that problem. I just looked at the code. Aaron 18:00, 8 February 2010 (UTC)

I'll do a reinstall Tuesday and see if the problem still exists. Herwin 22:32, 8 February 2010 (UTC)

Done and it now asks for a biography. Let's see... At least the error isn't showing up. Herwin 10:14, 9 February 2010 (UTC)


 * It's fixed in trunk. Liangent 14:38, 20 June 2010 (UTC)

How to let a user edit his biography (that is not confirmed yet)?
I do not really get the meaning of the "Hold" option when confirming account requests. When I choose this option, then an email with the following contents is sent to the email address requesting the account: Before your request for an account "Klaus Mustermann" can be accepted on Wiki you must first provide some additional information.

 Your biography needs editing. Please add your birth date, place, address, etc.

There may be contact lists on site that you can use if you want to know more about user account policy.

Now, assuming that the person wants to edit his/her biography according to my request, how can he/she do it? Is it possible at all? If not, what is the point of the "Hold" option?

Not receiving any email to administrator after the email address is confirmed
Even after setting (either directly in SpeciaConfirmationAccount.php or in LocalSettings.php) : $wgConfirmAccountContact = 'myemail@example.com' That administrator does not receive any email notification once the user confirmed his email address. Looking at the archives, seems like it was a problem already before and there is no answer there.

I am using mediawiki 1.15.2, the extension from 1.15.x branch. Even if I enable debug messages, I don't see it complaining about anything. Help please !


 * I have this same problem, although I am going to try it with an email address rather than the way I have it which is:
 * $wgConfirmAccountContact = true
 * Hbmallin 21:47, 26 January 2011 (UTC)


 * I had the sample problem but I found out that I had to whitelist the page Special:RequestAccount for anonymous users --85.181.85.33 11:25, 2 May 2011 (UTC)


 * I had the same problem because of the following mistake in LocalSettings.php. I used $wgConfirmAccountContact='mymail@mydomain.com'; before require_once("$IP/extensions/ConfirmAccount/ConfirmAccount.php"); . Switching the order solved the problem.--95.89.17.149 02:42, 23 November 2012 (UTC)

Doesn't respect $wgDBprefix
Using trunk as of 2010/04/18 & just wanted to point out, the setup steps are not quite correct.

1. they do not take into account if you are using $wgDBprefix in your settings. I had to run these mysql statements to post-fix: mysql> rename table account_requests to mw_account_requests; mysql> rename table account_credentials to mw_account_credentials;

2. The include in LocalSettings.php is (now) actually require_once("$IP/extensions/ConfirmAccount/ConfirmAccount.php");

—- The missing step that solves #1 above is you have to edit ConfirmAccount/ConfirmAccount.sql and perform a change as the remark there says: (this is actually included within the "Setup" steps as "substituting db prefix")

-- Replace /*$wgDBprefix*/ with the proper prefix

PeterS3 06:52, 23 June 2010 (UTC)

1.15x snapshot missing ConfirmAccount.php
Seems a bit fatal to me. (unsigned by 128.194.196.117 20:19, 21 April 2010)


 * I couldn't agree more. There is no ConfirmAccount.php in the package. Joly 05:10, 28 April 2010 (UTC)

AccountRequestMinWords
$wgAccountRequestMinWords, doesn't work on my wiki 1.15. when i add to Localsettings.php $wgAccountRequestMinWords=20; for example

It writes bio min=20, but really requires 50 words as default.
 * Note that it should be added *after* the "include" call. Aaron 19:59, 29 April 2010 (UTC)

AccountRequestMinWords works well only with english text of Bio but I need russian. How to fix it? --94.51.8.36 14:55, 5 June 2010 (UTC)DrShtopor

Fix
Extension can't count number of words in UTF8. You can fix it this way:
 * ConfirmAccount/business/AccountRequestSubmission.php
 * Find:
 * Replace with:

I used workaround from http://php.net/manual/en/function.str-word-count.php. --Jossmart (talk) 08:30, 12 September 2012 (UTC)

Problem with Special:UserCredentials
The display isn't right! Here is what it looks like:


 * If I go to Special:UserCredentials:
 * the page title shows as &amp;lt;usercredentials&amp;gt;
 * there is a box with the title , and an input field with the title &amp;lt;usercredentials-user&amp;gt;


 * When I type in a username, it goes to the display page:
 * If the user does not exist (or existed before ConfirmAccount was installed - which is only 3 accounts on my wiki) the message reads &amp;lt;usercredentials-badid&amp;gt;
 * If the user does exists and was confirmed, the following is displayed:
 * 

&amp;lt;usercredentials-leg-user&amp;gt;Username: test &amp;lt;usercredentials-email&amp;gt; test@xxxxx.com &amp;lt;confirmaccount-leg-areas&amp;gt; &amp;lt;usercredentials-leg-person&amp;gt;&amp;lt;usercredentials-real&amp;gt; Test Name

&amp;lt;usercredentials-bio&amp;gt; This is the bio provided when signing up &amp;lt;usercredentials-leg-other&amp;gt; &amp;lt;usercredentials-ip&amp;gt; 99.99.99.99

Does anyone know how I can get this to display properly? -- Phantom Steve /talk &#124;contribs \ 09:02, 21 June 2010 (UTC)

doesn't create tables
I have Mediawiki 1.15 running, and am trying to install ConfirmAccount. I substituted the dbprefix, but everytime i try to create an account, I get the message that the table account_requests doesn't exist.

can anyone help me with this?

thnx! --Gallomane 09:55, 22 June 2010 (UTC)
 * In the directory in which you installed ConfirmAccount, there is a file called.

If you are using phpmyadmin, you can import this in to create the tables. Otherwise, here is the SQL code which you need to create the table:

Hope this helps! -- Phantom Steve /talk &#124;<font color="#000080">contribs \ 19:53, 24 June 2010 (UTC)

I replaced the code, substituted the dbprefix again to match what is in my localsettings, but I still get the error: “1146: Table 'admin_anja_wiki.account_requests' doesn't exist (localhost)”. Teruggeplaatst van "http://wiki.familiekock.nl/index.php/Hoofdpagina"

I don't get it! Could it be because I don't really have a dbprefix? It says "" in my localsettings, so I put // in the sql file. --Gallomane 08:59, 28 June 2010 (UTC)

Using version 1.12, I had the same problems, and solved them like this: Then the tables were created, the field and index changes were attempted, and failed gracefully because they were redundant. --Nick Russo 18:12, 10 September 2010 (UTC)
 * create three new files in archives/:
 * patch-account_requests.sql -- contains the CREATE command copied from ConfirmAccount.sql, which never seems to be used
 * patch-acr_del.sql -- contains the INDEX lines from patch-account_credentials.sql
 * patch-acr_type.sql -- contains the ADD lines from patch-account_credentials.sql
 * add three lines to SpecialConfirmAccount.php in the $wgDBtype == 'mysql' section:
 * $wgExtNewTables[] = array('account_requests', "$base/archives/patch-account_requests.sql" );
 * $wgExtNewFields[] = array('account_requests', 'acr_type', "$base/archives/patch-acr_type.sql" );
 * $wgExtNewIndexes[] = array('account_requests', 'acr_type_del_reg', "$base/archives/patch-acr_del.sql" );

MediaWiki:Confirmaccount-welc
Is it possible to pass templates of pages through this page to the user's talk page when an account is created? For example if I wanted to add sections as the welcome to the new user's talk page?

Will the page also handle the and tags? Hutchy68 03:35, 8 August 2010 (UTC)

"biography will be set as default userpage" even though $wgMakeUserPageFromBio=false
(Applies to ConfirmAccount 1.46)

When setting $wgMakeUserPageFromBio to false (meaning "don't set the person's bio as his/her userpage"), the page Special:RequestAccount still claims that "Your biography will be set as the default content for your userpage" (first sentence of box "personal information").

To remove this inconsistency, two files have to be changed in ConfirmAccount 1.46: $form .= wfMsgExt( 'requestaccount-bio-text', array('parse') )."\n"; by global $wgMakeUserPageFromBio; if ( $wgMakeUserPageFromBio ) { $form .= wfMsgExt( 'requestaccount-bio-text1', array('parse') )."\n"; } $form .= wfMsgExt( 'requestaccount-bio-text2', array('parse') )."\n"; The modified file is available at my web site.
 * ConfirmAccount/RequestAccount_body.php: Replace the line
 * ConfirmAccount/ConfirmAccount.i18n.php: The requestaccount-bio-text has to be split into requestaccount-bio-text1 and requestaccount-bio-text2 for all languages. This new version of ConfirmAccount.i18n.php is available at my web site . For a few languages (most notably Chinese) I was not sure where to split the text. In these cases I left requestaccount-bio-text1 empty and renamed requestaccount-bio-text to requestaccount-bio-text2; this way the new version behaves the same as the old one (well, almost, see below).

Note: When $wgMakeUserPageFromBio is true, a line break is inserted between the two parts of the bio-text, which was not there before applying the patch. This is caused by the extra call to wfMsgExt, which wraps p-tags around the text. Maybe some knowledgeable person gets rid of this extra paragraph. Or we declare the new formatting to be the preferred one.
 * Does this have a bug report?Aaron 19:12, 12 September 2010 (UTC)

Invalid Argument in LocalisationCache, line 683
Hi,

upgraded to MW 1.16. and re-installed ConfirmAccount, now I get the error mentionend above - I traced it back to this extension - whenever I disable it in Localsettings everything is fine again. How does this fit? Any help is greatly appreciated THANKS --Fxk2
 * Oha, I activated the extension, fresh snapshot-install and the same error occurs. And the page "Confirm Account Requests" doesn't show up on "Special Pages" - how is that possible? - Any suggestions for solving this problem? PLEASE & Thanks --Fxk2 06:24, 27 April 2011 (UTC)

log of actions other than approval
When an account is not approved, instead being actioned as 'Reject', 'Hold' or 'Spam', these actions should be in a log somewhere, but I can't see a log. I think the log should be private, like the suppression log, and only accessible to people with the permission to approve accounts. Is this an RFE ? John Vandenberg 08:11, 26 October 2010 (UTC)

Internationalisation does not work
Latest SVN code from http://svn.wikimedia.org/svnroot/mediawiki/trunk/extensions/ConfirmAccount (revision 75783) installed in MW1.15.5 produces no internationalisation (i18n) text.

Instead, the raw tags are printed.

It appears the line ... wfLoadExtensionMessages('ConfirmAccount'); ... is missing from __construct in the files ConfirmAccount_body.php and UserCredentials_body.php

Adding this line to both files fixes the problem.
 * You need the 1.15 version of the extension. Aaron 06:39, 28 January 2011 (UTC)

Database error
I followed the first two steps, however was unsure about this step:

''Run maintenance/update.php (run ConfirmAccount.sql if not possible, substituting db prefix and options) mysql -h DB_HOST -u WIKIUSER -p WIKIDB < ConfirmAccount.sql''

I tried a few things however this error still occured.

The error message below would show when you click on "Request Account" on the registration page.

''A database query syntax error has occurred. This may indicate a bug in the software. The last attempted database query was: (SQL query hidden) from within function "efCheckIfAccountNameIsPending". Database returned error "1146: Table ' file in the   folder will run   and create the tables in your database automatically. --Dgennaro 13:54, 31 May 2011 (UTC)

SQL Error 1091
I run update.php and I get this error:

The last attempted database query was: "ALTER TABLE `account_requests` ADD acr_type tinyint(255) default 0, DROP INDEX acr_deleted_reg, ADD INDEX acr_type_del_reg (acr_type,acr_deleted,acr_registration)"

from within function "DatabaseBase::sourceStream". Database returned error "1091: Can't DROP 'acr_deleted_reg'; check that column/key exists (127.0.0.1)"

Lordy lord, this extension has been a nightmare. First I had the SQL error where I had to change the code to ENGINE=InnoDB and now I have this. Any solution?

Someone?

One Issue (Chrome), One request (Group Permission)
Installed extension, took about an an hour to get the extension installed to work. (some of the options set in Localsettings.php need to be in a certain order to work).

Only issue I have is with the Chrome Browser. On the main page, upper right, were it tells you if you have any confirmed accounts waiting for approval. On IE/firefox, the redirect link works, while on the Chrome browser, there is no link at all.

The request I have, is instead off of drop down menau of author/editor, how about a check box series for all available groups. My wiki, i have uploadaccess, editor, user, forumreadonly, and etc groups. This would make creating an account a breeze, instead of having to go to multiple locations on the wiki to setup the account.

Beyond this, great extension, works in MediaWiki 1.16.5/ PHP 5.2.17 (cgi)/ MySQL 5.0.91mm-log / Hosted/Shared server Lynxcub 18:48, 29 July 2011 (UTC)

Request Account Problem
I get the following error, when trying to request an account: Fatal error: Call to undefined method Status::toString in ..\extensions\ConfirmAccount\RequestAccount_body.php on line 375
 * Install the right extension version for your MW version (and sign your posts ;-) --Dmb 13:03, 5 October 2011 (UTC)

I get the same error as the anonymous user is reporting: PHP Fatal error: Call to undefined method Status::toString in XXXX/extensions/ConfirmAccount/RequestAccount_body.php on line 375 This is with ConfirmAccount-MW1.17-r90727.tar.gz, and MediaWiki 1.17, PHP 5.3.2-1ubuntu4.10. -- Hazelnusse Tue Oct 25 00:03:51 UTC 2011

I just tried setting this up and also get the same error :( . Setup using latest versions of xampp and MW/ConfirmAccount extension. Any ideas? -- Ad Tue Oct 25 17:24 UTC 2011
 * Fixed in r100948. Aaron 06:02, 27 October 2011 (UTC)

Question about "option"
the Command of $wgAccountRequestThrottle states that "Count of how many requests can come from an IP address per day. This only matters if throttling is true. [Type: positive integer]."

Question is, what is the command to set the "throttling" to true/false Lynxcub 14:56, 3 August 2011 (UTC)

Questions related to Request Account Tempate and Confimation E-mail
Let me preface this by apologizing for being a complete novice nonetheless I would greatly appreciate help with these issues:

1) On the Special:RequestAccount the user is unable to follow the path to the Terms of Service link how can I open this page to the potential user?

2) How do I edit the phrase "Personal Biography" to something which fits my wiki more appropriately?

3) How do I edit the language contained in the e-mails which are sent to users as a result of creating an account?

Thank you.
 * To answer your questions:
 * 1) use the following command inside your LocalSettings.PHP
 * $wgWhitelistRead = array ( "Main Page", "Special:Userlogin", "Special:RequestAccount", "Special:Login", "XXXX:Terms_of_Service");
 * replace XXXX with whatever comes after /index.php?title= in your titlebar
 * 2) 2 and 3 are the same answer. Go to your SpecialPages, then find System messages.  In the Filter by prefix section search for both requestaccount and confirmaccount.  Look for the items you are wanting to change.  Save and test.  You might need to go in there a few times to change what you need.  There is more than one section with "Biography" Lynxcub

Wonderful. Thank you. -Brad

Forms
I'm wondering if there's been any thoughts on adding support for including extra forms fields in the request form without butchering the php code manually.

There's a number of Form extensions (my personal favourite being SemanticForms so I'm wondering if some sort of compatibility could be added in? Ashimema 17:40, 31 August 2011 (UTC)

$wgPasswordSenderName for admin email
Minor change, but identifies email by admin specified name. Revise RequestAccount_body.php line 330 to: Not a big deal, but perhaps better identifies the email, if $wgPasswordSender is an unusual address.PolicyReformer 21:30, 4 October 2011 (UTC)
 * Added in r99331. Aaron 00:05, 9 October 2011 (UTC)

Check previously confirmed accounts
Hi,

Quick question - how do I check previously accepted accounts and the information that was presented to me at the time of review (IP, email, short description etc.)? Is there a log somewhere?

Thanks Veryhuman 12:16, 5 October 2011 (UTC)
 * Special:UserCredentials. Aaron 23:57, 8 October 2011 (UTC)

Docs bad or a bug...
I'm using http://svn.wikimedia.org/svnroot/mediawiki/branches/REL1_17/extensions/ConfirmAccount

and configuring $wgAccountRequestTypes. I don't find it written anywhere that I need to edit MediaWiki:Requestaccount-level-0 / MediaWiki:Requestaccount-level-1 / etc.

I expected the strings here to come from the array ... "The subpage param (string) is used to separate the queues when browsing Special:ConfirmAccount."

Is this a bug in the docs or in the code?

I found values like 'author', 'editor', '&lt;requestaccount-level-2&gt;' in the 'Position' field of Special:RequestAccount and in the display of Special:ConfirmAccount. This text lead me to find the above mentioned messages and edit them to reflect what I had already put in the subpage param of the $wgAccountRequestTypes array.

I guess I'll log this if you don't reply.

Cheers, --Dmb 13:02, 5 October 2011 (UTC)
 * This is as intended. The subpage parameter used in the URL is decided by the array, where as the name of the request type is determined by the MediaWiki:requestaccount-level-* page. Also, if the requesting user is viewing the form in language xx, and MediaWiki:requestaccount-level-*/xx exists, that will be used instead of MediaWiki:requestaccount-level-*. Aaron 00:15, 9 October 2011 (UTC)

$wgAccountRequestTypes > 1
The LocalSettings.php file contains an array (sample)

$wgAccountRequestTypes = array(   0 => array( 'abc', 'read')    1 => array( 'def', 'write') );

There's a check within the RequestAccount_body.php file, if the $wgAccountRequestTypes array has size > 1 and it seems that the array won't be overwritten. It always contains only one Entry (Authors). Is there something wrong with my configuration?

Mediawikie version: 1.17 Extension Version: latest version (at about 7 days old)
 * You are missing a comma after "'read')". Aaron 06:20, 10 November 2011 (UTC)

Sorry, my fault..define the array before loading the extension is not a good idea ;)

The selectbox is available now, but...

...a defined array $wgAccountRequestTypes = array(  0 => array( 'read', 'Lehrer'),   1 => array( 'write', 'Eltern'),   2 => array( 'read-write', 'Schueler') );

creates this selectlist ?!

<select name="wpType"> <option value="0" selected="selected">Autor Bearbeiter &amp;lt;requestaccount-level-2&amp;gt;


 * Create the page MediaWiki:Requestaccount-level-2 with what you'd like to be displayed there. —Emufarmers(T 00:10, 11 November 2011 (UTC)

Wiki is on Virtual Domain. Email From is showing webmaster@wrong_domain.
I am running MediaWiki 1.16.4 with a ConfirmAccount extension with file dates no newer than 28 Jul 2010. This is on a server that has multiple Apache virtual domains using a single IP address. I have the $wgConfirmAccountContact set to the email address of a mailing list run by Mailman (wiki-admin@RIGHT_DOMAIN). Email is going to that list and distributed to the folks who can review accounts.

The problem is that the "From: " field in all email sent by the extension shows "webmaster@WRONG_DOMAIN" where WRONG_DOMAIN is another domain on this server.

I have set the Apache ServerAdmin to webmaster@RIGHT_DOMAIN for every virtual host.

What is the source of the "From: " field in the emails sent by ConfirmAccount? How can I change it?
 * You might want to look at $wgSMTP. Aaron 07:43, 2 December 2011 (UTC)

Automatic confirmation
Hello, would it be easy/possible to add the following feature: a configuration options specifies a list of domain names (in the form of a regular expression, e.g. like *@wikimedia.org), and if an email address that matches one of these is confirmed, the account is automatically created without any need for manual approval. This would be very useful for accounts given within an organization in which email addresses are well controlled. I have looked at the source code, and adding the configuration option and the check seem straightforward, but I am not too sure about how to jump from the "email confirmed" part to the "create account" part. Best wishes, Schutz 11:11, 22 November 2011 (UTC)
 * I don't see any easy way to that atm. Aaron 07:59, 2 December 2011 (UTC)

Says that I must be logged in to use special:requestaccount
I needed to whitelist the the page. Manual:Preventing access

Notification of a new account request
There is the clear notification option for confirmations. But is there an option for admins being notified upon every request?

My wiki is small and if new users have to wait a day before getting their account, then they might lose interest and not come back. Not a good user experience....  Maybe there is an option for me to "watch" the Special:ConfirmAccounts page???
 * Admins can see notices on their watchlists about email confirmed account requests. I'm not sure exactly what is desired here. Aaron 08:34, 4 January 2012 (UTC)


 * $wgConfirmAccountContact='email@here'; will notify you when user confirms account. if they don't confirm account, why would you care?

SQL Error 1170: BLOB/TEXT column 'acr_email' used in key specification without a key length (localhost)
I've got MW 1.18 installed and downloaded ConfirmAccount using the >=1.17 link today. My server has PHP 5.3.5 (cgi-fcgi) and MySQL 5.1.54-log. I ran the maintenance/update.php script from the command line in Terminal and the table appears to have been created successfully, but when it tried to create the index on acr_email_token it failed with the following error:

Creating account_requests table...A database query syntax error has occurred. The last attempted database query was: "CREATE INDEX acr_email_token ON `mw_account_requests` (acr_email_token) " from within function "DatabaseBase::sourceFile( /users/home/dreimiller/domains/newlondonrocks.com/web/public/wiki/extensions/ConfirmAccount/ConfirmAccount.sql )". Database returned error "1170: BLOB/TEXT column 'acr_email' used in key specification without a key length (localhost)"

I tried using phpMyAdmin to set the index on that field and got the same error. Any ideas or suggestions? --Dreimiller 21:05, 3 January 2012 (UTC)


 * That error seems to be about acr_email, but the index on that is given a prefix length already. Can you pastebin what the sql file looks like? I don't see how this can happen. Aaron 08:33, 4 January 2012 (UTC)

Here you go, Aaron: ConfirmAccount.sql. --Dreimiller 20:38, 4 January 2012 (UTC)

It seems to be a problem with some MySQL versions. The following worked for me: I dropped the index acr_email, then created those ohter two indices, and finally created the acr_email index again.


 * I dropped the mw_accoount_requests table, which is the only one that was created before the SQL failed. I then edited the ConfirmAccount.sql file to move the line "CREATE UNIQUE INDEX /*i*/acr_email ON /*_*/account_requests (acr_email(255));" so that it followed the "CREATE INDEX /*i*/acr_type_del_reg ON /*_*/account_requests (acr_type,acr_deleted,acr_registration);" line. I then re-ran maintenance/update.php and the SQL ran without error. Thanks for the help, Aaron. --Dreimiller 13:02, 24 February 2012 (UTC)

I confirm this change works on a pre-set up wiki using godaddy hosting using the pre-loaded MediaWiki 1.19.0 set up and MySql 5.0.95 and PHP 5.3.6.

yes, this worked for me too. Deleting (dropping) the account_requests table using MySQL and then changing ConfirmAccount.sql as above did the trick. Make sure you don't just tweak ConfirmAccount.sql - if you don't delete the account_requests table, it doesn't work Jpmaytum (talk) 17:17, 25 September 2012 (UTC)

This was very helpful for me as well, as I was running into the same error. Dropping the acr_email index, then creating the missing indexes, followed by recreating the acr_email mail index resolved the problem. My installation is also on godaddy. --Jrandomguy (talk) 03:57, 25 June 2012 (UTC)


 * Same error here, but solution above did not work for me. Using standard debian 5.1.63-0+squeeze1 and testing newest 1.20 trunk (git). Why is acr_email "tinytext NOT NULL" but still desires a unique index? tinytext is essentially a blob, like text, and indexing behavior is special (and might perhaps be mysql-version dependent? I don't know but others report similar problems on the web). varchar(255) would make much more sense to me... Tried changing acr_email to varchar(255), -> ./maintenance/update.php goes through. Not sure yet whether any downstream problems with the ConfirmAccount code will occur. --G.Hagedorn (talk) 23:57, 24 September 2012 (UTC)

I had the same trouble; Dreimiller's solution worked for me. Do i need to restore ConfirmAccount.sql afterwards? Meng6 (talk) 06:15, 12 October 2012 (UTC)

Anyone Watching this Extension!?
This extension has been a living nightmare! Why have you made such an unnecessarily difficult script?

I am consistiently receiving the following AFTER I upload the .sql file to my database:

A database query syntax error has occurred. This may indicate a bug in the software. The last attempted database query was: SELECT 1 FROM `mdw_account_requests` WHERE acr_name = 'Test' LIMIT 1 from within function "UserAccountRequest::acquireUsername". Database returned error "1146: Table 'neveren6_mdw2.mdw_account_requests' doesn't exist (localhost)

Whats going on here? I have wasted 3 days trying to get SOMEWHERE with this...I dont see anywhere in the above with an error quite like this.

I am begging at this point for some assistance on this.
 * Did you run update.php? Aaron 05:54, 23 January 2012 (UTC)


 * Sure did, several times. Heres what I get:

<Fatal error</b>: call to undefined method MysqlUpdater::addExtensionField in <b>public_html/extensions/ConfirmAccount /backend/schema/ConfirmAccountUpdater.hooks.php</b> on line 17

....so, seriously, any idea's here? Its effectively caused my site to linger in limbo cause its just as puzzeling the results I get when attempting to remove the extension. And really, I have so many spam sign ups I have no choice but to wait for someone to figure this out. In addition, this extension bleeds into other areas of my site, namely Special Pages:Recent changes. I get this error when trying to access it: A database query syntax error has occurred. This may indicate a bug in the software. The last attempted database query was: SELECT COUNT(*) FROM `mdw_account_requests` WHERE acr_deleted = '0' AND (acr_held IS NULL) AND (acr_email_authenticated IS NOT NULL) LIMIT 1 from within function "ConfirmAccount::getOpenEmailConfirmedCount". Database returned error "1146: Table 'neveren6_mdw.mdw_account_requests' doesn't exist (localhost)". Seriously?  Guido 19:53, 23 January 2012 (UTC)
 * Are you running a version of MW and a version of the ConfirmAccount extension that don't match? addExtensionField is definitely defined in the /trunk version of MW. Aaron 06:05, 24 January 2012 (UTC)
 * Also, faster feedback can happen on #mediawiki IRC. Aaron 06:08, 24 January 2012 (UTC)
 * Just installed this extension on a MW 18.1 that was subject to heavy spam despite all anti-spam tricks I could figure out - Had no problem at all :) - Daniel K. Schneider (talk) 10:59, 21 February 2012 (UTC)
 * I had the same problem. It occurred because I was using MW REL_18_0 and the svn trunk of this extension.  As Aaron pointed out, you need to make sure that you get the ConfirmAccount version that matches your MW version.  Pgr94 (talk) 13:17, 26 March 2012 (UTC)
 * I am having this same problem on a MW REL_18_3 install. 8.30.79.4 13:26, 2 May 2012 (UTC)

Problem with 1.18x
I encounter the following error when trying to create an account on the version for 1.18x on 1.18.1: Fatal error: Call to a member function getName on a non-object in [masked]/mediawiki-1.18.1/extensions/ConfirmAccount/ConfirmAccount.php on line 178 Hello? Any help on this?
 * You might have another extension triggering one of the user hooks without a User argument. Aaron (talk) 00:24, 25 February 2012 (UTC)
 * Hi. I have no other extension installed. Just ConfirmAccount and it happens when I try to create an account. (Peter)
 * Search your copy of the code for "wfRunHooks( 'AbortNewAccount'" and see what turns up. All of those should pass a User object. The one in Special:Login clearly would have fataled if it wasn't before even reaching the hook. Aaron (talk) 05:08, 23 March 2012 (UTC)

Updating 1.18.1 fails with webupdater
when calling the mediawiki 1.18.1 webinstaller to run the update.php I'm running into the following problem An error occured: A database query syntax error has occurred. The last attempted database query was: "ALTER TABLE `account_requests` ADD acr_type tinyint(255) unsigned NOT NULL default 0, DROP INDEX acr_deleted_reg, ADD INDEX acr_type_del_reg (acr_type,acr_deleted,acr_registration) " from within function "DatabaseBase::sourceFile( /home/httpd/vhosts/wiki-products.org/subdomains/en/httpdocs/extensions/ConfirmAccount/archives/patch-account_credentials.sql )". Database returned error "1091: Can't DROP 'acr_deleted_reg'; check that column/key exists (localhost)" Backtrace:
 * 1) 0 httpdocs/includes/db/Database.php(827): DatabaseBase->reportQueryError('Can't DROP 'acr...', 1091, 'ALTER TABLE `ac...', 'DatabaseBase::s...', false)
 * 2) 1 httpdocs/includes/db/Database.php(3026): DatabaseBase->query('ALTER TABLE `ac...', 'DatabaseBase::s...')
 * 3) 2 httpdocs/includes/db/Database.php(2924): DatabaseBase->sourceStream(Resource id #290, false, false, 'DatabaseBase::s...')
 * 4) 3 httpdocs/includes/installer/DatabaseUpdater.php(362): DatabaseBase->sourceFile('/home/httpd/vho...')
 * 5) 4 httpdocs/includes/installer/DatabaseUpdater.php(379): DatabaseUpdater->applyPatch('/home/httpd/vho...', true)
 * 6) 5 httpdocs/includes/installer/DatabaseUpdater.php(233): DatabaseUpdater->addTable('account_credent...', '/home/httpd/vho...', true)
 * 7) 6 httpdocs/includes/installer/DatabaseUpdater.php(201): DatabaseUpdater->runUpdates(Array, Array)
 * 8) 7 httpdocs/includes/installer/DatabaseInstaller.php(248): DatabaseUpdater->doUpdates(Array, true)
 * 9) 8 httpdocs/includes/installer/WebInstallerPage.php(513): DatabaseInstaller->doUpgrade
 * 10) 9 httpdocs/includes/installer/WebInstaller.php(254): WebInstaller_Upgrade->execute
 * 11) 10 httpdocs/mw-config/index.php(50): WebInstaller->execute
 * 12) 11 httpdocs/mw-config/index.php(18): wfInstallerMain
 * 13) 12 {main}

update.php stalls.

--Francishunger (talk) 22:42, 19 February 2012 (UTC)


 * Are you trying to install it for the first time? I've seen other people have the acr_email error. Have you tried ? Aaron (talk) 20:53, 29 February 2012 (UTC)


 * thanks for pointing me there. The proposed solution worked. --Francishunger (talk) 20:34, 1 March 2012 (UTC)

http 500 when a new user try to register (version 1.18.1)
I have installed the extention according to the manual and the database is updated with "account_creditals" and "account_requests" fields. However when I test the application by filling out the account request form and it the request button (send button), I recieve a http 500 error message, page can't be shown. What could the problem be ? Anything I've missed ? I am using Norwegian language if that matters.

Regards Petter Enge
 * Check the PHP or apache error logs. Aaron (talk) 17:06, 7 March 2012 (UTC)


 * Could you please tell me were I find this log ?  I am using an external provider.   (Petter)

Found the problem. I had a Blacklist extention enabled. I disabled the extention in the LocalSetting and the error went away. I will continue the testing.-

Error sending mail: Policy restriction in effect. The fifth parameter is disabled on this system
Can anyone solve this problem?

Error sending mail:

'''Policy restriction in effect. The fifth parameter is disabled on this system'''

Mediawiki 1.18.0

Safe mode off
 * What are your other extensions?--Jasper Deng (talk) 16:20, 31 March 2012 (UTC)

ConfirmAccount - get the error message here

ConfirmEdit -disabled at the moment

Gadgets

intersection

Nuke

ParserFunctions

Renameuser

RSSReader

SpamBlacklist

Vector

WikiEditor

Most of them are in the standard installation.
 * OK, so is email enabled in your PHP settings?--Jasper Deng (talk) 19:11, 31 March 2012 (UTC)

yes, and it works fine. I can fill out the form and send it. The reciver get an email with an activation link, that works fine too. After sending the form the error shows.
 * Did you start debugging?--Jasper Deng (talk) 18:29, 1 April 2012 (UTC)

Fatal error: Call to undefined method User::getEditToken in
I am running MW 1_18_3 (just updated) and get this error when someone tries to create an account:

Fatal error: Call to undefined method User::getEditToken in $HOME/wikidir/extensions/ConfirmAccount/frontend/specialpages/actions/RequestAccount_body.php on line 234

Also, as others have noted, I still see this error on attempts to update:

$ php update.php MediaWiki 1.18.3 Updater

Going to run database updates for fwiki-fwiki Depending on the size of your database this may take a while! Abort with control-c in the next five seconds (skip this countdown with --quick) ... 0 Fatal error: Call to undefined method MysqlUpdater::addExtensionField in $HOMEW/wikidir/extensions/ConfirmAccount/backend/schema/ConfirmAccountUpdater.hooks.php on line 17 $

As you can see, I am running MW 1.18.3.

The version of ConfirmAccount I am using is:

$ svn info Path:. URL: http://svn.wikimedia.org/svnroot/mediawiki/trunk/extensions/ConfirmAccount Repository Root: http://svn.wikimedia.org/svnroot/mediawiki Repository UUID: dd0e9695-b195-4be7-bd10-2dea1a65a6b6 Revision: 115105 Node Kind: directory Schedule: normal Last Changed Author: raymond Last Changed Rev: 115102 Last Changed Date: 2012-05-01 11:42:15 -0700 (Tue, 01 May 2012)

Any thoughts?
 * You should use the 1.18 version of the extension. Aaron (talk) 06:19, 6 May 2012 (UTC)
 * I get the same. I couldn't get the "get snapshot" to work (I get Invalid response from remote subversion client.) - so went to SVN checkout-url and copied the files/directories from there (Revision 115157) - which appears to be the most recent version... which revision do I need for 1.18.0?. The db database worked ok by the way (tables created: account_requests - with 4 indexes;account_credentials - with 1 index).
 * However, the "request account" link on my wiki gives the "Fatal error: Call to undefined method User::getEditToken in /home/sepe5826/public_html/wiki/extensions/ConfirmAccount/frontend/specialpages/actions/RequestAccount_body.php on line 234" message - and if I go to Special:ConfirmAccounts, I get an internal error (with a message "Set $wgShowExceptionDetails = true; at the bottom of LocalSettings.php to show detailed debugging information.")
 * If I use  then I get this:


 * I am using MediaWiki v1.18.0. Regards, -- <font color="#307D7E">Phantom <font color="#55CAFA">Steve /<font color="#008000">talk &#124;<font color="#000080">contribs \ 21:51, 7 May 2012 (UTC)
 * The version in Subversion should always be assumed to be trunk, i.e. it may be liable to fail if you aren't using a trunk version of MediaWiki.--Jasper Deng (talk) 21:53, 7 May 2012 (UTC)
 * OK, I get that - but without the "Download snapshot" working, how can I find out which version I should use for my version of MediaWiki? In this case, I am probably going to try to install the latest version of MW, but in future I may not wish to do that, so need to download "older" versions from SVN -- <font color="#307D7E">Phantom <font color="#55CAFA">Steve /<font color="#008000">talk &#124;<font color="#000080">contribs \ 22:04, 7 May 2012 (UTC)
 * That I do not know. I think the extension distributor needs to be upgraded to work with Git - something's awfully wrong.--Jasper Deng (talk) 22:07, 7 May 2012 (UTC)

PHP Fatal error: Call to undefined method MysqlUpdater::addExtensionField
Hi,

I am running 1.18.3. When I try to make the update, I have the following error:

php maintenance/update.php MediaWiki 1.18.3 Updater

Going to run database updates for wikidb Depending on the size of your database this may take a while! Abort with control-c in the next five seconds (skip this countdown with --quick) ... 0 PHP Fatal error: Call to undefined method MysqlUpdater::addExtensionField in /opt/www/mediawiki/extensions/ConfirmAccount/backend/schema/ConfirmAccountUpdater.hooks.php on line 17

my svn info svn info Path:. URL: http://svn.wikimedia.org/svnroot/mediawiki/trunk/extensions/ConfirmAccount Repository Root: http://svn.wikimedia.org/svnroot/mediawiki Repository UUID: dd0e9695-b195-4be7-bd10-2dea1a65a6b6 Revision: 115126 Node Kind: directory Schedule: normal Last Changed Author: raymond Last Changed Rev: 115102 Last Changed Date: 2012-05-01 18:42:15 +0000 (Tue, 01 May 2012)

Any idea ?

Thank you
 * You are mixing MW 1.18 with the trunk version of ConfirmAccount. That always tends to cause breakage due to core interfaces changes. Aaron (talk) 21:44, 12 May 2012 (UTC)

Hijacking?
OK, I've updated my wiki to 1.19.0. I can use the "Request" page OK.

However, when I go to confirm, it doesn't work! Special:ConfirmAccounts works ok, showing the queues available. Obviously, the only queue with anything in it is the "open requests" queue. When I go to that queue, it shows all the entries correctly (including "confirmed" where appropriate against the email address). However, when I go to the individual entry to "Review", although everything is showing OK, whichever option I choose out of "Accept", "Reject", "Hold", "Spam" - or, indeed, if I choose none of these options - I get a box at the top of the screen saying "There seems to be a problem with your login session; this action has been cancelled as a precaution against session hijacking. Go back to the previous page, reload that page and then try again.".

I have used Chrome 18.0.1025.168, Safari 5.1.5, IE 9.0.8112.16421 64-bit edition, Firefox 12.0 and Opera 11.62 - they all have the same error.

I am using MediaWiki 1.19.0 and the latest version of ConfirmAccount.

Any ideas? -- <font color="#307D7E">Phantom <font color="#55CAFA">Steve /<font color="#008000">talk &#124;<font color="#000080">contribs \ 00:21, 8 May 2012 (UTC)
 * Did you try clearing your browser's cache?--Jasper Deng (talk) 00:28, 8 May 2012 (UTC)
 * Yes, I did - it still happens. -- <font color="#307D7E">Phantom <font color="#55CAFA">Steve /<font color="#008000">talk &#124;<font color="#000080">contribs \ 04:09, 8 May 2012 (UTC)
 * Then I really don't know... of interest is that I get this error message if I try to rollback an edit to a fully protected page on enwiki, in addition to the full protection message.--Jasper Deng (talk) 04:11, 8 May 2012 (UTC)
 * Fixed in r115264. Aaron (talk) 21:40, 12 May 2012 (UTC)

Fatal error: Call to a member function
If the applicant forget to fill in his/her's user name, the script breaks with the message:

Fatal error: Call to a member function getName on a non-object in /..../ConfirmAccount.php on line 193

I.m using Mediawiki 1.18

Could you solve this? -Bert

account request submission error
On submission of an account request, if the 'Real name' field is left empty, we get -

Fatal error: Call to a member function getName on a non-object in /home/atwork/public_html/devwiki/w/extensions/ConfirmAccount/SpecialConfirmAccount.php on line 151

Mediawiki ver. 1.162 - appears to be the same error that was just posted by Bert...

Any idea why?

Thanks for any leads, Paul N.

what happened to notification of account requests?!
I recall older versions of this extension had notifications for bureaucrats notifying them of open requests. E-mail and site notifications used to be available. However, I am not seeing either anymore.

I just did a fresh install of the extension checked out from the latest SVN revision (r115546) on MediaWiki 1.19 running PHP 5.3.

I think this is a pretty critical function for bureaucrats and administrators.

Any help?

Sure - Just add $wgConfirmAccountContact='email@here'; to your  after the inclusion of ConfirmAccount. This will not send a mail to all administrators, only to the email-adress (i use a mailing-list) --BLinz (talk) 20:26, 26 June 2012 (UTC)

Download currently broken?
I rather urgently need to download the latest version of this extension.

Sadly there isn't one: All the links to the GIT repository give me a 404 error and the main download link says this:

''Download MediaWiki extension Jump to: navigation, search

No such extension "ConfirmAccount"''

Can someone provide me with a mirror or possibly fix this?

http://svn.wikimedia.org/svnroot/mediawiki/branches/REL1_19/extensions/ConfirmAccount/  24.130.249.87

"Review" doesn't work. SpecialPage doesn't exist
Hi.

This extension works up until I try and do either of these two things.

1. Click the Review in which I get this:    ''The website encountered an error while retrieving http://localhost:8888/4/index.php?title=Special:ConfirmAccounts/authors&acrid=2. It may be down for maintenance or configured incorrectly.''

2. When I go to user credentials. I get this: ''The website encountered an error while retrieving http://localhost:8888/4/Special:UserCredentials. It may be down for maintenance or configured incorrectly.''

I am thinking the update.php didn't work but I don't know why it wouldn't. 24.130.249.87

Thank you.


 * You installed the matching version (release for MediaWiki 1.19 and MediaWiki 1.19)? Please always tell us what version do you use. Tim (SVG)  08:08, 1 July 2012 (UTC)

I am using MediaWiki 1.19.1 but upgraded from 1.16. . I am thinking maybe I have the legacy version of ConfirmAccount but I can't verify from SpecialVersion. I went to download the 1.19 version to test and the only available download was here since git isn't working yet : http://svn.wikimedia.org/svnroot/mediawiki/branches/REL1_19/extensions/ConfirmAccount/. I am very confused as to the file structure of these files and how I am suppose to order them in terms of directories and subdirectories. Should I have a folder for "backend" and "frontend" etc? They are definitely different than the version I am using. Thank you 24.130.249.87


 * BTW I have a version of MW 1.17 running this extension and it works fine. When I updated to 1.19.1 it breaks the special pages I mentioned 24.130.249.87

I'm equally confused about the file and folder structure and I'm struggling to get the version proved via http://svn.wikimedia.org/svnroot/mediawiki/branches/REL1_19/extensions/ConfirmAccount/ to work properly with MW 1.19.1.

I took the time to download that entire thing again one-by-one and use the exact same file structure as it is listed with and it seems to have worked. 24.130.249.87 04:52, 10 July 2012 (UTC)

Accept Requests doesn't work after update
After updating both, Wikimedia and this extension to the current version, I get a weird error when I try to accept a new account. Can somebody help me to understand and repair this? The rest of the extension seems to work fine with the new versions.

Catchable fatal error: Argument 1 passed to AccountConfirmSubmission::acceptRequest_rollback must be an instance of Database, instance of DatabaseMysql given, called in /www/htdocs/w00ee632/wiki/extensions/ConfirmAccount/business /AccountConfirmSubmission.php on line 205 and defined in /www/htdocs/w00ee632/wiki/extensions/ConfirmAccount/business /AccountConfirmSubmission.php on line 333
 * There is a "type hint" that should be DatabaseBase. Aaron (talk) 19:14, 9 July 2012 (UTC)
 * This was fixed in git (master branch). Aaron (talk) 19:53, 7 August 2012 (UTC)

Snapshot from Extension Distributor is currently unavailable
Trunk doesn't work with MW 1.18.2 and I can't get the appropriate snapshot from Extension Distributor. If I go to http://www.mediawiki.org/wiki/Special:ExtensionDistributor/ConfirmAccount, the error message is No such extension "ConfirmAccount".


 * It is on git now. Aaron (talk) 19:52, 7 August 2012 (UTC)

Error sending mail:Unknown error in PHP's mail function.
The extension seems to work fine except when the user gets to the point of sending a request for an account. Then this error appears : '''Error sending mail:Unknown error in PHP's mail function. '''

The server error log error is:

qmail-inject: fatal: unable to parse this line: Return-Path:apache@ 216.70.110.23:7081

Thank you 24.130.249.87 09:00, 12 July 2012 (UTC)

mw-config
Hi, I installed the extension and I have this error when running mw-config/?page=ExistingWiki

Fatal error: Class 'ConfirmAccountUISetup' not found in /home/rocket/public_html/wiki/extensions/ConfirmAccount/ConfirmAccount.php on line 42

can't confirm account
Hi, when I'm accepting a new user, this error occurrs: «1146: Table 'rocket_wiki.mw_account_credentials' doesn't exist (localhost)».

I run update script, and it helped to solve the same error when a new user request an account, but when I tried to accept a new user, the error shows again.

Someone can help me?

$wgConfirmAccountRequestFormItems undocumented
The README.txt says to go to this page for documentation, and says that a bunch of variables have been folded into "$wgConfirmAccountRequestFormItems", but there is no documentation on the format of this variable. Is it an associative array? Or some kind of bit mask number thing?
 * The .config.php file in the extension has inline documentation. Aaron (talk) 19:50, 14 August 2012 (UTC)

Invisible table - CSS error
The file confirmaccount.css contains background colour declarations but the matching text colour declarations are missing. This produces invisible or near-invisible text unless the skin in use happens to be using a dark text colour. There are two obvious ways to correct this - either add something like this to confirmaccount.css:

or else simply delete the four offending rules. This works just fine on my site, and there seems to be no reason why it wouldn't be equally OK on any other - the foreground and background colours default back to the site-wide standards, so that should not be a problem.

Brilliant extension by the way! It has saved us untold amounts of work!

Tannin (talk) 12:30, 22 August 2012 (UTC)

PS: it turns out that there are also hard-coded background colours with missing foreground colour declarations in ConfirmAccount_body.php. RequestAccount_body.php and UserCredentials_body.php. Simply removing these appears to work just fine. Tannin (talk) 12:59, 22 August 2012 (UTC)

Installation failed completely
Hey,

no way to get it run.

I have no access to the server via SSH or Telnet or similar and cannot run the update.php directly. Web-updater didn't work, no tables were installed.

After extraction of the downloaded gz, confirmaccount.sql is not in the extension's directory but in the backend subdirectory, but does not contain the prefix (search and replace failed: the one and only occurrence of the string to replace was in the replace instruction itself).

In the meantime my spam pages in the Wiki are getting more and more.

Please, somebody out there who can save me and my wiki??

Thanks --Thorsten (talk) 13:55, 11 September 2012 (UTC)

Fixed
I found the way my hoster allows to execute SQL via PHPMyAdmin. Afterwards, the tables were present and the extension worked.

Nevertheless, accounts are created by spammers as before, although I edited the group permissions according to the instructions, in so far I do not see how this extension may help.

--Thorsten (talk) 12:54, 12 September 2012 (UTC)
 * The extension sets $wgGroupPermissions['*']['createaccount'] = false;. Are you setting that back to true anywhere? Aaron (talk) 05:30, 13 September 2012 (UTC)

Update to 1.19.2 and mwstoreerror occurs
Any idea how to fix this?

Unable to find the wrapper "mwstore" - did you forget to enable it when you configured PHP? in /wiki/extensions/ConfirmAccount/backend/ConfirmAccount.class.php on line 26

TeraS (talk) 18:40, 11 October 2012 (UTC)

Having the exact same problem and will be interested to find out a solution

--Gmatthews (talk) 19:51, 14 October 2012 (UTC) Same here. Any clue on a fix? Mine reads the same, except AccountConfirmSubmission.php and line 308.

Problems Running ConfirmAccount with PostgreSQL
Problem #1:

For a new user request, ConfirmAccount attempts to insert NULL into acr_id column, which is marked NOT NULL. This can be fixed by commenting out the following line in UserAccountRequest.php (line 313):

$dbw->insert( 'account_requests',			array( #         			'acr_id'			=> $acr_id, 'acr_name'			=> strval( $this->name ), 'acr_email'		=> strval( $this->email ), However, it's unclear on why the following code, above that section, does not work:

# Allow for some fields to be handled automatically... $acr_id = is_null( $this->id ) ? $this->id : $dbw->nextSequenceValue( 'account_requests_acr_id_seq' );

Problem #2: Cannot Approve Accounts

"There is no pending request corresponding to the given ID. It may have already been handled."
 * 1) Go to Pending Requests.
 * 2) Click "Review" on any resquest
 * 3) Get:

I haven't been able to confirm any requests for this reason. ConfirmAccount.php won't let me review/look at any individual request.
 * What do the "review" link URLs look like? Do they have IDs that are actually in the table? Aaron (talk) 08:11, 18 November 2012 (UTC)


 * Actually that code is broken (I fixed it in https://gerrit.wikimedia.org/r/#/c/33976/). Aaron (talk) 08:11, 18 November 2012 (UTC)

Thanks for the patch. It doesn't do anything to fix the "Unable to review" issue, though. Here's what the Review link looks like:

And acr_id 1 definitely does exist.
 * Try changing acr_deleted to "INTEGER NOT NULL DEFAULT 0". Aaron (talk) 19:26, 18 November 2012 (UTC)

Aaron:

That worked! Thanks. I presume you'll fix the SQL file in the source code?

BTW, if anyone else needs to fix this like I did, the series of commands for an already installed database are:

alter table account_requests alter column acr_deleted drop default;

alter table account_requests alter column acr_deleted type integer using ( 0 );

alter table account_requests alter column acr_deleted set default 0;

Thanks so much for the very rapid turnaround on this bug. Above and beyond!


 * The source was changed. Aaron (talk) 08:39, 8 December 2012 (UTC)

Error
Hi, I have installed the extension, if it works :) I can delete, and reject the users. But i want a user to confirm / accept I come to the site: (link to the press) http://.../Spezial:Benutzerkonto_bestätigen/authors

See in the picture: (Image) http://labs.wikibyte.org/w/images/c/cc/Error-extension-ConfirmAccount.png

Confirmed the user is not in the DB table "account_credentials" enrolled!

the error log: HP Notice: Undefined property: stdClass::$acr_xff in: /.../w/extensions/ConfirmAccount/backend/UserAccountRequest.php on line 55, referer: http://testwiki.domain.tld/w/index.php?title=Spezial:Benutzerkonto_best%C3%A4tigen/authors&acrid=1

PHP Notice: Undefined property: stdClass::$acr_agent in: /.../w/extensions/ConfirmAccount/backend/UserAccountRequest.php on line 56, referer: http://testwiki.domain.tld/w/index.php?title=Spezial:Benutzerkonto_best%C3%A4tigen/authors&acrid=1

PHP Catchable fatal error: Argument 1 passed to: AccountConfirmSubmission::acceptRequest_rollback

must be an instance of Database, instance of DatabaseMysql given, called in:

/.../w/extensions/ConfirmAccount/business/AccountConfirmSubmission.php on line 205

and defined in:

/.../w/extensions/ConfirmAccount/business/AccountConfirmSubmission.php on line 333,

referer: http://testwiki.domain.tld/w/index.php?title=Spezial:Benutzerkonto_best%C3%A4tigen/authors&acrid=1

I use InnoDB and the new user is created. However, it remains the user in the "Confirm account requests" as open requests. My Wiki software is 19.2 maybe you have an info? I have a lot of spam and it seems to me that the good solution extension. Sorry for my bad english, i'am german user.

--Extemist (talk) 22:35, 21 November 2012 (UTC)
 * The "DatabaseMysql" errors seems fixed in the latest version of the code. There was a bug where the type hint was for "Database" when it should have been "DatabaseBase". Aaron (talk) 08:43, 8 December 2012 (UTC)

Disable account request limit from the same IP
Hi! Since my MediaWiki instalaltion is behind a proxy configuration, every request is interpreted as coming from Localhost (127.0.0.1). As a result, sending request for accounts doesn't work at all because every user get's this error: Sorry, you have already requested 1 account. You cannot make any more requests.

Is there any configuration option to diable this IP check or maybe some way to increment that limit per IP? Thanks!. --FrancoIacomella (talk) 11:02, 29 November 2012 (UTC)
 * See $wgAccountRequestThrottle. Aaron (talk) 08:44, 8 December 2012 (UTC)

Account confirmation status does not appear in Special:ConfirmAccounts (and related pages)
Just upgraded to MW 1.20.1 and ConfirmAccount-master-6712353.

In the ConfirmAccounts section, it looks like the status of account requests now misses whether or not the user has confirmed their email address - so admins can't tell if they've been verified or not. Apologies if I've missed something, but if not I think this is an important omission.

On a related note, in older versions, when logging into mediawiki as Admin, the login page used to display a line at the top saying that there were accounts waiting to be approved - this seems to have disappeared. This is really just a cosmetic comment.

Could I also suggest that the ConfirmAccount Wiki page is updated to reflect that the wgAccountRequestMinWords and some other variables are no longer in use having been wrapped into wgConfirmAccountRequestFormItems?

Thanks for the effort in this, we've been happily running ConfirmAccount for some time now.

-sysad77
 * Where is the email confirmation status missing? On the list view or the page for a single account request? Aaron (talk) 08:48, 8 December 2012 (UTC)

Hi - Under SpecialPages, Confirm account requests (i.e. Special:ConfirmAccounts), the only indication of an unconfirmed account is the "prospective authors(open requests...) link:-

prospective authors (open requests [1] | held requests [0] | recently rejected requests [0] | expired requests)

Selecting this page for the Confirm account requests page (showing the prospective authors queue for review) does not displays:-

Queue: prospective authors [open requests | held requests | rejected requests | expired requests] (show all queues)

I'm fairly sure that there should be the email status displayed in this second page, or if not that, then the first.

Account confirmation error: Could not create directory "mwstore://accountcreds-backend/accountcreds-public/w/we/wes".
Upgraded from MW1.16 to MW1.20.2, and to ConfirmAccount-master-5ef9b44.

I've run the maintenance/update.php file, with the updated LocalSettings.php with require_once("$IP/extensions/ConfirmAccount/ConfirmAccount.php");

When I try to approve an account, I get the following error: Could not create directory "mwstore://accountcreds-backend/accountcreds-public/w/we/wes"

Any ideas?

02:19, 6 December 2012 (UTC)
 * Look in the php error log (often apache.log). Aaron (talk) 08:48, 8 December 2012 (UTC)

Account confirmation error
MW: 1.20.2, when I try to approve an account:
 * Warning: file_exists [function.file-exists]: Unable to find the wrapper &quot;mwstore&quot; - did you forget to enable it when you configured PHP? in /html/w/extensions/ConfirmAccount/business/AccountConfirmSubmission.php on line 304


 * Jaider Msg 16:53, 19 December 2012 (UTC)
 * See https://gerrit.wikimedia.org/r/#/c/41815/. This was broken by some core refactoring many months back. Aaron (talk) 00:21, 1 January 2013 (UTC)