Bug 56231 – Cannot distribute material containing umlauts

Bug 56231 - Cannot distribute material containing umlauts


Summary:	Cannot distribute material containing umlauts

Status:	CLOSED FIXED

Product:	UCS@school
Classification:	Unclassified
Component:	UMC - Distribution
Version:	UCS@school 5.0
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS@school 5.0 v4
Assigned To:	UCS@school maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2023-06-29 12:14 CEST by Christina Scheinig
Modified:	2023-07-06 10:58 CEST (History)
CC List:	2 users (show)

See Also:	37694 36846
What kind of report is it?:	Bug Report
What type of bug is this?:	4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?:	1: Will affect a very few installed domains
How will those affected feel about the bug?:	5: Blocking further progress on the daily work
User Pain:	0.114
Enterprise Customer affected?:
School Customer affected?:	Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2023062721000231
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Christina Scheinig

2023-06-29 12:14:27 CEST

Umlauts in the material distribution cause the material to be distributed immediately.
The material with the umlaut will not be distributed in the filesystem and cannot be uploaded again because it has already been distributed.

This can be reproduced

Comment 1 Christina Scheinig

2023-06-30 09:10:54 CEST

This material is also not possible to distribute in Exammode. So I will increase the pain.

Comment 2 J Leadbetter

2023-07-06 08:45:23 CEST

This behavior exists in version 5.0-3, and is caused by a regression related to Cherrypy in the way it decodes uploaded filenames. This is fixed in version 5.0-4, where we switch to using Tornado instead.

Please upgrade to 5.0-4 in order to fix the problem.

Comment 3 Jan-Luca Kiok

2023-07-06 10:58:03 CEST

The affected customer was asked to update -> Closing for now. If the error happens again with a current version please reopen or clone this bug.