Yeah, this all happened during the 2.0 patch timeframe when they broke the hell out of everything including Decursive and eePanels, two of the most used raid mods around. What you'll notice in some of those is that they can one-button buff/decurse but only after the combat has ended. They don't figure it's a big deal out of combat as that's just tedium time anyway. Here's the skinny (direct link to the WoW 2.0 UI change list ) with the relevant portion highlighted:
The protected code mechanism introduced in 1.10 has been extended to cover more functions. Blizzard code is considered secure, all other code is untrusted. The following function types are restricted for AddOns:
* Movement is never allowed.
* Spell casting and targetting (including focus) are only allowed using secure templates or special slash commands (not /script).
* Programatic modification of macros, key bindings, and the action bar page only allowed outside of combat.
* Trading, placing auction bids, querying LFG, crafting, and reloading the UI are only allowed interactively.
* Action buttons and targeting frames are now "protected". Protected frames cannot be programmatically moved, shown or hidden, or have their attributes (unit, action, etc) changed during combat.