• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

HTTP Error in Fetch, more...

K

Koro76

Well-known member
I just transferred control of a PC to a member, and they're having some problems when they view the inherited PC:

- HTTP Error in Fetch when HLO tries to retrieve the PC portrait
- Tried to split a stack of poison (black smear poison), and now it doesn't appear on the play screen, but still appears in the gear list
- AbbreviationSpace appeared in the PC's movement entry on the play page, but this issue resolved itself after re-assigning control to the campaign member

The member in question has an Apprentice account, if that helps.
 
Report this as a bug within HLO, or send an email to support. The devs may not see forum posts, and they don't get added to their bug tracker.
 
The issue with the image is definitely on our radar. It's a somewhat complex issue that we overlooked, so it's probably not gonna get fixed for a little bit. But we're definitely aware.

The other two issues are new ones to me. So please submit those as bug reports to ensure they get properly logged into our system and addressed.
 
I submit quite a few bugs, but for new features, it might easier for others to filter their requests by reading that their issue is already on the radar. I work on a software team, and prioritizing and combining frequently reported tickets in our tool is something I hear coworkers complaining about often.
 
Koro76 said:
I submit quite a few bugs, but for new features, it might easier for others to filter their requests by reading that their issue is already on the radar. I work on a software team, and prioritizing and combining frequently reported tickets in our tool is something I hear coworkers complaining about often.
Click to expand...

LWD have said in the past that everybody who sees a bug should report it, so that they can gauge how widespread it is. I would hope that internally they merge/link duplicate bug reports.

Bug reporting in forums won't get their attention.
 
Farling said:
LWD have said in the past that everybody who sees a bug should report it, so that they can gauge how widespread it is. I would hope that internally they merge/link duplicate bug reports.

Bug reporting in forums won't get their attention.
Click to expand...

I think that perhaps I've been misunderstood. I report many bugs in the tool. I had reported THESE bugs before I posted this thread.

I was more speaking to their bandwidth. LWD has said before that their team isn't as big as it used to be, which means their bandwidth is smaller, and time spent sorting duplicate tickets isn't time spent on development.

Also, are you saying that the response from Rob means that I didn't get anyone's attention?
 
Last edited:
The issue is that all too often, users are reporting bugs when we're at our busiest. There are some times when we have the chance to look over the forums and turn the issues we find into cards, like this, but there's too many times when we don't, and we're worried about issues getting lost at those times. So it's best to get into the habit of reporting them through our bug tracker, because then they're seen first by CS, who can start collecting the necessary details even if the rest of the team is concentrating on finishing a project and even if we're busy, it's filed away for later.
 
You must log in or register to reply here.
Back
Top