Welcome, Guest. Please Login or Register.
July 05, 2025, 08:55:57 PM
Home Help Search Log in Register
News: SMF is the next generation in forum software, almost completely re-written from the ground up, make sure you don't fall for cheap imitations that suffer from feature bloat!

YaBB SE Community  |  English User Help  |  English Help  |  Password corruption / invalidness? « previous next »
Pages: [1] Reply Ignore Print
Author Topic: Password corruption / invalidness?  (Read 865 times)
Spug
Noobie
*
Posts: 19


I'm a llama!

Password corruption / invalidness?
« on: February 13, 2004, 11:48:16 PM »
Reply with quote

YaBB SE Version: 1.5.5
PHP Version: 4.3.4
MySQL Version: 4.0.x

Problem Description:
I just converted my YaBB 1.3.1 board to YaBB SE, and after driving over a few bumps, I thought it was established well. But it seems some select members are having problems logging in.

All I know is that they request their passwords mailed to them, and they get a randomly generated password. Why this is, I don't know, the passwords on the YaBB I had weren't encrypted. Anyway, the thing is that these passwords don't seem to work. I'm not talking a couple of members here, but many, many. I don't have capacity to find out if they registered after I created the YaBB SE (which I reckon generates random passwords and mails them to new members, and this would be the reason for the randomized ones?), but this concerns MANY members. While also many members have no problems logging in using their old passwords (that is if the ones who DO have problems are from the YaBB times - if any newly registered member gets an invalid password mailed to them, that's pretty critical).

Some advice / help would be appreciated.
Logged
[Unknown]
Global Moderator
YaBB God
*****
Posts: 7830


ICQ - 179721867unknownbrackets@hotmail.com WWW
Re:Password corruption / invalidness?
« Reply #1 on: February 14, 2004, 12:47:49 AM »
Reply with quote

The passwords are encrypted for security reasons.  The passwords are randomized because YaBB SE can't even get to what the password was before.

Can we have a link to your forum for testing?

-[Unknown]
Logged
Spug
Noobie
*
Posts: 19


I'm a llama!

Re:Password corruption / invalidness?
« Reply #2 on: February 14, 2004, 12:59:52 AM »
Reply with quote

Sure, sure, as long as you don't laugh at the fact that it's the official Norwegian Pokémon Forum.

http://www.hazardlabs.com/pokemon/index.php
Logged
[Unknown]
Global Moderator
YaBB God
*****
Posts: 7830


ICQ - 179721867unknownbrackets@hotmail.com WWW
Re:Password corruption / invalidness?
« Reply #3 on: February 14, 2004, 01:51:24 AM »
Reply with quote

I was able to use the reminder properly.  Please make sure your users are copying and pasting the password they are being sent.

Example:

QuoteHei test2,

Pokemon-forumet ==>

Brukernavn: test2
Passord: 1SufwjgSNs
Posisjon:

Med vennlig hilsen,
Administratorene til Pokemon-forumet.

-[Unknown]
Logged
Spug
Noobie
*
Posts: 19


I'm a llama!

Re:Password corruption / invalidness?
« Reply #4 on: February 14, 2004, 02:00:06 AM »
Reply with quote

Now, that's strange. I'll make the members e-mail me and tell me exactly what's wrong. The error log has lots of errors that say they input invalid password, so I don't think they're lying. But maybe something is wrong manually and not serverside.

But just to clarify, I didn't quite get what you said; the passwords from the last board, they were kept or reset to something random?
Logged
[Unknown]
Global Moderator
YaBB God
*****
Posts: 7830


ICQ - 179721867unknownbrackets@hotmail.com WWW
Re:Password corruption / invalidness?
« Reply #5 on: February 14, 2004, 02:20:07 AM »
Reply with quote

They should have been kept, but they were encrypted... there's no "going back" now.

-[Unknown]
Logged
Shadow's Pawn
Support Team
YaBB God
*****
Posts: 597


ich soll nicht toten

ICQ - 8039201shadowpawn@hotmail.com WWW
Re:Password corruption / invalidness?
« Reply #6 on: February 14, 2004, 03:53:39 AM »
Reply with quote

You can change their passwords manually by editting their profiles.
Logged

apologize \A*pol"o*gize\, v. i. - To lay the foundation for a future offense.
Spug
Noobie
*
Posts: 19


I'm a llama!

Re:Password corruption / invalidness?
« Reply #7 on: February 14, 2004, 11:06:48 PM »
Reply with quote

I'm talking about very many members here. You can change all their passwords and mail them to them if you want :P
Logged
Peter Duggan
Llama Chameleon
Global Moderator
YaBB God
*****
Posts: 1793


You come and go...

WWW
Re:Password corruption / invalidness?
« Reply #8 on: February 14, 2004, 11:58:18 PM »
Reply with quote

Quote from: Spug on February 14, 2004, 11:06:48 PM
I'm talking about very many members here.

Changing them manually *might* have been your only option, but:

Quote from: [Unknown] on February 14, 2004, 01:51:24 AM
I was able to use the reminder properly.

So was I! ;)

QuotePlease make sure your users are copying and pasting the password they are being sent.

So what's wrong with mailing them all and asking them to try this?
Logged

Shadow's Pawn
Support Team
YaBB God
*****
Posts: 597


ich soll nicht toten

ICQ - 8039201shadowpawn@hotmail.com WWW
Re:Password corruption / invalidness?
« Reply #9 on: February 15, 2004, 04:45:08 AM »
Reply with quote

If they can't manage to copy and paste the random password in properly (I've had a couple users that couldn't do this) then you might want to check out the mod to make the random passwords completely numerical.

That way the majority of your users should be able to do it themselves.  Then if there are still a few who can't resolve it themselves, you can always just change it manually.
Logged

apologize \A*pol"o*gize\, v. i. - To lay the foundation for a future offense.
Pages: [1] Reply Ignore Print 
YaBB SE Community  |  English User Help  |  English Help  |  Password corruption / invalidness? « previous - next »
 


Powered by MySQL Powered by PHP YaBB SE Community | Powered by YaBB SE
© 2001-2003, YaBB SE Dev Team. All Rights Reserved.
SMF 2.1.4 © 2023, Simple Machines
Valid XHTML 1.0! Valid CSS

Page created in 0.111 seconds with 20 queries.