Bug with secure action buttons noted and to be fixed in 2.1.2

A WoW Forum member named Shirly noted that a certain code (viewable using our “read” link below) which is designed to bind the MultiBarBottomLeft buttons such that they change their actions whenever the main action bar’s page is changed worked fine with Blizzard‘s World of Warcraft. But that was until the 2.1 update.

Shirly said that after the 2.1 update, the code only worked out of combat. While in combat, the actions in the MultiBarBottomLeft buttons don’t change. Shirly speculated that a bug could have caused this apparent malfunction.

Within the same day of the post, Blizzard Community Manager Slouken said that the errors with the code will be looked into.

Other Forum members like Iriel, confirmed that based on their testing, this was definitely a WoW bug. “There appears to be a problem with objects being created during AddOn load being tainted, regardless of where they’re loaded.”

Around 12 hours later (wow, that’s sort of fast), Slouken said that this bug with the secure action buttons has been fixed. He says: “This is fixed for 2.1.2, thanks!”

All we have to do now is wait for 2.1.2.

A WoW Forum member named Shirly noted that a certain code (viewable using our “read” link below) which is designed to bind the MultiBarBottomLeft buttons such that they change their actions whenever the main action bar’s page is changed worked fine with Blizzard‘s World of Warcraft. But that was until the 2.1 update.

Shirly said that after the 2.1 update, the code only worked out of combat. While in combat, the actions in the MultiBarBottomLeft buttons don’t change. Shirly speculated that a bug could have caused this apparent malfunction.

Within the same day of the post, Blizzard Community Manager Slouken said that the errors with the code will be looked into.

Other Forum members like Iriel, confirmed that based on their testing, this was definitely a WoW bug. “There appears to be a problem with objects being created during AddOn load being tainted, regardless of where they’re loaded.”

Around 12 hours later (wow, that’s sort of fast), Slouken said that this bug with the secure action buttons has been fixed. He says: “This is fixed for 2.1.2, thanks!”

All we have to do now is wait for 2.1.2.