--- Comment #1 from Brad Jorsch <> ---
What appears to be happening here is that an API error is being raised
somewhere after the point where the custom feed printer is initialized, and the
custom feed printer chokes when asked to print that API error.

I don't see any obvious candidates for the cause of the original error, but
that doesn't matter much since this situation should be handled anyway. For
testing, this bug can be reproduced by locally editing ApiFeedRecentChanges to
throw an exception from its execute() method.

You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
Wikibugs-l mailing list

Reply via email to