View Issue Details

This bug affects 6 person(s).
 50
IDProjectCategoryView StatusLast Update
19866Bug reportsAuthenticationpublic2024-12-16 19:10
Reporterwfb_kunde Assigned Totibor.pacalat  
PrioritynoneSeveritypartial_block 
Status ready for testingResolutionopen 
Product Version6.6.x 
Summary19866: LimeSurvey version 6.8.2 - Reset password error
Description

Get the message 500: Internal Server Error - User::checkPasswordStrength(): Argument #1 ($password) must be of type string, null given, called in C:\inetpub\wwwroot\limesurvey\application\controllers\admin\Authentication.php on line 239 after put in new password.

Steps To Reproduce

Execute the password forgotten function, click the link and type in new password and you will get the Output above. Probably the problem is in Authentication.php on line 239 the variable $passwordTest, which is given to the function. I can's see, where it is delared an it doesn't come from the Post-variable password

TagsNo tags attached.
Bug heat50
Complete LimeSurvey version number (& build)LimeSurvey version 6.8.2
I will donate to the project if issue is resolvedNo
BrowserFirefox
Database type & versionmysql???
Server OS (if known)
Webserver software & version (if known)
PHP Version8.3

Users monitoring this issue

Activities

fradeff

fradeff

2024-12-11 09:47

reporter   ~81604

I confirm the same error (LimeSurvey version 6.8.2 , PHP Version 7.4.33, mysqlnd 7.4.33 - MariaDB); it is nearly critical as the users can't email themselves their connexion information

thumbnail_image001.jpg (56,917 bytes)   
thumbnail_image001.jpg (56,917 bytes)   
tibor.pacalat

tibor.pacalat

2024-12-12 16:18

administrator   ~81618

I am not getting this error on live. @gabrieljenik can you look into this?

Einkauf.ZIT

Einkauf.ZIT

2024-12-16 13:58

reporter   ~81637

We have also the same problem

gabrieljenik

gabrieljenik

2024-12-16 19:10

manager   ~81642

There is already a commit from @c_schmitz
https://github.com/LimeSurvey/LimeSurvey/commit/3b677da62cd4a7a325349068cac7110d2bde642d

@tibor.pacalat can you confirm if this issue is still reproducible on master?

Issue History

Date Modified Username Field Change
2024-12-05 14:23 wfb_kunde New Issue
2024-12-05 16:04 thws_jp Issue Monitored: thws_jp
2024-12-05 16:04 thws_jp Bug heat 0 => 2
2024-12-09 15:54 zweikampfsieger Bug heat 2 => 8
2024-12-09 15:55 zweikampfsieger Issue Monitored: zweikampfsieger
2024-12-09 15:55 zweikampfsieger Bug heat 8 => 10
2024-12-10 11:54 Crag Issue Monitored: Crag
2024-12-10 11:54 Crag Bug heat 10 => 12
2024-12-10 11:55 Crag Bug heat 12 => 18
2024-12-10 18:48 dschmidtke Issue Monitored: dschmidtke
2024-12-10 18:48 dschmidtke Bug heat 18 => 20
2024-12-10 18:48 guest Bug heat 20 => 26
2024-12-11 08:10 KaBeLin Issue Monitored: KaBeLin
2024-12-11 08:10 KaBeLin Bug heat 26 => 28
2024-12-11 08:10 KaBeLin Bug heat 28 => 34
2024-12-11 09:47 fradeff Note Added: 81604
2024-12-11 09:47 fradeff File Added: thumbnail_image001.jpg
2024-12-11 09:47 fradeff Bug heat 34 => 36
2024-12-12 16:18 tibor.pacalat Note Added: 81618
2024-12-12 16:18 tibor.pacalat Bug heat 36 => 38
2024-12-12 16:18 tibor.pacalat Assigned To => gabrieljenik
2024-12-12 16:18 tibor.pacalat Status new => assigned
2024-12-16 11:29 guest Bug heat 38 => 44
2024-12-16 13:52 Einkauf.ZIT Issue Monitored: Einkauf.ZIT
2024-12-16 13:52 Einkauf.ZIT Bug heat 44 => 46
2024-12-16 13:58 Einkauf.ZIT Note Added: 81637
2024-12-16 13:58 Einkauf.ZIT Bug heat 46 => 48
2024-12-16 19:10 gabrieljenik Note Added: 81642
2024-12-16 19:10 gabrieljenik Bug heat 48 => 50
2024-12-16 19:10 gabrieljenik Assigned To gabrieljenik => tibor.pacalat
2024-12-16 19:10 gabrieljenik Status assigned => ready for testing