Static Popups not working properly

Guides UI and Macro
1

I have a problem I’m pretty sure is linked to an addon. The only problem is, I can’t find the addon.

The issue is with static popups. For example, I’m sending Cache of War Resources to an alt. When you put it in the mail you get the warning that doing this will make the item non-refundable. To which you have to Ok or Cancel. What I get is the screen darkening (which happens when the popup appears) but no dialog box is able to be seen. I have to do a /reload and try again.

That is just one example, there are many different circumstances where this issue crops up that I can’t get into them all. I run 2 addons for bugs, bugcatcher and bugsack. Bugsack lets me see the error text, and this is what appears from Bugsack:

28x FrameXML\StaticPopup.lua:5175: Action[SetPoint] failed because[SetPoint would result in anchor family connection]: attempted from: StaticPopup1:SetPoint.
[C]: in function SetPoint' FrameXML\StaticPopup.lua:5175: in functionStaticPopup_SetUpAnchor’
FrameXML\StaticPopup.lua:5165: in function <FrameXML\StaticPopup.lua:5163>
[C]: in function StaticPopup_SetUpPosition' FrameXML\StaticPopup.lua:4798: in function <FrameXML\StaticPopup.lua:4391> [C]: in functionStaticPopup_Show’
FrameXML\UIParent.lua:1218: in function <FrameXML\UIParent.lua:1108>

Locals:
InCombatSkipped

I’m pretty sure that there is a specific addon causing the issue. Generally the bugsack report info usually helps you find the offending addon. As you can see in the above case there is no mention of an addon.
I run quite a few addons. Disabling addons entirely is not an option, but I did try it temporarily. The problem didn’t occur that I recall, but then again, there are times when this bug doesn’t happen at all… or times when it constantly happens. There seems to be no rhyme or reason when it decides it wants to be an issue, but it’s annoying when it decides to be!

I would have made this post in the addons forum, but with the new layout I couldn’t find it. Or more to the point, if it takes more than 5 minutes to find, it may as well not exist.

I don’t know if anyone else has (or has had) this problem… but if I could at least get an idea of where to start looking to discover the offending addon, that would be awesome.

Thanks.

2

Best option is a FULL UI reset https://us.battle.net/support/en/article/7549 then reinstall all addons fresh and test them one by one till either problem desists or u find the bad addon.

3

I do understand that is an option. That solution isn’t exactly as easy as it sounds though. Getting all those settings back takes forever, especially across multiple characters and realms. In 12 years of WoW, I have done it exactly twice. I’ve regretted doing it each time.

It’s why I was hoping someone would have an idea of the type of addon that would interfere with that procedure call. Since it happens outside of the mailbox as well, I assume addons like Postal wouldn’t be the culprit. If I’m not in combat or casting, again assumption would be it’s not likely to be Quartz. Auctionator should be clear as well since there should be no calls to that while I’m trying to logout (yes, it has happened while trying to log out in a non rest location)

So that solution is an absolute last resort. I mean, I’d rather set fire to my PC. (almost).

4

Here’s a thought.

Disable half your add-ons
Wail on some training dummies for 5 min (this should result in triggering all your add-ons to some degree)
Then go try to reproduce the error.

If it doesn’t happen, disable another half and repeat the above

5

A quick test might be to do a search on your Interface folder for the string
"StaticPopup
You might also run it again using single rather than double quote. This should tell you which addon(s) might save anchoring information on StaticPopup frames.

You could also try the same searches on your WTF folder which might tell you the addons(s) that are saving StaticPopup settings.

6

Thanks guys, I will give both of those a shot. I’ve only played a couple times since I posted this message and thankfully the error hasn’t made a problem again (yet). Then again, I haven’t been doing much that would trigger a static popup… so… /shrug. lol.