View Issue Details

This bug affects 1 person(s).
 2
IDProjectCategoryView StatusLast Update
19621Bug reportsTranslationpublic2024-06-20 14:03
Reporterverena.berisha Assigned To 
PrioritynoneSeveritycrash 
Status newResolutionopen 
Product Version6.4.x 
Summary19621: Adding a language to an existing survey
Description

We set up a survey in several languages ​​and subsequently added the language DE-informal.

The base language of the survey is English. When testing the survey again, we recognized that in all languages ​​the scales of the array questions were no longer in the respective national language, but in English. All other answer options for single-choice questions were not affected.

What caused this? Is this a known bug?

After that we carried out manual revisions in all languages, which resolved the problem.

What should we pay attention to when we subsequently add (or possibly delete) a (new) language?

Steps To Reproduce

Steps to reproduce
We set up a survey in several languages (EN,DE,UK,FR,IT,TH,PL).
Participants table and Testtokens were uploaded.
After that a new language (DE-informal) was added later.

Expected result

  • We would have assumed that we would have to fill out the new translations for DE-informal
  • all other languages that were already programmed won't be affected by this change

Actual result
Instead, it turned out that in all languages (​​except the base language), the answer scales (only array) were overwritten in the base language EN. All other answer options for single-choice questions were not affected.

In a newly created survey, this BUG could NOT be reproduced using the same procedure.

TagsNo tags attached.
Bug heat2
Complete LimeSurvey version number (& build)LimeSurvey Community Edition Version 6.4.6+240212
I will donate to the project if issue is resolvedNo
BrowserMozilla Firefox
Database type & versionFirefox 122.0.1 (64-Bit
Server OS (if known)
Webserver software & version (if known)
PHP Version8.1.23

Users monitoring this issue

verena.berisha

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2024-06-20 14:02 verena.berisha New Issue
2024-06-20 14:03 verena.berisha Issue Monitored: verena.berisha
2024-06-20 14:03 verena.berisha Bug heat 0 => 2