Red Hat Bugzilla – Bug 114774
Badly formed Internal Link causes stack trace
Last modified: 2007-04-18 13:02:26 EDT
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
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Created attachment 97410 [details]
Patch described in bug report