The following warnings occurred:
Warning [2] Undefined variable $unreadreports - Line: 26 - File: global.php(961) : eval()'d code PHP 8.1.2-1ubuntu2.14 (Linux)
File Line Function
/global.php(961) : eval()'d code 26 errorHandler->error
/global.php 961 eval
/showthread.php 28 require_once





× This forum is read only. As of July 23, 2019, the UserSpice forums have been closed. To receive support, please join our Discord by clicking here. Thank you!

  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
edit bio
#1
Hi,

Sorry, still using Version 4.1.3. After adding and deleting several users, I noticed that editing the bio in edit_profile.php had no effect, i.e. nothing has been written to the data base.
Thus, I found that in the data base in the profiles tab, the id and the user_id can differ.
So I think that in edit_profile.php the data base update has to use the id and not the user_id.
A change of
Code:
$db->update('profiles',$userID,$fields);
to
Code:
$db->update('profiles',$thisProfile->id,$fields);
worked for me.

Cheers,
Sebastian

  Reply
#2
Hmm. Interesting. I was pretty sure that was patched. Is there a reason you can't patch to 4.1.5?
  Reply
#3
Sure, I will patch to 4.1.5 soon. However, I have looked into 4.1.4b and 4.1.5 and I've not found a new edit_profile.php ... or did you fix this issue somehow differently?
  Reply
#4
Well, I'm not in front of the code, so I'll have to look but either somehow you missed a patch somewhere along the way or I reintroduced a bug I've already fixed. That wouldn't be the first time. I did that in 4.2 also. Either way, thanks for pointing it out....I will definitely take a look.
  Reply
#5
Definitely, I will not exclude having missed a patch ;-) Thanks again for taking a look.
  Reply
#6
I did confirm that this bug was fixed a while ago and isn't in 4.1.5. I'll push it out anyway just in case I reintroduced it, but line 29 should read
$userID = $user->data()->id;
  Reply
#7
Thanks for checking that. I can also confirm that line 29 reads exactly as you mentioned. However it is still not clear to me. Have other users not observed these problems? As I said above, the userID cannot work in this case, if the DB id and the userID differ, thus I needed to use $thisProfile->id instead of $userID.
Or have you fixed this issue by guaranteeing that the DB id (in the profiles tab) and the userID always are the same?
  Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)