Bug 975593 - [RFE] Make name field validation consistent across entities, and use the non-html validator
Summary: [RFE] Make name field validation consistent across entities, and use the non-...
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: Nightly
Hardware: Unspecified
OS: Unspecified
medium vote
Target Milestone: Unspecified
Assignee: Bryan Kearney
QA Contact: Tazim Kolhar
Depends On:
TreeView+ depends on / blocked
Reported: 2013-06-18 20:51 UTC by Jeff Weiss
Modified: 2019-09-26 18:19 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Last Closed: 2014-07-02 14:08:50 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Jeff Weiss 2013-06-18 20:51:39 UTC
Right now, the org name validator disallows these characters:  .^&%$# etc plus a lot of UTF8 chars.  This is overly strict.

After discussing on irc, seems to be agreement that all entities' name field should use the "non-html" validator that allows all chars except: <>/

Comment 1 RHEL Program Management 2013-06-18 21:02:47 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 3 Adam Price 2013-07-09 20:37:40 UTC
it has been agreed upon that 'name' should allow all characters, but 'label' should be restricted under the hood.

this may include fixes in the javascript to correctly display special characters.

Comment 4 Payal Godhani 2013-07-11 18:48:53 UTC

Comment 7 Mike McCune 2013-10-17 21:01:27 UTC
Moving this to be tested during MDP3, not critical for MDP2 success story

Comment 8 Tazim Kolhar 2014-05-08 06:51:11 UTC

Comment 9 Bryan Kearney 2014-07-02 14:08:50 UTC
This was delivered with 6.0.3, which is the Satellite 6 Beta.

Comment 10 Bryan Kearney 2014-07-02 14:10:18 UTC
This was delivered in 6.0.3, the Beta version of Satellite 6.0

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