View Issue Details

Jump to NotesJump to History
This bug affects 1 person(s).
 4
IDProjectCategoryView StatusDate SubmittedLast Update
13893Bug reportsCentral participant databasepublic2018-07-20 19:112019-05-23 10:03
Reportersocius Assigned Toc_schmitz  
PrioritynoneSeverityminor 
Status closedResolutionwon't fix 
Summary13893: 2.6.7 LTS
Description

When creating participants for a certain survey token table via CPDB the attribute_ID for the attribute in the survey token table does not start at "1". If the attributes in the survey token table are created manually the ID correctly starts at "1"

In short:

  • Auto adding attribute via CPDB : starts at 'last done' + 1 (= Number of attributes in the DB + 1)
  • Adding via token attribute management : start at 1

A description w/ screenshot:
https://www.limesurvey.org/forum/can-i-do-this-with-limesurvey/115892-delete-attributes-from-token-table-to-start-attribute_id-at-attribute_1-again

Steps To Reproduce

1) Create CPDB with additional attributes via .csv - upload
2) Create participants from the CPDB in a certain survey token table - also create attributes from the CPDB there
3) Delete survey token table
4) Initialize new token table
5) Delete attributes from token table (they are still there, also after deletion of the token table in §)
6) Repeat 2) Create participants from CPDB again

-> The attribute_ID does not start at 1, but at n+1, where n seems the number of attributes that were created in 2)

If the attributes are created manually via "Add attribute" in the survey token table the attribute_ID starts correctly with "1".

TagsCPDB
Bug heat4
Complete LimeSurvey version number (& build)2.6.7-lts Build 171212
I will donate to the project if issue is resolvedNo
BrowserFirefox
Database type & versionMariaDB 10.1.14
Server OS (if known)Linux
Webserver software & version (if known) Apache/2.2.15 (Red Hat)
PHP Version5.6.36

Users monitoring this issue

socius

Activities

c_schmitz

c_schmitz

2019-05-23 10:03

administrator   ~52062

Last edited: 2019-05-23 10:03

I am sorry but we do not fix bugs in 2.6.7 anymore as support has ended. Plea update to the latest 3.x version.

Issue History

Date Modified Username Field Change
2018-07-20 19:11 socius New Issue
2018-07-20 19:14 socius Issue Monitored: socius
2018-08-16 15:48 socius Tag Attached: CPDB
2018-08-16 15:48 socius Tag Detached: CPDB
2018-08-16 15:48 socius Tag Attached: CPDB
2018-08-17 10:59 LouisGac Assigned To => c_schmitz
2018-08-17 10:59 LouisGac Status new => assigned
2019-05-23 10:03 c_schmitz Status assigned => closed
2019-05-23 10:03 c_schmitz Resolution open => fixed
2019-05-23 10:03 c_schmitz Note Added: 52062
2019-05-23 10:03 c_schmitz Note Edited: 52062
2019-05-23 10:03 c_schmitz Resolution fixed => won't fix
2021-08-28 23:20 guest Bug heat 2 => 4