catch user page exceptions and provide more information to the user

Bug #339738 reported by Greg Grossmeier
Affects Status Importance Assigned to Milestone

Bug Description

We need to handle this case better:

A user clicks on a @username which does not exist on the service which they are subscribed to. Doing so gives a blank tab for that @username. We should instead say "This user does not exist on $SERVICE."

Being smart and trying to guess where the user actually is beyond the scope of this bug.

Catching an exception in get_user_messages() (in all that are effected) is probably the place to add this functionality. get_data() in microblog/ throws a URLError exception which we can work with.

Changed in gwibber:
importance: Undecided → Medium
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.