General oUF/oUF_ALZA help

[jusion]

I converted over to ALZA's newest released UI a couple days ago, but I started getting a large amount of LUA errors while in combat in a raid. The errors came from oUF_ALZA\raid.lua (lines 16 and 18 ):

--[[ Aggro coloring ]]
 local function ColorAggro(self, event, unit)
    if(not unit) then return end
    local s = UnitThreatSituation(self.unit)
    if(s and s>0) then
        local r, g, b = .8, 0, 0
        if(s==1) then
            r, g, b = 0.5, 0.5, 0
        elseif(s==2) then
            r, g, b = 0.5, 0, 0
        end
        self.bd:SetBackdropBorderColor(r, g, b)
    else
        self.bd:SetBackdropBorderColor(0, 0, 0)
    end
end

Those lines are from the aggro coloring section. Being the LUA novice I am, I just commented out the whole section, as I don't particularly care for having aggro coloring on my raid frames anyways.
However, after that (or maybe simultaneously, I just didn't notice) I am now getting spammed with errors originating from oUF\ouf.lua

local oUF = {}

The exact error is:

oUF-1.3.16\ouf.lua:39: attempt to call field '?' (a nil value)

Locals:

  ---

The oUF version is 1.3.16; I am unable to update oUF without braking oUF_ALZA. Any ideas?
EDIT: The problem is definitely with the oUF_ALZA\raid.lua. Disabling that file in the ALZA TOC stops the oUF errors.

[Dawn]

You don't need to comment out the function. Well it's better if you do it, too. But a function is "disabled" if you remove the way it's updated. Depending on how he's updating it there should be something like

RegisterEvent, blah, ColorAggro

or

UpdateThreatblah = ColorAggro

[jusion]

Originally Posted by Dawn You don't need to comment out the function. Well it's better if you do it, too. But a function is "disabled" if you remove the way it's updated. Depending on how he's updating it there should be something like RegisterEvent, blah, ColorAggro or UpdateThreatblah = ColorAggro

That worked. Thanks a bunch!