Authors CurseForge

r203 throws 2 errors onload is as follows:

[2008/10/10 04:26:58-523-x1]: Buffalo\Buffalo.lua:946: attempt to compare number with nil
AceAddon-2.0-82169 (Ace2):983: in function <Interface\AddOns\Ace2\AceAddon-2.0\AceAddon-2.0.lua:976>
<in C code>: ?
AceEvent-2.0-82169 (Ace2):260: in function `TriggerEvent'
AceEvent-2.0-82169 (Ace2):910: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:903>

---

[2008/10/10 04:27:04-523-x9]: Buffalo\Buffalo.lua:946: attempt to compare number with nil
Buffalo\Buffalo.lua:769: in function `BuffaloButton_Update'
<string>:"*:OnEvent":1: in function <[string "*:OnEvent"]:1>

---

That's strange, that's a bug I fixed. If you could do me a favor...

Please look at Buffalo.lua and post the contents of lines 800 to 820. This is the first time I've used SVN, so I'm wondering if something went wrong with the update. These lines are where I put in the fix, and I'd like to know if it's there in the version you downloaded.

Also, did you run this on the beta or on the PTR?

I also updated the version number in the TOC file, so we're on rev 204.

Everything seems to have went fine with the commit, there was just an initialization missing :-).

Gabriel, could you try again with revision 208? (Or later).

Quote from Nimbal

Everything seems to have went fine with the commit, there was just an initialization missing .

Gabriel, could you try again with revision 208? (Or later).

Ahh, thanks. Sorry I missed that one, thought I'd gotten all of them.

Not sure why I never saw the bug though, I've been playing with it on the beta for a few weeks now.

Because I'm a bit neurotic, I messed with the indenting on your fix, so we're on rev 209.

I checked out the latest code (r209) and this is much more stable than the latest on curse. I'd give it a push out because what's already there is not at all usable.

Thanks for the great work.

Forgive me for being clueless, but where can I get r209?

OMG OMG OMG I figured out how to use the WoWAce files >.>

Although the "install via CC" for the alphas don't work.

Quote from brambler

I checked out the latest code (r209) and this is much more stable than the latest on curse. I'd give it a push out because what's already there is not at all usable.

Thanks for the great work.

I take that as a "Buffalo works on 3.0.2 live". Repository tagged.

This addon, wich I like a lot anyway, on 3.0.2 live servers crash addon engine with fatal error preventing any changes (sounds "fatality" in buggrabber) in addons leaving only already runnig procedures and functions in memory on any kind of timed buffs popping (buffs with unlimited duration like auras and mounts works ok). Same time, same pack of addons (I use buttonfacade on top of the buffalo to skin the buttons) on beta 3.0.2 wotlk servers works fine. Can you research the problem since I miss buffalo in my UI a lot?

I need some more information to fix this. You mentioned Buggrabber. If you also have Bugsack, there should be a red bag icon somewhere on your screen. Click it and copy the text. Post it here. If there are several errors, click through them with the buttons of bugsack and post all of them here.

If you don't have Bugsack, you'll have to use slash commands:

1. Enter "/buggrabber". This should elicit a response like "Usage: /buggrabber <1-3>". In this case it would mean that Buggrabber has grabbed 3 errors.
2. Enter "/buggrabber 1" to see the first error. Copy the text and post it here. Repeat with "/buggrabber 2", "/buggrabber 3" and so on until you have all errors.

Yeah, I have BugSack, and I know how to use it, used to debug everything for some weeks on beta, but after release of 3.0.2 new version of BugSack seems to be little fuzzy for me - there are no button with bag (don't ask me why and where I didn't searched, was a little busy with all that release vanity). The main problem I encounter with this - that after "fatality" sound and fatal error in engine everything that was not in memory stops, and that means that buggrabber didn't catch or didn't show what it caught. =(
I will try harder to catch and show what happens this evening, I promise.

PS. Oh yeah, just read the BugSack thread and discovered that wotlk version need Broker2Fubar addon to show up his face.

This may or may not be a bug but...why isnt the debuffs colored anymore? (borders)
Everything works fine except that the borders of the debuffs aint red or w/e depending on debuff - or is it intended?

So this is the trace:
[2008/10/17 22:00:59-100-x1]: Buffalo\Buffalo.lua:791: attempt to index local 'color' (a nil value)
<string>:"*:OnEvent":1: in function <[string "*:OnEvent"]:1>

PS. Yikes, logged on by other account...

Yep, I've digged some and researched that debuffType is set not to nil on buffs, but to "".
If change 789 line to
if ( debuffType and not debuffType == "" ) then
everything works smooth.

Quote from Oversun

PS. Yikes, logged on by other account...

Does this mean Oversun = EShiva? And good work on the fix, I've uploaded it to the svn and will tag it when I get confirmation that this is the same bug as EShiva reported.

Yeah, yeah, EShiva = Oversun from work.

Quote from Mucklan

This may or may not be a bug but...why isnt the debuffs colored anymore? (borders)
Everything works fine except that the borders of the debuffs aint red or w/e depending on debuff - or is it intended?

Can you try out the latest version (v1.01) and see if it has been fixed? Thank you.

Quote from Nimbal

Can you try out the latest version (v1.01) and see if it has been fixed? Thank you.

Doesnt look like it's working.

I get this error message:
Date: 2008-10-17 22:03:06
ID: 1
Error occured in: Global
Count: 1
Message: ..\AddOns\beql\questlog.lua line 476:
attempt to call method 'GetFont' (a nil value)
Debug:
...ce\AddOns\Buffalo\Libs\AceAddon-2.0\AceAddon-2.0.lua:25:
...ce\AddOns\Buffalo\Libs\AceAddon-2.0\AceAddon-2.0.lua:23
...ce\AddOns\Buffalo\Libs\AceAddon-2.0\AceAddon-2.0.lua:1055: ManualEnable()
...ce\AddOns\Buffalo\Libs\AceAddon-2.0\AceAddon-2.0.lua:983:
...ce\AddOns\Buffalo\Libs\AceAddon-2.0\AceAddon-2.0.lua:976
[C]: ?
...ce\AddOns\Buffalo\Libs\AceEvent-2.0\AceEvent-2.0.lua:260: TriggerEvent()
...ce\AddOns\Buffalo\Libs\AceEvent-2.0\AceEvent-2.0.lua:910:
...ce\AddOns\Buffalo\Libs\AceEvent-2.0\AceEvent-2.0.lua:903

This is not a Buffalo error, but an error of an addon named "beql". Buffalo only pops up here because Ace2 is loaded first from Buffalo's embedded version. beql uses Ace2 and triggers an error in it.

Quote from Nimbal

This is not a Buffalo error, but an error of an addon named "beql". Buffalo only pops up here because Ace2 is loaded first from Buffalo's embedded version. beql uses Ace2 and triggers an error in it.

Oh...right ;D

Well...still no colored borders around debuffs - I assume it's not the beql error that is cuasing it..?

Despite the fact that i disable the beql addon, the error is still being shown. (trying to cut down on the errors to reduce lag) - Any idea why?