View Issue Details

This issue affects 1 person(s).
 12
IDProjectCategoryView StatusLast Update
15339Bug reportsInstallationpublic2026-10-07 23:33
ReporterDenisChenu Assigned Toc_schmitz  
PrioritynoneSeverityminor 
Status closedResolutionfixed 
Product Version3.17.x 
Summary15339: Installer must check max_input_vars value and send a warning
Description

See https://manual.limesurvey.org/Troubleshooting#After_submitting_a_page.2C_you_end_up_on_the_general_index_page.2Fon_a_404_page_or_you_get_the_message_.27The_CSRF_token_could_not_be_verified.27
A lot of potential issue with max_input_vars
Then i think we must check it and send a warning when it was below 3000 ?

TagsNo tags attached.
Bug heat12
Complete LimeSurvey version number (& build)3.18.0
I will donate to the project if issue is resolvedNo
Browsernot relevant
Database type & versionnot relevant
Server OS (if known)not relevant
Webserver software & version (if known)not relevant
PHP VersionPHP7

Relationships

related to 15327 closedDenisChenu Bug reports Data export stops after exactly 980 columns 
related to 15340 new Feature requests Show a warning in export if max_input_vars OR allow «export ALL» 
related to 16319 closedollehar Bug reports Labelset with 215 items save only the first 111 

Users monitoring this issue

There are no users monitoring this issue.

Activities

Mazi

Mazi

2019-09-30 09:25

updater   ~53740

@DenisChenu, that setting is famous for causing weird issues with larger surveys. Since the default value is just 1000 we always raise it to 10000 just in case (what can it hurt?). So I think a limit of 3000 is fine but 5000 or even 10000 would be better if there are no serious side effects,

DenisChenu

DenisChenu

2019-09-30 17:41

developer   ~53788

@Mazi : i think we must always test if "Last input posted" are sent to server.
Some survey system can live with 1000 without any issue …

But send a error if last POST value is not set when

  1. Export
  2. Manage answer/labels
  3. Survey (send by email here)

must be done too :)

ollehar

ollehar

2019-10-01 13:21

reporter   ~53797

This issue can be closed if there already is a feature request, no?

DenisChenu

DenisChenu

2019-10-01 14:46

developer   ~53798

@ollehar : no, not same feature. Can be in feature request, but the other one if when export

Mazi

Mazi

2020-09-01 11:39

updater   ~59671

@cdorin: Adding that check should be pretty simple. Can we add that really useful feature to LS 3.x and 4.x?

ollehar

ollehar

2020-09-01 11:51

reporter   ~59672

Bug fixing is still priority.

jelo

jelo

2020-09-02 11:58

partner   ~59681

All these check should not be done in the installer alone. All these checks should be avaiable from the installation itself. It helps detecting change in the hosting environment after installation and the code is getting tested not only a fraction of users which install LimeSurvey. The code is tested all the time when available in the LimeSurey application.

c_schmitz

c_schmitz

2026-10-03 09:21

administrator   ~86191

Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=40666

c_schmitz

c_schmitz

2026-10-03 09:21

administrator   ~86192

Added a check for this. The installer now warns if important PHP settings are too low, without blocking the installation. The same check is also on the "Check data integrity" page, and it can be turned off if needed.

LimeBot

LimeBot

2026-10-07 23:33

administrator   ~86252

Fixed in Release 7.5.1+261007

Related Changesets

LimeSurvey: master c21e4d8d

2026-10-03 09:21

c_schmitz


Details Diff
Fixed issue 15339: PHP limits that were too low (e.g. max_input_vars) caused data loss with large surveys without any warning
Dev Installer precheck and Check data integrity show recommended PHP settings (memory_limit, max_input_vars, post_max_size, upload_max_filesize), the integrity check section can be hidden with $config['showserverconfigurationcheck']
Affected Issues
15339
mod - application/config/config-defaults.php Diff File
mod - application/controllers/admin/CheckIntegrity.php Diff File
mod - application/models/InstallerConfigForm.php Diff File
mod - application/views/admin/checkintegrity/check_view.php Diff File
mod - application/views/installer/precheck_view.php Diff File

Issue History

Date Modified Username Field Change
2019-09-29 10:54 DenisChenu New Issue
2019-09-29 10:54 DenisChenu Relationship added related to 15327
2019-09-30 09:25 Mazi Note Added: 53740
2019-09-30 17:41 DenisChenu Note Added: 53788
2019-09-30 17:42 DenisChenu Relationship added related to 15340
2019-10-01 13:21 ollehar Note Added: 53797
2019-10-01 13:21 ollehar Status new => feedback
2019-10-01 14:46 DenisChenu Note Added: 53798
2019-10-01 14:46 DenisChenu Status feedback => new
2020-05-22 17:46 DenisChenu Relationship added related to 16319
2020-09-01 11:39 Mazi Note Added: 59671
2020-09-01 11:51 ollehar Note Added: 59672
2020-09-02 11:58 jelo Note Added: 59681
2026-10-03 09:21 c_schmitz Changeset attached => LimeSurvey master c21e4d8d
2026-10-03 09:21 c_schmitz Note Added: 86191
2026-10-03 09:21 c_schmitz Assigned To => c_schmitz
2026-10-03 09:21 c_schmitz Status new => resolved
2026-10-03 09:21 c_schmitz Resolution open => fixed
2026-10-03 09:21 c_schmitz Bug heat 8 => 10
2026-10-03 09:21 c_schmitz Note Added: 86192
2026-10-07 23:33 LimeBot Note Added: 86252
2026-10-07 23:33 LimeBot Status resolved => closed
2026-10-07 23:33 LimeBot Bug heat 10 => 12