UBB.threads PHP Forum Software Community Forums UBB.threads 6 Version 6 Support error editig profile after updating to 6.5

after i upgraded from v6.4 all seemed to work fine. but when a user wants to edit his profil the following sql-error is displayed:

when i look at the database, there is realy no field u_profilehash.


another question: is it possible in 6.5 to edit the stored user password? when i send the user a new password from the admin console, he getS' the mail with the new pw but can only login with the old. strange.

Looks like you missed the 6.4.1 altertable - you'll probably want to re-run it.

You can change a user's password by using the following command in the Database Tools -> SQL Command area:



Replace "password" with the new password. Keep the quotes.

Replace 0 with the user's number. If you don't know the user's number, you can try:



... replacing "Display Name" with the user's display name. Keep the quotes.

Do note that the email retrieval feature actually sets a temporary password instead of reminding the user of his current password. MD5 is a one-way function that can not be decrypted.

i'm sure i've run the altertable to 6.41.
but i'll try to run it again.

i understand the temporary password thing. the problem is the mail with the temp pw is send but the user can only login with the old pw.

wasn't in v6.4 the possibility to set a new pw for a user in the admin area?

ok, i've run the altertable from 6.4 to 6.41 again and now it works. but how about the altertable to 6.5? it says it can only be run within the upgrade process which i did already and which worked without errors.

very strange.

If the 6.5 upgrade install didn't do the altertables, you'd know it, I assure you. <img src="https://www.ubbcentral.com/boards/images/graemlins/smile.gif" alt="" />

that's was i thought also <img src="https://www.ubbcentral.com/boards/images/graemlins/smirk.gif" alt="" />

so it remains the question how it's possible the the db row disappears after a succesful update and can be restored with a new altertable run.

It is possible that the first time you ran the 6.4.1 alter, it did not actually complete. Adding the column to the users table is the last thing done. Earlier operations could potentially have timed out.

You're certainly not alone in having this happen.