Player auras require the new SecureAuraHeader to be used. #38

Open
haste opened this Issue Sep 5, 2010 · 7 comments

Projects

None yet

5 participants

@haste
oUF-wow member

No description provided.

@LiquidAtoR

As it stands current, you get this error when trying to cancel the unitbuff by rightclick.
Date: 2010-10-22 19:22:06
ID: 2
Error occured in: AddOn: oUF
Count: 1
Message: Error: AddOn oUF attempted to call a forbidden function (CancelUnitBuff()) from a tainted execution path.
Debug:

oUF\elements\aura.lua:25:
oUF\elements\aura.lua:24

@mvader123

From the description, it looks like you are only going to use the secure header for player auras. If you were going to make all auras use the secure header, I'd like to request that you provide a secure path for player auras, and a non-secure path for target, party, etc auras. The secure path would allow for right-click canceling (but fewer sorting options), and the non-secure path would allow for more advanced sorting where you need it: on target, party, and raid auras.

TLDR: Please only use the secure header for player auras and not for target, party, raid auras.

@haste
oUF-wow member

If I provide a secure path, it will only be for the player auras, nothing more. No reason to limit the rest of the system.

@ghost

Would be great if this would be optional on both Buffs and Auras, some use them just for buff tracking.

@haste
oUF-wow member

It will be its own element. As mentioned before there's no need to limit the rest of the system.

It currently isn't feasible to implement the secure aura header system into oUF however.

@p3lim p3lim referenced this issue Jun 15, 2012
Closed

auras click off #129

@nixpulvis

Ah, this is what I need. Sad to see it over 2 years old.

@haste
oUF-wow member
@p3lim p3lim added the element label Sep 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment