Bug 114774 - Badly formed Internal Link causes stack trace
Summary: Badly formed Internal Link causes stack trace
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Enterprise CMS
Classification: Retired
Component: content types
Version: nightly
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: ccm-bugs-list
QA Contact: Jon Orris
URL:
Whiteboard:
Depends On:
Blocks: 113496
TreeView+ depends on / blocked
 
Reported: 2004-02-02 18:43 UTC by Matthew Booth
Modified: 2007-04-18 17:02 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-03-17 22:49:51 UTC
Embargoed:


Attachments (Terms of Use)
Patch described in bug report (829 bytes, patch)
2004-02-02 18:44 UTC, Matthew Booth
no flags Details | Diff

Description Matthew Booth 2004-02-02 18:43:03 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030922

Description of problem:
A problem with our importer caused Links to be imported without the
associated link item (in APLAWS, the Related Links authoring step).
Specifically it was an internal link, but both target_uri and
target_item_id were null.

Obviously this is a problem with the importer which we'll fix, however
its possible using only published APIs to create a Link in this state.
Such a link causes the Related Links authoring step to give a stack
trace, which isn't helpful.

I'll attach my patch to a comment. It simply outputs a log message at
ERROR level indicating the invalid Link object instead of throwing a
stack trace.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. blah
2.
3.
    

Additional info:

Comment 1 Matthew Booth 2004-02-02 18:44:36 UTC
Created attachment 97410 [details]
Patch described in bug report

Comment 2 Richard Li 2004-02-05 20:42:28 UTC
@40120


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