View Issue Details

This issue affects 1 person(s).
 2
IDProjectCategoryView StatusLast Update
17986Bug reports_ Unknownpublic2022-05-05 19:14
Reporterzufolo441 Assigned Togabrieljenik  
PrioritynoneSeverityminor 
Status closedResolutionfixed 
Product Version5.2.x 
Summary17986: data integrity check doesn't work
Description

Hi, when I launch data integrity check I obtain this error:

Undefined array key "qid"
/var/www/limesurvey-qsnap/application/controllers/admin/CheckIntegrity.php(763)
763 if (!array_key_exists($condition['qid'], $okQuestion)) {

I checked previous versions of LS and I found that this line of code is sligthly different:
// skip case with cqid=0 for codnitions on {TOKEN:EMAIL} for instance
if (!array_key_exists($condition['cqid'], $okQuestion)) {

Can I simply modify 'qid' in 'cqid' or is the problem elsewhere?

thanks.

Steps To Reproduce

Steps to reproduce

(Replace this text with detailed step-by-step instructions on how to reproduce the issue)

Expected result

(Write here what you expected to happen)

Actual result

(Write here what happened instead)

TagsNo tags attached.
Bug heat2
Complete LimeSurvey version number (& build)5.3.5
I will donate to the project if issue is resolvedNo
BrowserFirefox 98
Database type & versionPostgresql 13
Server OS (if known)FreeBSD 13
Webserver software & version (if known)Nginx + php-fpm
PHP Version8.0

Users monitoring this issue

There are no users monitoring this issue.

Activities

gabrieljenik

gabrieljenik

2022-05-05 19:14

manager   ~69433

Hello zufolo441,
This should already be fixed in recent versions (17989).
Can you please check if this issue still exists in the latest version of LimeSurvey and let us know?
Thank you!

Issue History

Date Modified Username Field Change
2022-03-24 08:56 zufolo441 New Issue
2022-03-24 10:51 galads Assigned To => galads
2022-03-24 10:51 galads Status new => acknowledged
2022-05-04 08:28 galads Assigned To galads => gabrieljenik
2022-05-04 08:28 galads Status acknowledged => assigned
2022-05-05 19:14 gabrieljenik Status assigned => closed
2022-05-05 19:14 gabrieljenik Resolution open => fixed
2022-05-05 19:14 gabrieljenik Note Added: 69433
2022-05-05 19:14 gabrieljenik Bug heat 0 => 2