Shadow Priest Problem!
 

Every time i get this Error and the Player and Target Frames are gone and Blizz Target one only Show on my Shadow Priest.
Cant Play my Priest now due to this :(



Dont have this happen on Hunter - Feral Druid or my Rouge.

This is the Error i get:

Getting the same error on my Disc priest, other characters are working fine post patch.

On my rogue I will show either 1 CP or none regardless of how many I actually have. Fresh install with latest version and no other addons.

Same thing on my priest

Did I miss a fix for this because my priest is starting to feel neglected

Here are my errors

14x ...ce\nibRealUI\Libs\oUF\elements\classicons.lua:75: attempt to index local 'color' (a nil value)
...ce\nibRealUI\Libs\oUF\elements\classicons.lua:75: in function <...ce\nibRealUI\Libs\oUF\elements\classicons.lua:62>
...ce\nibRealUI\Libs\oUF\elements\classicons.lua:263: in function 'enable'
nibRealUI\Libs\oUF\ouf.lua:99: in function 'EnableElement'
nibRealUI\Libs\oUF\ouf.lua:269: in function <nibRealUI\Libs\oUF\ouf.lua:192>
(tail call): ?
nibRealUI\Libs\oUF\ouf.lua:555: in function 'Spawn'
...ace\nibRealUI\HuD\UnitFrames\Units\Player-Player.lua:292: in function '?'
nibRealUI\HuD\UnitFrames\Shared.lua:733: in function 'InitializeLayout'
...rface\nibRealUI\HuD\UnitFrames\UnitFrames.lua:268: in function <...rface\nibRealUI\HuD\UnitFrames\UnitFrames.lua:260>
(tail call): ?
[C]:: ?
[string "safecall Dispatcher[1]"]:9: in function <[string "safecall Dispatcher[1]"]:5>
(tail call): ?
...AskMrRobot\Libs\AceAddon-3.0\AceAddon-3.0-12.lua:558: in function 'EnableAddon'
...AskMrRobot\Libs\AceAddon-3.0\AceAddon-3.0-12.lua:571: in function 'EnableAddon'
...AskMrRobot\Libs\AceAddon-3.0\AceAddon-3.0-12.lua:651: in function <...AskMrRobot\Libs\AceAddon-3.0\AceAddon-3.0.lua:636>
[C]:: ?
[C]:: in function 'LoadAddOn'
FrameXML\UIParent.lua:343: in function 'UIParentLoadAddOn'
FrameXML\UIParent.lua:422: in function 'TimeManager_LoadUI'
FrameXML\UIParent.lua:923: in function <FrameXML\UIParent.lua:825

Thanks in advance

This was fixed in r16a, make sure you are using that version.

My bad I missed that update.
Apologies and many thanks for a speedy reply