| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 10070 | Bug reports | Central participant database | public | 2015-12-02 17:05 | 2015-12-04 15:13 |
| Reporter | blake1024 | Assigned To | c_schmitz | ||
| Priority | normal | Severity | minor | ||
| Status | closed | Resolution | fixed | ||
| Product Version | 2.06+ | ||||
| Fixed in Version | 2.06+ | ||||
| Summary | 10070: New user show language "en" but not a valid option | ||||
| Description | In the participant panel, when you list participants, many show their language as "en". However, when you utilize the dropdown for that field, "en" is not one of the options. Is it "en" or is it "English"? Use one o the other throughout. | ||||
| Tags | No tags attached. | ||||
| Bug heat | 4 | ||||
| Complete LimeSurvey version number (& build) | 151109 | ||||
| I will donate to the project if issue is resolved | No | ||||
| Browser | |||||
| Database type & version | PostgreSQL 9.3.10 | ||||
| Server OS (if known) | Linux | ||||
| Webserver software & version (if known) | Apache2 | ||||
| PHP Version | 5.5.9 | ||||
 |
Screenshot or it didn't happen. |
 |
Response quip: Fix it or you'll have fewer users. I'll get the screen shot. Thanks. |
|
|
Okay. I uploaded a screenshot. Look at the column titled "Language". It shows "en" but when you edit it, it turns into "English". It should be consistent or the user is confused about what the difference is. Although I am sure that your system is clear to you, and others who have invested a bunch of time to figure out the system, it is needlessly confusing to new users. (I have been a programmer for 35 years.) I agree that this particular report is trivial, however, your system has a lot of inconsistencies that make it needlessly confusing. For example, if you have a field called "ID" and another called "Token", what the heck is a field on another screen labeled "Token ID" ?!? (ID is too generic. Use "Participant ID".) You must pick one unique name for each unique field and use it consistently. |
|
|
Oops. Didn't press upload. It's there now. |
|
|
Yeah, I saw that you opened another report for the token ID issue - there is need to rant about this here. |
|
|
2.06+ Build 151205 released |
