WeakAuras

WeakAuras

Addons
200M Downloads

1x [ADDON_ACTION_BLOCKED] AddOn 'WeakAuras' tried to call the protected function 'Search()'.

PAKOTxx opened this issue ยท 2 comments

commented

Description

1x [ADDON_ACTION_BLOCKED] AddOn 'WeakAuras' tried to call the protected function 'Search()'.
[string "@!BugGrabber/BugGrabber.lua"]:480: in function <!BugGrabber/BugGrabber.lua:480>
[string "=[C]"]: in function Search' [string "@FrameXML/LFGList.lua"]:2101: in function LFGListSearchPanel_DoSearch'
[string "*LFGList.xml:1167_OnClick"]:2: in function <[string "*LFGList.xml:1167_OnClick"]:1>
[string "=[C]"]: in function `Click'
[string "return function() ------------------------------------------------------- Hide Buttons --------------------------------------------------"]:43: in function <[string "return function() -------------------------..."]:43>

Blizzard blocked the ability to access LFG completely? Or It can be fixed somehow?

WeakAuras Version

5.4.2

World of Warcraft Flavor

Retail (Default)

Tested with only WeakAuras

  • Yes
  • No

Lua Error

1x [ADDON_ACTION_BLOCKED] AddOn 'WeakAuras' tried to call the protected function 'Search()'.
[string "@!BugGrabber/BugGrabber.lua"]:480: in function <!BugGrabber/BugGrabber.lua:480>
[string "=[C]"]: in function `Search'
[string "@FrameXML/LFGList.lua"]:2101: in function `LFGListSearchPanel_DoSearch'
[string "*LFGList.xml:1167_OnClick"]:2: in function <[string "*LFGList.xml:1167_OnClick"]:1>
[string "=[C]"]: in function `Click'
[string "return function() ------------------------------------------------------- Hide Buttons --------------------------------------------------"]:43: in function <[string "return function() -------------------------..."]:43>

Reproduction Steps

LFG weakuras, somethis like https://wago.io/NDlWRwsLr

Last Good Version

No response

Screenshots

No response

Export String

No response

commented

Yes you cannot automate the searching of lfg listings.

commented

This error pops from random addons.
I renamed the addon directory for testing and logged in without any addon. This error was still popping at random when queueing for dungeons.
I believe it's self introduced taint by Blizzard. It seems they forgot to mark some of their code as secure and it spreads taint into their own code.