Project

General

Profile

Bug #5678

Fill the blank test doesn't work if the text to find is utf-8

Added by Hubert Borderiou almost 7 years ago. Updated about 4 years ago.

Status:
Bug resolved
Priority:
Normal
Assignee:
Category:
Exercises
Target version:
Start date:
26/10/2012
Due date:
% Done:

50%

Estimated time:
Complexity:
Normal
SCRUM pts - complexity:
?

Description

I've got a question Fill the blank for a russian course.
The texte to find is utf-8
The text to find has been replace with ??
I've tested it in stable.chamilo.org


Files

ruso.png (16 KB) ruso.png Julio Montoya, 30/10/2012 14:41
Selection_002.png (13.2 KB) Selection_002.png Julio Montoya, 02/09/2015 07:40

Associated revisions

Revision c968876c (diff)
Added by Julio Montoya over 6 years ago

Creating main tables with UTF8 adding "DEFAULT CHARACTER SET utf8 DEFAULT COLLATE utf8_general_ci" see #5678

History

#1

Updated by Julio Montoya almost 7 years ago

  • Status changed from New to Assigned
  • Assignee set to Julio Montoya

testing

#2

Updated by Julio Montoya almost 7 years ago

  • File ruso.png ruso.png added
  • Status changed from Assigned to Needs more info
  • Assignee deleted (Julio Montoya)

Works for me with the latest chamilo code 1.9.4

#3

Updated by Hubert Borderiou almost 7 years ago

I've tested again in stable.chamilo.org, and actually, the issue occured when I put the right answer in the test.
If I put the wrong answer, it is ok.
(this doesn't motivate to put the right answer ;-) )

#4

Updated by Julio Montoya almost 7 years ago

Can you share to the world your Russian exercise? :)

#6

Updated by Julio Montoya almost 7 years ago

I think the problem is in the DB enconding.
In my installation I have this:


mysql> use chamilo;
mysql> show variables like "character_set_database";
+------------------------+-------+
| Variable_name          | Value |
+------------------------+-------+
| character_set_database | utf8  |
+------------------------+-------+
1 row in set (0.00 sec)

mysql> show variables like "collation_database";
+--------------------+-----------------+
| Variable_name      | Value           |
+--------------------+-----------------+
| collation_database | utf8_general_ci |
+--------------------+-----------------+
1 row in set (0.00 sec)

And in stable.chamilo:

mysql> use chamilostable;
mysql> show variables like "character_set_database";
+------------------------+--------+
| Variable_name          | Value  |
+------------------------+--------+
| character_set_database | latin1 |
+------------------------+--------+
1 row in set (0.00 sec)

mysql> show variables like "collation_database";
+--------------------+-------------------+
| Variable_name      | Value             |
+--------------------+-------------------+
| collation_database | latin1_swedish_ci |
+--------------------+-------------------+
1 row in set (0.00 sec)

#7

Updated by Julio Montoya almost 7 years ago

And when checking the course tables example "c_quiz_answer" utf8 is ok

mysql> SELECT CCSA.character_set_name FROM information_schema.`TABLES` T,        information_schema.`COLLATION_CHARACTER_SET_APPLICABILITY` CCSA WHERE CCSA.collation_name = T.table_collation   AND T.table_schema = "stablechamilo"   AND T.table_name = "c_quiz_answer";
+--------------------+
| character_set_name |
+--------------------+
| utf8               |
+--------------------+
1 row in set (0.00 sec)
#8

Updated by Julio Montoya almost 7 years ago

  • Status changed from Needs more info to Assigned
  • Assignee set to Julio Montoya

I remember that someone else already reported that problem

#9

Updated by Julio Montoya almost 7 years ago

well, this requires a DB change at least in the migration process, so I can't add it to 1.9.4

The idea is to add an "DEFAULT CHARACTER SET utf8 DEFAULT COLLATE utf8_general_ci" when creating a table for the main.sql, stats.sql and

#10

Updated by Julio Montoya almost 7 years ago

  • Status changed from Assigned to Needs testing
  • % Done changed from 0 to 50
#11

Updated by Hubert Borderiou almost 7 years ago

Hi,
does it convert existing tables from latin1 to utf-8 ?

#12

Updated by Julio Montoya almost 7 years ago

  • Status changed from Needs testing to Assigned

Not yet I will do a migration process

#13

Updated by Yannick Warnier over 6 years ago

  • Target version set to 1.9.6
#14

Updated by Julio Montoya over 6 years ago

  • Target version changed from 1.9.6 to 2.0

This requires DB changes moving to 1.10

#15

Updated by Yannick Warnier about 4 years ago

  • Status changed from Assigned to Needs testing
  • Target version changed from 2.0 to 1.10.0

Julio, I believe this has been fixed now in 1.10.0 (through a task reported by Laura)... can you confirm?
If so, please mark this issue as resolved.

#16

Updated by Julio Montoya about 4 years ago

Works for me.

Also available in: Atom PDF