Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 03/05/2016 in Bug Comments

  1. i reported a fix for this ages ago Fix (just incase they forgot):
    4 points
  2. I found the quickfix for Chrome users: 1. Go here - chrome://flags/#autoplay 2. select how it is selected in this printscreen: http://prntscr.com/jhqe68 or more simply "No user gesture required."
    3 points
  3. Fix was submitted earlier today and is applied whenever @Admins get to it. Done.
    3 points
  4. will fix at next release
    3 points
  5. Issue is caused because after going away or invis you dont get sent the scroller message again so on <i it resets scroller to empty or Live Mode stuff Fix: File: network.as Function: myOnXML (towards the end of the if statement "if (e.nodeName == "i")"
    3 points
  6. This is related to the Dunce power. Dunce allows a moderator to dunce another moderator, hence the "Kick" menu is available. Regarding the "Ban" menu, Dunce was originally placed on that menu and it seems like the administrators have forgotten to make this option unavailable when they moved it onto "Kick". Dunce power enabled Dunce power disabled
    3 points
  7. IPS confirmed there was an issue and escalated it to higher departments.
    2 points
  8. The forum is now running on the latest release. If you're still experiencing this issue then link to the exact content and I'll address it.
    2 points
  9. This is not an issue actually. The timestamp for pawns has expired and since HTML5 doesn't use this system, it works like a charm I emailed admins with explanations about this and should be fixed soon.
    2 points
  10. 2 points
  11. @Blacky The issue has been fixed now. Thank you for reporting.
    2 points
  12. We will need more evidence or details before we’re able to proceed! Thinks such as event logs could be useful, perhaps. Are you sure the tempmodded users weren’t kicked/dunced/yellowcarded etc ?
    2 points
  13. Users have been complaining about this in help chats. I wouldn't classify its priority as "normal" since users find it very inconvenient that they can't browse chats in a specific language.
    2 points
  14. A self note: you still can access the chat through the /go command. The bug has been transmitted to the administrators. I will post when it is fixed. Thank you for reporting.
    2 points
  15. Thank you for reporting. This bug seems to appear also on HTML5. I will post when this bug is fixed.
    2 points
  16. Changed Status to Status: Fixed
    2 points
  17. Changed Status to Status: Fixed Managed to reproduce on 1920x1080 screen resolution.
    2 points
  18. If i remember correctly, this isn't a bug. It was made like that due the lack of activity that xat Ayuda has.
    2 points
  19. Fix: File: xmessage.as Function: Smilie Replace: with if (Code.match(/#wc/g).length > 0 && !todo.HasPowerA(todo.Users[uid].Powers, 410)) { Code = Code.replace(/#wc/g, "#WC"); smc.u = ("C" + xatlib.xInt(smc.u)); }
    2 points
  20. Issue is caused by pools not being reset with <w packet (it doesnt get sent with chats that dont have pools) Before fix:After fix: Fix: (found problem with old fix added new one which is 100% now) File: network.as Function: myOnXML this goes at the end of the if statement "if (e.nodeName == "gp"")"
    2 points
  21. IPS admits that there's probably an issue, but they can't fix what they can't reproduce, so they expect step-by-step instructions. Every time I've tried - a notification was conveniently sent.. We're probably missing some parameters that those specific topic creators managed to meet. Asking them to explain in detail how they created their topic might be the way of successfully reproducing this and solving the issue once and for all.
    1 point
  22. Yeah, it requires refreshing to display updated data. It's supposed to work like that. If you don't want to refresh the whole tab, right-click the banner and select "Reload Frame".
    1 point
  23. This is a real problem for everyone who uses the phone.
    1 point
  24. The Hat power currently have some issues with the flash version of xat, many hats from powers aren't working, however you can still use the hat#t, hat#x .
    1 point
  25. It will be fixed in a future update of the HTML5 chat.
    1 point
  26. This has been fixed now. The fix is as follows: Using an old register link will redirect you to the new register page, containing the user id / k1 / k2 info in the link already (full redirect). So should just be able to register on the new web. Thank you for letting us know.
    1 point
  27. 1 point
  28. This should now be fixed (pending one more upload to fix default en to default international).
    1 point
  29. Yeah, other users are experiencing this too. LaFleur has told it's due a websocket and they are trying to fix it.
    1 point
  30. Ah this bug on Firefox! I see. But we are already aware about this bug already! Thank you for reporting.
    1 point
  31. Hello, We are fully aware with the issue on Edge and the homepage. I'll mail the administrators to take a look at that. Other issues are already reported on our bugs board. We do not have official dates for when it will be fixed. Thank you.
    1 point
  32. Hello, We have already this bug listed on the board. (Was previously reported by Leandro to me.) Thank you for reporting.
    1 point
  33. 1 point
  34. Changed Status to Fixed
    1 point
  35. It does not support underline because it is the separator
    1 point
  36. 1 point
  37. Changed Status to Status: Fixed Fixed in a future IPS update.
    1 point
  38. 1 point
  39. Admin has been notified. I'll notify you once i know more, it was probably a mistake. @ANGY It's fixed in next release. Thanks for reporting.
    1 point
  40. I don't quite get this. Can you please elaborate so I can understand?
    1 point
  41. Thanks for the report @Stif. We're already aware of this issue and this will be fixed at some point. It is considered low priority for now.
    1 point
  42. This has been fixed now. @Laming thanks for the info.
    1 point
  43. This issue has been fixed for the future release.
    1 point
  44. This is a confirmed bug. It happens also with the number "0". Thank you for report. @Admin
    1 point
  45. I checked and yeah, it doesn't redirect to ayuda. That's more because it hasn't been updated or even added. Confirmed bug
    1 point
  • Newsletter

    Want to keep up to date with all our latest news and information?
    Sign Up
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.