Can't locate Token.pm in @INC when trying to log in

RESOLVED FIXED in Bugzilla 2.18

Status

()

Bugzilla
Bugzilla-General
RESOLVED FIXED
14 years ago
5 years ago

People

(Reporter: justdave, Assigned: justdave)

Tracking

({regression})

2.17.6
Bugzilla 2.18
regression
Bug Flags:
approval +
blocking2.18 +

Details

Attachments

(1 attachment)

This is a regression from the bug 192516 checkin.  I missed some occurances of
Token.
Bugzilla/Auth/DB.pm:53:    require Token;
Bugzilla/Auth/DB.pm:54:    Token::DeletePasswordTokens($userid, "user_logged_in");
Bugzilla/Auth.pm:178:retrieved through the L<Token interface|Token>.
Bugzilla/Token.pm:29:# Bundle the functions in this file together into the
"Token" package.
Bugzilla/Token.pm:250:        Token::Cancel($token, $reason);
token.cgi:160:    Token::IssuePasswordToken($cgi->param('loginname'));
token.cgi:239:        $vars->{'email'} = $new_email; # Needed for
Token::Cancel's mail
token.cgi:240:        Token::Cancel($::token,"account_exists");
Attachment #144208 - Flags: review?(gerv)
Flags: blocking2.18+
Target Milestone: --- → Bugzilla 2.18
Comment on attachment 144208 [details] [diff] [review]
Patch

r=gerv as long as you check none of the changes break the 80 character line
length limit.

Gerv
Attachment #144208 - Flags: review?(gerv) → review+
Yep, it fits (barely)

Checking in token.cgi;
/cvsroot/mozilla/webtools/bugzilla/token.cgi,v  <--  token.cgi
new revision: 1.23; previous revision: 1.22
done
Checking in Bugzilla/Auth.pm;
/cvsroot/mozilla/webtools/bugzilla/Bugzilla/Auth.pm,v  <--  Auth.pm
new revision: 1.3; previous revision: 1.2
done
Checking in Bugzilla/Token.pm;
/cvsroot/mozilla/webtools/bugzilla/Bugzilla/Token.pm,v  <--  Token.pm
new revision: 1.22; previous revision: 1.21
done
Checking in Bugzilla/Auth/DB.pm;
/cvsroot/mozilla/webtools/bugzilla/Bugzilla/Auth/DB.pm,v  <--  DB.pm
new revision: 1.5; previous revision: 1.4
done
Status: NEW → RESOLVED
Last Resolved: 14 years ago
Flags: approval+
Resolution: --- → FIXED
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.