#LUA Error: chat frame blocked

34 messages · Page 1 of 1 (latest)

naive crown
#

Hello,

I have a problem with Weak Auras. I've disabled ALL add-ons to test whether the problem is indeed with WeakAuras. My problem is with the chat. Every time I'm in combat and someone whispers to me and I try to reply, I get an error. It only happens when I'm in combat, and it doesn't matter if it's a WoW or Battlenet whisper. I've deleted the game and the entire interface to do a clean install, but the problem persists.

I've searched a bit on Discord for this issue, but haven't found anything similar. I've attached the Pastebin with the error recorded by Bugsack. https://pastebin.com/NtJ2ftVL

Help, please PepeHands

#

I forgot to say that I have the latest version of WeakAuras and I don't have any WeakAuras installed.

summer bolt
#

The add-on by default does not interact with the chat in any way.

#

Zero.

#

And that includes ChatFrame1:HideBase() from the error. This never gets called.

naive crown
summer bolt
#

It's in the logs folder of the game.

naive crown
wooden jackal
zinc ivy
#

it doesn't show where weakauras taint SELECTED_DOCK_FRAME

naive crown
zinc ivy
#

Yes it should have much more informations

#

Maybe do the command with 3 instead of 2, then reload

naive crown
naive crown
zinc ivy
#

then /reload and retry

naive crown
zinc ivy
#

so not loading taintless didnt help

#

this is on retail, not ptr?

naive crown
#

Yes, retail

zinc ivy
#

ok.. i don't have a solution sorry, looks like a bug on blizzard code

naive crown
zinc ivy
#

i have no idea

#

mhm

#

try close game, rename WTF folder into WTF_old

#

see if that help

naive crown
#

Hmm nope, problem persists ):

naive crown
#

I've deleted all WoW and Blizzard logs from my system, including the information in REGEDIT. I reinstalled everything, and the problem persists. I'm going to contact Blizzard support to see if they can help me.

zinc ivy
naive crown
#

Anyway, a friend gave me a temporary solution and it was changing the chat whisper settings from "new tab" to "both". For now, this has worked to solve the problem, at least temporarily.