search

google-code-export / oppia

Automatically exported from code.google.com/p/oppia
Apache License 2.0
4 stars 0 forks source link

Cannot upload explorations with unicode characters #158

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.On Oppia.org, Find exploration in Create tab (in my case, it was "The 'Good 
Times' Sample"
2. Click "Copy"
3.Get  butterbar error(see attachment) and JS errors (see below)

(Looks like Clone was still created successfully though)

Failed to load resource: the server responded with a status of 500 (Internal 
Server Error) https://www.oppia.org/contributehandler/clone
'ascii' codec can't decode byte 0xd0 in position 21: ordinal not in range(128) 
angular.js:8296
(anonymous function) angular.js:8296

Original issue reported on code.google.com by yana...@google.com on 30 Mar 2014 at 9:14

Attachments:

GoogleCodeExporter commented 9 years ago

Original comment by yana...@google.com on 30 Mar 2014 at 9:14

GoogleCodeExporter commented 9 years ago

Original comment by yana...@google.com on 30 Mar 2014 at 9:15

GoogleCodeExporter commented 9 years ago 
I investigated this a bit by downloading a zip file of the exploration and 
uploading it to a local instance. It refuses to upload, giving this traceback:

  File "/opensource/oppia/core/domain/exp_domain.py", line 1111, in from_yaml
    exploration_dict = utils.dict_from_yaml(yaml_content)
  File "/opensource/oppia/utils.py", line 197, in dict_from_yaml
    raise InvalidInputException(e)
InvalidInputException: 'utf8' codec can't decode byte #x8a: invalid start byte
  in "<string>", position 10

This might be something to do with strange characters in the YAML, but I am not 
sure:

      value: ... It was released on their album <i>Risqu\xE9\</i> and proved a big hit.

Original comment by s...@seanlip.org on 31 Mar 2014 at 7:41

GoogleCodeExporter commented 9 years ago 
I also noticed (much later) that the exploration used an image, and the image 
did not get copied over to the new exploration, or get linked properly. so it 
was broken in the clone.
(or should I file a new bug for that?)

Original comment by yana...@google.com on 31 Mar 2014 at 4:32

GoogleCodeExporter commented 9 years ago 
Changing the issue title, since exploration cloning is no longer supported.

Original comment by s...@seanlip.org on 22 Aug 2014 at 4:43