Auctionator

Auctionator

136M Downloads

Action Forbidden

lightyear66 opened this issue · 8 comments

commented

Please include as much of the following information as possible to help me fix the bug:

Are you on the retail or the classic version of WoW?

Retail - Dragonflight

Is this a bug or a feature request?

Bug:

Brief Description of Bug

Sometimes when I right click an object such as an enchant to apply it to one of my equipment the blizz UI pops up a warning that the auctionator addon has tried to perform an action not allowed - I'm given the option to disable the addon or cancel the action of right-clicking the enchantment.

Please include a brief description of the bug, including what you were doing, and when it occurred.

Happens about 25% of the time when trying to right click objects in inventory for use or application.
Disabling Auctionator fixes problem 100% of time.

Steps to Reproduce

Include the steps I would need to follow to reproduce the bug.
right click on an enchant before attempting to apply it to an item

Loaded Addons

Include a list of addons you were running at the time this bug occurred.
Auctionator
BugGrabber
BugSack
Details! Damage Meter
Gathermate2
Handynotes
Leatrix Plus
MapCoords
Plater
Postal
Premade Group Finder
Raider.IO
Rarescanner
Talent Tree Tweaks
Unlimited Map Distance
WeakAuras
Speedy Autoloot
Deadly Boss Mods

Back Trace (LUA Error Output)

Bugcatcher:
6x [ADDON_ACTION_FORBIDDEN] AddOn 'Auctionator' tried to call the protected function 'UNKNOWN()'.
[string "@!BugGrabber/BugGrabber.lua"]:480: in function <!BugGrabber/BugGrabber.lua:480>
[string "=[C]"]: ?
[string "=[C]"]: in function UseContainerItem' [string "@FrameXML/ContainerFrame.lua"]:1409: in function <FrameXML/ContainerFrame.lua:1318> [string "=[C]"]: in function ContainerFrameItemButton_OnClick'
[string "@FrameXML/ContainerFrame.lua"]:1461: in function <FrameXML/ContainerFrame.lua:1448>

You can get this through the use of !BugGrabber and BugSack addons.

Feature Request:

Is your feature request related to a problem? Please describe

Describe the problem you are experiencing.

Describe the solution you'd like

A clear and concise description of what you want to happen.

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

Additional context

Add any other context or screenshots about the feature request here.

commented

Same issue here, it can happen on any "on use" item in my bags. UI reload usually fixes it for a bit, but can happen again and again.

commented

I've hit this issue too, but haven't been able to identify the trigger yet. The cause is something else and the unable to use a bag item is the symptom.

Do you remember if you used

  1. The auction house in the session before the error? If you did use the auction house, did you buy something? Cancel something? Post something?
  2. Used the professions view (seeing crafting and profits values)?
  3. Used work orders (seeing the reagents cost)?
  4. Opened the guild bank (viewing tooltips)?

Anything else (basically anything you may have seen information or UI components from Auctionator on)?

Hopefully with enough different answers to the above questions I should be able to narrow down what the trigger is.

commented

I've pushed a fix for the blocked error triggering after a purchase in some scenarios. This may help with the blocked errors. Please report back if you get a blocked error after installing 10.0.29

commented

It sometimes even happens during combat blocking the usage of any spells and abilities.

commented
commented

Thanks for the summary. I'll try the different scenarios out and see if I can get a trigger from one of them.

I have read about other addons having protected errors trigger after some kind of loading screen.

commented

There are a variety of taint bugs in the 10.x interface, and by the nature of taint, they often spread and implicate innocent addons. This repo attempts to track them: https://github.com/Stanzilla/WoWUIBugs/issues

commented

I'm going to assume this issue is resolved - no further errors have been reported 🥳