View Issue Details

IDProjectCategoryView StatusLast Update
15339Bug reportsInstallationpublic2020-06-25 15:20
ReporterDenisChenu Assigned To 
PrioritynoneSeverityminor 
Status newResolutionopen 
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.
Complete LimeSurvey version number (& build)3.18.0
I will donate to the project if issue is resolvedNo
Browsernot relevant
Database & DB-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 
related to 14772 assignedDenisChenu Development  Review default config.php when installing 

Activities

Mazi

Mazi

2019-09-30 09:25

partner   ~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

administrator   ~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

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-06-25 15:20 DenisChenu Relationship added related to 14772