I've been getting this error since the patch, and narrowing my addons down to just bugsack and fubar didn't make it go away, so I was wondering if anyone could shed some light on what's causing it and if it can be fixed :S
Doesn't seem to be affecting anything though, except Cartographer no longer works.
[2007/05/22 17:41:15-739-x3929]: Interface\FrameXML\ChatFrame.lua:1256: bad argument #2 to 'strsplit' (string expected, got nil):
Interface\FrameXML\ChatFrame.lua:1256: in function <Interface\FrameXML\ChatFrame.lua:1229>:
Interface\FrameXML\ChatFrame.lua:1272: in function <Interface\FrameXML\ChatFrame.lua:1269>:
(tail call): ?:
Interface\FrameXML\ChatFrame.lua:1287: in function <Interface\FrameXML\ChatFrame.lua:1283>:
Interface\FrameXML\ChatFrame.lua:1299: in function `UpdateMacroFeedback':
<string>:"*:OnUpdate":10: in function <[string "*:OnUpdate"]:1>
---
Seems to me like Blizzard got bit by their own feature.
This error must be something that the Blizzard UI provokes, and the reason they have released with it is probably because they didn't see it, since Lua errors are disabled by default in 2.1.
However, with BugSack installed, the settings is overruled, and errors are shown.
There are multiple bugs in the FrameXML code on Blizzards side, BugSack was trying to give me thousands of actionBar errors that it was constantly in a shutdown mode counting down to restart. As long as the errors don't stop the game from functioning they will probably fix it on next patch day.
The error is a problem in the code that handles castsequences. You can delete the file, but if you want to remake your macros (which, unlike addons, are officially supported by blizzard..), you'll get the errors again.
'Your product's not working? Try not using it, that'll get rid of your problems!'
Blizzard seems blind to these type of errors, probably because they have report LUA errors off. They had same problems when 2.0 came out and they originally went to secure UI elements. probably take a patch or 2 for them to go away.
Doesn't seem to be affecting anything though, except Cartographer no longer works.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThis error must be something that the Blizzard UI provokes, and the reason they have released with it is probably because they didn't see it, since Lua errors are disabled by default in 2.1.
However, with BugSack installed, the settings is overruled, and errors are shown.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse Premium'Your product's not working? Try not using it, that'll get rid of your problems!'
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse Premium