ResetUserEmail::__construct()   A
last analyzed

Complexity

Conditions 1
Paths 1

Size

Total Lines 9
Code Lines 6

Duplication

Lines 0
Ratio 0 %

Importance

Changes 0
Metric Value
cc 1
eloc 6
nc 1
nop 0
dl 0
loc 9
rs 9.6666
c 0
b 0
f 0
1
<?php
0 ignored issues
show
Coding Style Compatibility introduced by
For compatibility and reusability of your code, PSR1 recommends that a file should introduce either new symbols (like classes, functions, etc.) or have side-effects (like outputting something, or including other files), but not both at the same time. The first symbol is defined on line 32 and the first side effect is on line 24.

The PSR-1: Basic Coding Standard recommends that a file should either introduce new symbols, that is classes, functions, constants or similar, or have side effects. Side effects are anything that executes logic, like for example printing output, changing ini settings or writing to a file.

The idea behind this recommendation is that merely auto-loading a class should not change the state of an application. It also promotes a cleaner style of programming and makes your code less prone to errors, because the logic is not spread out all over the place.

To learn more about the PSR-1, please see the PHP-FIG site on the PSR-1.

Loading history...
2
/**
3
 * Reset user email.
4
 *
5
 * This program is free software; you can redistribute it and/or modify
6
 * it under the terms of the GNU General Public License as published by
7
 * the Free Software Foundation; either version 2 of the License, or
8
 * (at your option) any later version.
9
 *
10
 * This program is distributed in the hope that it will be useful,
11
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
12
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
13
 * GNU General Public License for more details.
14
 *
15
 * You should have received a copy of the GNU General Public License along
16
 * with this program; if not, write to the Free Software Foundation, Inc.,
17
 * 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
18
 * http://www.gnu.org/copyleft/gpl.html
19
 *
20
 * @file
21
 * @ingroup Maintenance
22
 */
23
24
require_once __DIR__ . '/Maintenance.php';
25
26
/**
27
 * Maintenance script that resets user email.
28
 *
29
 * @since 1.27
30
 * @ingroup Maintenance
31
 */
32
class ResetUserEmail extends Maintenance {
33
	public function __construct() {
34
		$this->addDescription( "Resets a user's email" );
35
		$this->addArg( 'user', 'Username or user ID, if starts with #', true );
36
		$this->addArg( 'email', 'Email to assign' );
37
38
		$this->addOption( 'no-reset-password', 'Don\'t reset the user\'s password', false, false );
39
40
		parent::__construct();
41
	}
42
43
	public function execute() {
44
		$userName = $this->getArg( 0 );
45
		if ( preg_match( '/^#\d+$/', $userName ) ) {
46
			$user = User::newFromId( substr( $userName, 1 ) );
47
		} else {
48
			$user = User::newFromName( $userName );
49
		}
50
		if ( !$user || !$user->getId() || !$user->loadFromId() ) {
51
			$this->error( "Error: user '$userName' does not exist\n", 1 );
52
		}
53
54
		$email = $this->getArg( 1 );
55
		if ( !Sanitizer::validateEmail( $email ) ) {
0 ignored issues
show
Bug Best Practice introduced by
The expression \Sanitizer::validateEmail($email) of type null|boolean is loosely compared to false; this is ambiguous if the boolean can be false. You might want to explicitly use !== null instead.

If an expression can have both false, and null as possible values. It is generally a good practice to always use strict comparison to clearly distinguish between those two values.

$a = canBeFalseAndNull();

// Instead of
if ( ! $a) { }

// Better use one of the explicit versions:
if ($a !== null) { }
if ($a !== false) { }
if ($a !== null && $a !== false) { }
Loading history...
56
			$this->error( "Error: email '$email' is not valid\n", 1 );
57
		}
58
59
		// Code from https://wikitech.wikimedia.org/wiki/Password_reset
60
		$user->setEmail( $email );
61
		$user->setEmailAuthenticationTimestamp( wfTimestampNow() );
0 ignored issues
show
Security Bug introduced by
It seems like wfTimestampNow() can also be of type false; however, User::setEmailAuthenticationTimestamp() does only seem to accept string, did you maybe forget to handle an error condition?
Loading history...
62
		$user->saveSettings();
63
64
		if ( !$this->hasOption( 'no-reset-password' ) ) {
65
			// Kick whomever is currently controlling the account off
66
			$user->setPassword( PasswordFactory::generateRandomPasswordString( 128 ) );
67
		}
68
	}
69
}
70
71
$maintClass = 'ResetUserEmail';
72
require_once RUN_MAINTENANCE_IF_MAIN;
73