View Issue Details

This bug affects 1 person(s).
 2
IDProjectCategoryView StatusLast Update
20324Bug reportsSurvey participants (Tokens)public2025-11-07 17:15
Reporterrnelson@dep.net Assigned Togabrieljenik  
PrioritynoneSeverityminor 
Status assignedResolutionopen 
Product Version6.5.x 
Summary20324: Keep token linked info (attributes) when changing language in survey
Description

I have built two multilingual and restricted to a specific group of participants surveys in LimeSurvey. In one of them, for some conditional questions, I use attributes from the participant table (e.g., TOKEN:ATTRIBUTE_1 = 1) so the survey doesn’t need to ask for information I already have. In the second one, I use attributes from the participant table just to give a reference to the participant at the top of every group of qüestions. As this second survey is less complex and exposes the same bug the first one does, I use the second one for this bug report.
Step 1: Programming and expected output
Screenshot 1 (Use of token attribute, language A)

Screenshot 2 (Screen output for user with language A)

Screenshot 3 (Use of token attribute, language B)

Screenshot 4 (Screen output for user with language B)

Screenshot 5 (Use of token attribute, language C)

Screenshot 6 (Screen output for user with language C)

Step 2: The issue
The issue is that when I start the survey and switch languages using the top-menu language switcher, the attribute information disappears. It doesn’t matter the initial language (language A, B or C). I use as initial language in the screenshots example language A.

Screenshot 7 (Language change)

Screenshot 8 (Language changed)

Step 3: Other scenarios
Secondly, I tested whether the token information is stored after first "next" click. To do so, I enabled the welcome page (which I usually skip to keep surveys as short as possible). Unfortunately, it didn’t work: if I change the language on page two or three of the survey, the same issue occurs.

On the other hand, I noticed that if I change the language on the welcome page —whether using the top-menu language switcher or the specific language switcher on that page—, there's no issue with the token information throughout the rest of the survey.

Screenshot 9 (Initial language at the welcome page)

Screenshot 10 (Language change)

Screenshot 11 (Language changed)

Screenshot 12 (Next page)

Finally, another scenario I tested was going forward, answering some questions, then going back to the welcome page and changing the language (either using top-menu language switcher or welcome page language switcher). In this case, the issue also occurs. So, it seems the bug is somewhat more complex; it is not just a top-menu language switcher problem through the survey.

Screenshot 12 (Page 2, also with answers in page 1)
Screenshot 13 (Page 1 with answers)
Screenshot 14 (Language change in welcome page)
Screenshot 15 (Language changed)
Screenshot 16 (Come forward to page 1 with answers)

Screenshot 16 (Come forward to page 2 with answers)

Steps To Reproduce

Have a LimeSurvey instance with:
A multilingual survey with at least three languages enabled (e.g., A, B, C).
Participants (tokens) enabled.
At least one custom participant attribute defined (e.g., ATTRIBUTE_1).
Create one participant whose token is active and has ATTRIBUTE_1 set (e.g., value 1).
Ensure the survey uses top-menu language switcher (default) and optionally the welcome-page language switcher.
(Replace this text with detailed step-by-step instructions on how to reproduce the issue)

Case 1 — Bug manifests when switching language after survey start

Open the survey link with the test token.

On the Welcome page, do not change the language. Click Next to go to Page 1.

Confirm that the attribute placeholder resolves correctly (e.g., “Reference: 1”).

Use the top-menu language switcher to change from language A → B (or A → C).

Expected result

We expect no change and that the attribute continues to be shown in the other language.

Actual result

Observed: The previously displayed attribute value disappears (placeholder renders blank/empty).
Expected: {TOKEN:ATTRIBUTE_1} continues to resolve to the same value regardless of a mid-survey language change.

(The attached Screenshots 1–6 show initial correct rendering per language; Screenshots 7–8 show the loss after switching.)

TagsNo tags attached.
Attached Files
Bug heat2
Complete LimeSurvey version number (& build)LimeSurvey Cloud Version 6.15.20
I will donate to the project if issue is resolvedNo
BrowserGoogle Chrome, Edge
Database type & versionLimeSurvey Cloud Version 6.15.20
Server OS (if known)
Webserver software & version (if known)
PHP VersionLimeSurvey Cloud Version 6.15.20

Users monitoring this issue

There are no users monitoring this issue.

Activities

tibor.pacalat

tibor.pacalat

2025-11-07 17:15

administrator   ~83722

Thank you for great bug report! Hopefully it will get resolved soon.

Issue History

Date Modified Username Field Change
2025-10-27 11:29 rnelson@dep.net New Issue
2025-10-27 11:29 rnelson@dep.net File Added: BugReport_InfoAttributeProblem.docx
2025-10-27 11:29 rnelson@dep.net File Added: survey_archive_156742.lsa
2025-10-27 11:29 rnelson@dep.net File Added: limesurvey_survey_156742.lss
2025-11-07 16:55 tibor.pacalat View Status private => public
2025-11-07 16:55 tibor.pacalat Bug heat 6 => 0
2025-11-07 17:15 tibor.pacalat Note Added: 83722
2025-11-07 17:15 tibor.pacalat Bug heat 0 => 2
2025-11-07 17:15 tibor.pacalat Assigned To => gabrieljenik
2025-11-07 17:15 tibor.pacalat Status new => assigned