Anniversary PvE: 'SpellCoda' tried to call the protected function 'Search()'.
Bogdanov89 opened this issue ยท 3 comments
Thank you for this awesome addon!
I got the following error on WoW Anniversary PVE:
1x [ADDON_ACTION_BLOCKED] AddOn 'SpellCoda' tried to call the protected function 'Search()'.
[string "@!BugGrabber/BugGrabber.lua"]:485: in function <!BugGrabber/BugGrabber.lua:485>
[string "=[C]"]: in function `Search'
[string "@Blizzard_GroupFinder_VanillaStyle/Blizzard_LFGVanilla_Browse.lua"]:250: in function `LFGBrowse_DoSearch'
[string "@Blizzard_GroupFinder_VanillaStyle/Blizzard_LFGVanilla_Browse.lua"]:189: in function `SearchActiveEntry'
[string "@Blizzard_GroupFinder_VanillaStyle/Blizzard_LFGVanilla_ParentFrame.lua"]:95: in function `LFGParentFrame_SearchActiveEntry'
[string "@Blizzard_GroupFinder_VanillaStyle/Blizzard_LFGVanilla_Listing.lua"]:77: in function <...pFinder_VanillaStyle/Blizzard_LFGVanilla_Listing.lua:54>
Locals:
_ = Frame {
}
event = "ADDON_ACTION_BLOCKED"
events =
{}
I also got the following LFGBrowse error:
1x [ADDON_ACTION_BLOCKED] AddOn 'SpellCoda' tried to call the protected function 'Search()'.
[string "@!BugGrabber/BugGrabber.lua"]:485: in function <!BugGrabber/BugGrabber.lua:485>
[string "=[C]"]: in function Search' [string "@Blizzard_GroupFinder_VanillaStyle/Blizzard_LFGVanilla_Browse.lua"]:250: in function LFGBrowse_DoSearch'
[string "@Blizzard_GroupFinder_VanillaStyle/Blizzard_LFGVanilla_Browse.lua"]:189: in function SearchActiveEntry' [string "@Blizzard_GroupFinder_VanillaStyle/Blizzard_LFGVanilla_ParentFrame.lua"]:95: in function LFGParentFrame_SearchActiveEntry'
[string "@Blizzard_GroupFinder_VanillaStyle/Blizzard_LFGVanilla_Listing.lua"]:77: in function <...pFinder_VanillaStyle/Blizzard_LFGVanilla_Listing.lua:54>
Locals:
_ = Frame {
}
event = "ADDON_ACTION_BLOCKED"
events =
}
The addon is certainly not calling 'Search()' so this is some kind of tainting issue. I've had this once myself but I wasn't able to reproduce it again which makes it difficult to pinpoint the problem. Please let met know if and how you are able to reproduce the issue reliably after each /reload. If you are able to reproduce it, test if it happens without the addon loaded.