Deferred XML object already exists.
Theranyx opened this issue ยท 8 comments
Bugsack has been catching the following exceptions:
12x Deferred XML Node object named Ellyb_LogsFrame already exists
12x Deferred XML Node object named Ellyb_StaticPopTemplate already exists
24x Deferred XML Node object named Ellyb_CursorFrameTemplate already exists
24x Deferred XML Node object named Ellyb_ChatInputTextures already exists
24x Deferred XML Node object named Ellyb_PopupButton already exists
24x Deferred XML Node object named Ellyb_PopupButton_Okay already exists
(Please do not close this issue, so people coming here to check the known issues can find this.)
It's a harmless warning, the issue causing it will be fixed in time but you can safely ignore it, nothing will break.
Ah great! Was trying to pick at it to see if there was a conflicting addon, but seems to still occur with all other addons disabled. Good to know its something that is already known about.
Every time I log in, Bug sack reminds me of the bug your addon. This is too bad, I really liked this addon.
Issue is still harmless, the addon will still work fine regardless, it will still be fixed in time anyway.
I know you call it a "harmless" warning. Yes the addon still works. But, nonetheless, blizzard is letting you know that you should probably do something about it. Maybe I should ask the author of Bug Sack to add a feature to not remind me of known "harmless" errors..lol
And I'd like to remind you that this work is mainly the effort of one man (Ellypse) on his free time while he has a job and a life. This warning happens once per reload and doesn't affect how the addon works in any way, shape, or form. I hope you'll understand that it has not been deemed so critical as to require full-time investment after weeks of work to ensure all addons work well with 8.0 changes.
You are free to provide a pull request on Ellyb if you would like to contribute in a meaningful way to solve this issue.