Ce site requiert JavaScript pour fonctionner.
Veuillez activer JavaScript dans votre navigateur.
Live
RPT
12.0.5
RPT
12.0.1
Bêta
Addon? error
Répondre
Retourner à l'index
Publication par
Coletrane
Hi guys...
I keep getting this error:
Message: ...terface\AddOns\Blizzard_GlyphUI\Blizzard_GlyphUI.lua:174: attempt to index global 'PlayerTalentFrame' (a nil value)
Time: 10/01/12 18:55:13
Count: 26
Stack: : ?
...terface\AddOns\Blizzard_GlyphUI\Blizzard_GlyphUI.lua:174: in function `GlyphFrame_Update'
...terface\AddOns\Blizzard_GlyphUI\Blizzard_GlyphUI.lua:91: in function <...terface\AddOns\Blizzard_GlyphUI\Blizzard_GlyphUI.lua:80>
Locals:
But can't find any addon that causes the problem. Any suggestions?
Publication par
Neffi
First off, make sure all your addons are up to date. Check both Curse and WoWInterface; some are posted at both, but only stay up to date on one. You may think you have the latest version but don't.
Inspecting the code, I see that both GlyphUI and TalentUI are load-on-demand. Apparently something is causing the GlyphUI to load (and attempt to update) before the TalentUI, which shouldn't logically happen. This could very well be an oversight in the default UI. In that case, there's no way to fix it, just disable error reporting.
I'm not getting this error and I've seen no reports of it, so test to see if it's not just you. Disable all your addons and attempt to recreate the error. If you get the error on the default UI, report it on the bug report or tech support section of the official forums.
Also, you may try resetting your settings and reproducing it once again (without addons still). You can do this by navigating to your WoW installation folder (while WoW is exited) and renaming "WTF" to something else (like "WTF.old"). Start WoW and try to reproduce the error; if it doesn't happen, you may want to just redo all your settings. (If that doesn't help, exit WoW fully, delete the new WTF folder and rename the old one back to restore all your settings.)
If disabling all addons prevented it, do a binary search for which addon is causing it to happen. Disable half your addons, test; disable the other half, test. One you find which half has the offending addons, repeat the process for that half, and so on in halves until you come down to the single addon causing it.
Publication par
Ketho
Slightly related, but at least the Wowhead Looter is, or was one of the causes
http://www.wowhead.com/forums&topic=205988/wowhead-lua-error#p3265282
Publication par
620095
This post was from a user who has deleted their account.
Publication par
Coletrane
Thx for the good advice guys :)
I've disabled wowhead looter, and the error seems to be gonne.
Répondre
Vous n'êtes pas connecté. Veuillez vous
connecter
pour répondre à ce sujet, ou
vous inscrire
si vous n'avez pas déjà un compte.