Sign in with
Sign up | Sign in
Your question

A *bug* with the automated PMs and a question

Tags:
  • Tom's Hardware
  • Settings
Last response: in Site Feedback
Share
November 24, 2013 5:42:16 PM

Hi guys!..:) 

Just checked my forum PMs and noticed a broken links in the automated message, for: 'You got a new badge!'

The last line reads:
Quote:
'Set this badge as status: http://www.tomshardware.co.uk/community/badge-status?ba...;redirect=1#xtor=EPR-8808'

.. but the URL link only goes as far as illustrated above; actually it's exactly like it, in the PM received from author 'tomshardware' ^^


&& my question is, in the 'Account settings', the 'Communication' Messenger type doesn't currently include Jabber:
Would it be possible to add it, please? =)

P.S.
This is completely non-relevant, but I found it -somewhat- interesting (hehe); an old, old PM, from 2009, links to:
  1. http://www.tomshardware.co.uk/community/profil

.. which is in Serbian, the word 'profil'; pretty cool! xD

More about : bug automated pms question

November 24, 2013 6:00:50 PM

Bug #2

Just unsuccessfully tried, to set badge as status, from 'My account', by clicking on the mouseover 'Set as status' when hovering over a badge. Using Firefox 25.0.1 on Xubuntu Linux, 13.10 Saucy:

  1. ~$ lsb_release -a
  2. No LSB modules are available.
  3. Distributor ID: Ubuntu
  4. Description: Ubuntu 13.10
  5. Release: 13.10
  6. Codename: saucy

(Typed it as *bug* because these are, really, only just annoyances and nothing else :) )

Edit: Managed to change the status, using Opera, thanks!
m
0
l
November 25, 2013 6:58:10 AM

Thanks for the detailed bug reports on these issues. The second one we knew about, and a fix is underway. The first looks newer - so I'll forward it along to the QA folks to make sure it gets looked at. Thanks again!
m
0
l
November 25, 2013 7:49:05 AM

Hey there nimd4,

We'd like to know more about your bug #2. We weren't able to reproduce your bug though we know you are not the only one to encounter it. Would you be able to produce us a screenshot of the ajax call in Firebug or Chrome Dev tools so that we learn more about the error ?

Thanks :) 

Gzav
m
0
l
!