Bug 128553 - Change to /cve/ template
Summary: Change to /cve/ template
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Network
Classification: Retired
Component: RHN/Web Site
Version: rhn340
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jesus M. Rodriguez
QA Contact: Mark J. Cox
URL:
Whiteboard:
Depends On:
Blocks: 120693
TreeView+ depends on / blocked
 
Reported: 2004-07-26 12:24 UTC by Mark J. Cox
Modified: 2007-04-18 17:09 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-09-09 18:05:50 UTC
Embargoed:


Attachments (Terms of Use)

Description Mark J. Cox 2004-07-26 12:24:43 UTC
The fixes to /cve/ have not yet been pushed live - so I'd like to make
a suggestion for a minor display change.

In /rhn/web/titan_html/errata_hidden/cve_details.pxi

Currently "Errata >\n Updated packages to correct...."

Change to "Errata >\n <some heading>CAN-2004-0001</some heading> \n
Updated packages to correct...."

With the corresponding Snigglet change so you can substitute in the
CVE name, make sure it gets sanitized ((C\s\s-\d{4}-\d{4}) is safe) to
ensure no nasty cross-site-scripting.

Some heading could be similar to that used for the /errata/
<font style="color:#990000; font-family:helvetica;
text-decoration:none; font-size:14pt; font-weight:bold;">

Comment 1 Chip Turner 2004-07-26 12:43:32 UTC
assigning to rhn350hosted to see if there's time to fix it for this
release

Comment 2 Jesus M. Rodriguez 2004-07-26 15:52:14 UTC
Added the ability to display CVE/CAN title as a heading to the details
page.

Comment 3 Jesus M. Rodriguez 2004-07-26 15:52:34 UTC
Changing status to ondev.

Comment 4 Mark J. Cox 2004-07-26 15:55:08 UTC
looks good to me.

Comment 5 Fanny Augustin 2004-07-26 16:02:42 UTC
Mark,

Are you testing this bug?  If so, I will change the QA contact to you.
 Change it back to me with a note if this is not the case.

Comment 6 Mark J. Cox 2004-07-27 07:44:18 UTC
yes, this works as expected.


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