View Issue Details

Jump to NotesJump to History
This issue affects 1 person(s).
 6
IDProjectCategoryView StatusDate SubmittedLast Update
20665Bug reportsComfortUpdatepublic2026-09-01 10:302026-09-01 14:33
ReporterJHulaas Assigned Toc_schmitz  
PrioritynoneSeverityminor 
Status closedResolutionduplicate 
Summary20665: Missing PostgreSQL version and webserver config tests before upgrading to version 7
Description

When upgrading LimeSurvey from v6 to v7, ComfortUpdate should verify the version of the PostgreSQL server.
In our case, we were using PostgreSQL version 13, and ComfortUpdate did not block us even though version 14 is required for LimeSurvey 7.
I'm also wondering if it's feasible for ComfortUpdate to check the new configuration settings of Apache that are required by LimeSurvey 7: things like letting the web server pass the /editor/ folder directly and transmit the Authorization header to PHP.

Steps To Reproduce

Steps to reproduce

Start with LimeSurvey 6 (latest version, on top of PostgreSQL 13) and use ComfortUpdate to upgrade to version 7.

Expected result

ComfortUpdate should block, or at least warn that the PostgreSQL server is too old for LimeSurvey 7. If possible, also block or warn upon missing web server configuration.

Actual result

ComfortUpdate freezes during the upgrade. The database upgrade does not take place. When logging into LimeSurvey as a user, the version displayed is v7.0.11, as if the upgrade were successful. When editing a survey, the browser console is full of HTTP errors 404 and 500.

TagsNo tags attached.
Bug heat6
Complete LimeSurvey version number (& build)6.17.16
I will donate to the project if issue is resolvedNo
Story point estimate0
Browser
Database type & versionPostgreSQL 13.20
Server OS (if known)Rocky Linux release 9.6
Webserver software & version (if known)Apache 2.4.62
PHP Version8.2.28

Relationships

Relationship GraphDependency Graph
duplicate of 20624 closedc_schmitz DB crash when updating from 7.0.5 to 7.0.7 due to missing DB version check 

Users monitoring this issue

DenisChenu, JHulaas

Activities

Mazi

Mazi

2026-09-01 11:07

updater   ~85536

Looks like this is similar to 20624 but for Postgres DB.

Issue History

Date Modified Username Field Change
2026-09-01 10:30 JHulaas New Issue
2026-09-01 10:45 JHulaas Issue Monitored: JHulaas
2026-09-01 10:45 JHulaas Bug heat 0 => 2
2026-09-01 11:03 DenisChenu Issue Monitored: DenisChenu
2026-09-01 11:03 DenisChenu Bug heat 2 => 4
2026-09-01 11:06 Mazi Relationship added related to 20624
2026-09-01 11:07 Mazi Note Added: 85536
2026-09-01 11:07 Mazi Bug heat 4 => 6
2026-09-01 14:33 c_schmitz Relationship replaced has duplicate 20624
2026-09-01 14:33 c_schmitz Bug heat 6 => 12
2026-09-01 14:33 c_schmitz Relationship replaced duplicate of 20624
2026-09-01 14:33 c_schmitz Bug heat 12 => 6
2026-09-01 14:33 c_schmitz Assigned To => c_schmitz
2026-09-01 14:33 c_schmitz Status new => closed
2026-09-01 14:33 c_schmitz Resolution open => duplicate