Bug 31246 – schoolexam: project directory syntax not validated on input

Bug 31246 - schoolexam: project directory syntax not validated on input


Summary:	schoolexam: project directory syntax not validated on input

Status:	RESOLVED DUPLICATE of bug 31158

Product:	UCS@school
Classification:	Unclassified
Component:	UMC - Exam mode
Version:	UCS@school 3.1
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	Bugzilla Mailingliste
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-04-30 14:25 CEST by Arvid Requate
Modified:	2013-05-06 11:43 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
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 Arvid Requate

2013-04-30 14:25:43 CEST

Creating a schoolexam the name "/dir1" was sepcified for the project directory and the UMC-wizzard accepted the input. Only at the final moment of creation the teacher gets stuck with an error message:

An error occurred during the preparation of the exam. The following information will show more details about the exact error. Please retry to start the exam.

An unexpected error occurred during installation: Das angegebene Projektverzeichnis darf nicht das Zeichen "/" enthalten.

Since there is no back button at this point, the teacher can only abort the whole operation and try again.

The wizzard should validate the input directly and in case of an error a back-button should be offered.

Comment 1 Alexander Kläser

2013-05-06 11:43:26 CEST

Absolutely correct, this shortcomings have already been noted down :) .

*** This bug has been marked as a duplicate of bug 31158 ***