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. I have discovered that the reputation system turned itself off. It has now been turned back on.
    1 point
  22. I've encountered this as well, only happens in mobile with any page of the xat.wiki. Thanks for the report Blacky. @Andre
    1 point
  23. This is a confirmed bug. It happens also with the number "0". Thank you for report. @Admin
    1 point
  24. This is not a connection issue. You are asked to relogin on xat.com/login to update your account values according to Mike's comment since an exploit was recently found and fixed.
    1 point
  25. The reason this has occured is because there recently was an exploit that has now been fixed. The relogin is needed to update everyone's values with the new values that are generated that fixed the exploit. So just go to xat.com/login and you should be fine, otherwise do what is said above and clear cache / cookies.
    1 point
  26. Are you aware that PCBACK was boosted recently to show your pcback if the user doesn't have one ? Source : xat.wiki/pcback Thread closed since there is no bug.
    1 point
  27. What seems to be the cause of this login issue, I experienced this the other day after I updated my flash.
    1 point
  28. This will fix two problems (not being able to do (RANDOM) and the problem listed above) Fix: @Admin File: xAvatar.as Function: xAvatar(constructor) Replace with if ((((((_arg_2.charAt(0) === "(")) && ((_arg_2.toLowerCase().indexOf("random") >= 0)))) && (todo.HasPower(_arg_5, 272)))){ var randavy = _arg_2.split("#"); for (var i:Number = 0; i < randavy.length; i++) { randavy[i] = xmessage.DoRandom(randavy[i], _arg_5); } _arg_2 = randavy.join("#"); }; File: xmessage.as Function: DoRandom
    1 point
  29. You would do so after getting into the pc and then clicking at the user again - then you get to the user dialog. But i don't disagree, it's quite inconvenient.
    1 point
  30. This issue has been fixed. Thank you ^^
    1 point
  31. Thanks for the report. We're already aware of this issue.
    1 point
  32. Changed Status to Status: Fixed This issue has been fixed with the latest chat version (debug chats for now).
    1 point
  33. 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
  34. Fix: File: xkiss.as Function: WhoIs replace it with this private static function WhoIs(_arg_1:*=0){ if (todo.w_userno != todo.uKiss) { main.openDialog(2, todo.uKiss); } }
    1 point
  35. This doesn't only happen with smiley and it is indeed a bug Fix: FIle: main.as Function: ProcessMessage //towards the bottom of the function
    1 point
  36. Issue is caused by NaughtyStep & Dunce being treated as both a kick and ban function which they are not Fix: File: DialogActions.as Function: Constructor (aka DialogActions) Replace: with if (bKick != undefined || this.bDunce != undefined || this.bNaughty != undefined){ s = xconst.ST(79); Dia.kick = new xBut(Dia, (xx + 10), yy, 150, xatlib.NY(30), s, this.ViewprofileonKick, ((bKick || this.bDunce || this.bNaughty) ? 0 : (xBut.b_Grayed + xBut.b_NoPress))); Dia.kick.SetRoll(xconst.ST(80)); D
    1 point
  37. there you go baby cakes 10/10 perfect fix (pretty sure it works as far as i tested but that was a while ago) did it a month ago
    1 point
  38. this is correct its so users can register quick and easy. They can set a nick to anything they want right away. They can chose a reg name later.
    1 point
  39. For the second problem, this is something we can fix on the wiki. To be honest, we had much trouble with the Arabic translations. Send me a PM and we can try finding fixes for this.
    1 point
  40. Pretty sure it's been like this since forever. It goes for anything you send, if it's the same exact message. I think this was added to stop a user trying to spam multiple people with the same message, link, etc.
    1 point
  41. The only way to make working export and import again would be to redo the photo_upload3.php file. (Maybe you can add it to your main post)
    1 point
  42. I can see how you'd think that's a bug, but it's actually working as intended. The levels were changed slightly.
    1 point
  43. Changed Priority to Priority: Trivial Yes, can confirm this issue. Mute shouldn't be shown when being mod. Thanks for reporting.
    1 point
  44. Yeah, at least it's working when I'm not logged LOL I also saw a lot of users reporting the problem.
    1 point
  45. I've looked into it but i can not confirm/reproduce this issue (tried with opera, chrome and edge). Is flash allowed for the ticket page for the users who have it?
    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.