Wholly

61 - Is Forbidden error when clicking on quest

What steps will reproduce the problem?
1.Click, CTRL/Click or any type of click on quest in Wholly quest log.
2.
3.

What is the expected output? What do you see instead?
When clicking should set TomTom waypoint, when CTRL/Clicking should ignore quest.

What version of the product are you using?
037

Do you have an error log of what happened?
Yes..

BugGrabberDB = {
    ["session"] = 1080,
    ["lastSanitation"] = 3,
    ["errors"] = {
        {
            ["message"] = "FrameXML\\SecureTemplates.lua:542 attempt to call method \"IsForbidden\" (a nil value)",
            ["time"] = "2013/09/15 19:17:33",
            ["locals"] = "self = com_mithrandir_whollyFrameScrollFrameButton1 {\n 0 = <userdata>\n normalText = com_mithrandir_whollyFrameScrollFrameButton1NormalText {}\n statusCode = \"P\"\n secureProcessed = true\n questId = 31579\n tag = com_mithrandir_whollyFrameScrollFrameButton1Tag {}\n}\nbutton = \"LeftButton\"\ndown = false\nunit = nil\nactionType = \"click\"\natRisk = false\nhandler = <func> @FrameXML\\SecureTemplates.lua:539\nSECURE_ACTIONS = <table> {\n action = <func> @FrameXML\\SecureTemplates.lua:334\n worldmarker = <func> @FrameXML\\SecureTemplates.lua:564\n item = <func> @FrameXML\\SecureTemplates.lua:418\n focus = <func> @FrameXML\\SecureTemplates.lua:503\n target = <func> @FrameXML\\SecureTemplates.lua:488\n attribute = <func> @FrameXML\\SecureTemplates.lua:548\n click = <func> @FrameXML\\SecureTemplates.lua:539\n cancelaura = <func> @FrameXML\\SecureTemplates.lua:463\n spell = <func> @FrameXML\\SecureTemplates.lua:379\n macro = <func> @FrameXML\\SecureTemplates.lua:441\n pet = <func> @FrameXML\\SecureTemplates.lua:354\n mainassist = <func> @FrameXML\\SecureTemplates.lua:533\n maintank = <func> @FrameXML\\SecureTemplates.lua:527\n assist = <func> @FrameXML\\SecureTemplates.lua:508\n togglemenu = <func> @FrameXML\\SecureTemplates.lua:291\n actionbar = <func> @FrameXML\\SecureTemplates.lua:315\n stop = <func> @FrameXML\\SecureTemplates.lua:481\n flyout = <func> @FrameXML\\SecureTemplates.lua:363\n glyph = <func> @FrameXML\\SecureTemplates.lua:405\n multispell = <func> @FrameXML\\SecureTemplates.lua:370\n}\nforceinsecure = <func> =[C]:-1\n",
            ["stack"] = "FrameXML\\SecureTemplates.lua:542 in function \"handler\"\nFrameXML\\SecureTemplates.lua:633 in function <FrameXML\\SecureTemplates.lua:581",
            ["session"] = 1080,
            ["counter"] = 4,
        }, -- [1]
    },
}

Please provide any additional information below.

User When Change
Nimhfree Sep 18, 2013 at 20:29 UTC
Meloric Sep 17, 2013 at 03:00 UTC
Nimhfree Sep 16, 2013 at 13:14 UTC
Meloric Sep 16, 2013 at 00:38 UTC Create

You must login to post a comment. Don't have an account? Register to get one!

  • 4 comments
  • Avatar of Nimhfree Nimhfree Sep 18, 2013 at 20:29 UTC - 0 likes

    I have put up a prerelease version of Wholly on the official prerelease page at http://ns1.mithrandir.com/WorldOfWarcraft/WhollyGrailPrerelease.shtml if you are interested in testing it.

  • Avatar of Nimhfree Nimhfree Sep 17, 2013 at 15:01 UTC - 0 likes

    It seems Blizzard has changed their SECURE_ACTIONS.click code for 5.4 such that it now checks IsForbidden() which Wholly does not implement. In the next version of Wholly I am adding the following:

    IsForbidden = function(self) return false end,

    which seems to make things once again work. I will try to create a prerelease version and make that available on the prerelease site as soon as possible.

  • Avatar of Meloric Meloric Sep 17, 2013 at 03:00 UTC - 0 likes

    No I was not in combat. Opened the Wholly quest log as I was flying over an area and noticed a quest I had no interest in and tried to ignore it and got that error. After landing, I again tried to ignore a quest and received the same error. Log completely out of game to desktop, restarted game and still getting the same error with any type of cllick in the Wholly quest log.

    I tried deleting version 037, including all SavedVariables in the account and character WTF files and installed version 036 of wholly and version .53 of Grail. I think those are the versions I was using prior to 037. Wholly would not load saying it needed version 54 or higher of Grail.

    I'll try doing some other troubleshooting with different versions when I get time and download earlier versions. I don't know exactly when this began occurring as I have not tried to interact with Wholly's quest log in some time.

  • Avatar of Nimhfree Nimhfree Sep 16, 2013 at 13:14 UTC - 0 likes

    Were you in combat at the time this happened? Does this normally work for you properly when not in combat?

  • 4 comments

Facts

Last updated
Sep 18, 2013
Reported
Sep 16, 2013
Status
Fixed - Developer made requested changes. QA should verify.
Type
Defect - A shortcoming, fault, or imperfection
Priority
Medium - Normal priority.
Votes
0

Reported by

Possible assignees