Bug 30050 - Error message for internet rules name is hard to read
Error message for internet rules name is hard to read
Status: RESOLVED WONTFIX
Product: UCS@school
Classification: Unclassified
Component: UMC - Internet rules
UCS@school 3.1
Other Linux
: P5 minor (vote)
: UCS@school 3.x
Assigned To: UCS@school maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-01-17 18:09 CET by Dirk Wiesenthal
Modified: 2019-02-05 21:26 CET (History)
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): Usability
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Wiesenthal univentionstaff 2013-01-17 18:09:56 CET
The error message shown if the name of the internet rule is not valid wrt ucr.validate_key() is hard to read. The letter " is forbidden three times (*very* forbidden) and the commas between these letters are confusing. It would be much better to read if they would be left out.

By the way, I do not think that ucs-school-umc-internetrules is the right place for the error message. It should go into ucr itselt as changes to the validate_key function could lead to changes in this module, which is probably undesired. One should also scan for other uses of the function and if they provide their very own error message.
Comment 1 Dirk Wiesenthal univentionstaff 2013-01-17 18:23:28 CET
Oh, I suppose two of the three " were enclosing a comma, which is also forbidden. +1 for removing the commas in the message.
Comment 2 Sönke Schwardt-Krummrich univentionstaff 2019-02-05 21:26:33 CET
This issue has been filled against UCS@school 3.2. The maintenance with
bug and security fixes for UCS@school 3.2 has ended on Dec 31, 2016.

Customers still on UCS 3.x are encouraged to update to UCS 4.3 (or later). 
Please contact your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug"
or simply reopen the issue. In this case please provide detailed information on
how this issue is affecting you.