[Addon] Jamba - An assistant for Multiboxers - Release for WoW 6+

[Tehtsuo]

Getting this when you get a quest that turns in automatically (as-you-go quests in dungeons for example)

Message: CreateFrame(): Couldn't find inherited node "WatchFrameAutoQuestPopUpTemplate"Time: 10/19/14 17:28:21
Count: 28
Stack: (tail call): ?
[C]: ?
[C]: in function `CreateFrame'
...face\AddOns\Jamba-QuestWatcher\JambaQuestWatcher.lua:1733: in function `AutoQuestGetOrCreateFrame'
...face\AddOns\Jamba-QuestWatcher\JambaQuestWatcher.lua:1765: in function `DisplayAutoQuestPopUps'
...face\AddOns\Jamba-QuestWatcher\JambaQuestWatcher.lua:1661: in function `QuestWatcherQuestListScrollRefresh'
...face\AddOns\Jamba-QuestWatcher\JambaQuestWatcher.lua:1153: in function `UpdateQuestWatchList'
...face\AddOns\Jamba-QuestWatcher\JambaQuestWatcher.lua:1136: in function `DoQuestWatchObjectiveUpdate'
...face\AddOns\Jamba-QuestWatcher\JambaQuestWatcher.lua:1862: in function `JambaOnCommandReceived'
Interface\AddOns\Jamba\JambaCore.lua:348: in function `OnCommandReceived'
Interface\AddOns\Jamba\JambaCommunications.lua:425 : in function `?'
...1.0\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:147: in function <...1.0\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:147>
[string "safecall Dispatcher[4]"]:4: in function <[string "safecall Dispatcher[4]"]:4>
[C]: ?
[string "safecall Dispatcher[4]"]:13: in function `?'
...1.0\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:92: in function `Fire'
...erface\AddOns\Jamba\Libs\AceComm-3.0\AceComm-3.0.lua:261: in function <...erface\AddOns\Jamba\Libs\AceComm-3.0\AceComm-3.0.lua:243>


Locals: <none>

Also spams "Automatically Accepted Quest" and doesn't let you continue the quest chain.

[Jafula]

Getting this when you get a quest that turns in automatically (as-you-go quests in dungeons for example)



Also spams "Automatically Accepted Quest" and doesn't let you continue the quest chain.

This one is not an easy fix. I found the new template to use, but when clicking on the popup that Jamba makes it tries to run the script from the underlying system which causes another Lua error. In the release I have just made 6.0.2.3, I have disabled the popups from showing until I come up with a better solution. I imagine I'll just use some text rather than a popup...