5x Deferred XML Node object named oUF_ClickCastUnitTemplate already exists
Hi all,
I basically have two of my addons embed oUF as a library. (let's call them AddonA and AddonB) And just now, it started to popping the following error as soon as I log in to my toon. Lua Code:
The interesting fact is that those two addons currently do nothing but loading oUF as an embedded library. I honestly don't know why this is happening as those two addons have been co-existing since the Legion :confused: Obviously disabling either of them would stop crying for such error. Would this be a bug with Blizzard's end? |
It's not a bug. Having multiple XML objects w/ identical names has become an error in BfA.
Ideally, embeddable libraries shouldn't create/define anything in XML because it's impossible to update such objects. But due to oUF's nature, we have to use XML templates because there's no way to do what we need in Lua. The only solution to your problem is to disabled embedded oUF in both addons, and to use standalone version of oUF for them. |
Quote:
Would there be any possible ways to load one's embedded oUF only when there is no oUF loaded yet, instead of making it standalone? (Maybe like version checking done on LibStub) Guessing there's none as you stated tho :( |
LibStub won't help.
As I said, your best bet is to use oUF as a standalone addon, then both addons will use it. Alternatively, you can disable error reporting entirely :D |
Quote:
right?! It's sad that I can't use custom tag ##X-oUF thing :( |
Blame Blizzard for not letting us create templates with Lua or allow us to set certain attributes outside XML.
Quote:
|
I created an addon that loads all my shared libraries. So that way I don't have any duplicates that I want to embed, including oUF. This works out really nice. Then I don't have to clutter up my addon list with a bunch of addons that are frameworks or libraries. :)
|
Quote:
Quote:
Quote:
It might be inefficient, but I want all those libraries gathered in a single pack, not placed individually within an addon folder. |
Me too. That's how I did mine. It makes it easier to manage too.
I put all my shared stuff in a single addon and organized in folders by type (assets, libs, sounds, fonts, etc) and then make all my other addons dependent on it. I'm a little anal retentive lmao. Here is how I have mine laid out. https://1drv.ms/u/s!AoICZc1JonHCgd4s-MtjieXYdnv1ZQ |
This thread appears as top result for the error on google.
Could any of you elaborate on how to fix it as a normal person? I don't even know which add on produces this... |
Any addon that loads the same library that uses XML-declared frames that any other addon has already loaded can generate this error. In this specific thread (and forum), oUF had the error.
It’s an error that’s not an error. There’s nothing wrong, just Blizzard doing weird things. It only ever shows up when the UI loads, so I’d just ignore it. |
All times are GMT -6. The time now is 04:58 PM. |
vBulletin © 2024, Jelsoft Enterprises Ltd
© 2004 - 2022 MMOUI