Authors CurseForge

I see your point, and I'm going to consider a solution for it soon, but in the meantime you can either downgrade to an older version (that still works fine in 3.0), install a LDB display, or install Broker2FuBar.

Pre patch i had all my Ace libs disembedded (used jwowupdater to keep mods current)

Bugsack worked fine on the PTR using this method.

But since the load on demand "feature" isn't getting fixed until next patch, I rebuilt my addons from scratch using embedded lib versions of the Ace mods.

The problem it seems for me with Bugsack is the embedded library versions on the project page are missings some of the libs/functions it uses.

When I log in with only the follow addons enabled these 3 messages appear in /buggrabber

- !Buggrabber & Bugsack Loaded

1. AceComm-3.0\AceComm-3.0.lua:15: Cannot find a library instance of "CallbackHandler-1.0".
BugSack-3.0\Libs\AceLibrary\AceLibrary.lua:49: in function `GetLibrary'
AceComm-3.0\AceComm-3.0.lua:15: in main chunk

2. LibDataBroker-1.1\LibDataBroker-1.1.lua:3: LibDataBroker-1.1 requires CallbackHandler-1.0
LibDataBroker-1.1\LibDataBroker-1.1.lua:3: in main chunk

3. BugSack-3.0\BugSack.lua:37: Cannot find a library instance of "CallbackHandler-1.0".
BugSack-3.0\Libs\AceLibrary\AceLibrary.lua:49: in function `LibStub'
BugSack-3.0\BugSack.lua:37: in main chunk

This is using the BugSack-3.0-beta2 version from the project page.. I tried a few other versions with the embedded libs but get the same errors

I tried to add the missing Ace libs into the \libs folder and added the includes into the embeds file, but didn't seem to get very far!

Check your !BugGrabber folder to see that it has LibStub and CallbackHandler-1.0.

Quote from Rabbit

Check your !BugGrabber folder to see that it has LibStub and CallbackHandler-1.0.

The installed version of !BugGrabber didn't have any embedded libs..

So installed the following versions : 3.0-beta2, r131, 3.0-beta & r129 (which all have the libs)

I get a ui error popup on all 4 versions saying:

Interface\Addons\!BugGrabber\BugGrabber.lua:120 attempt to call global 'LibStub' (a nil value)

Quote from gramg

The point of LDB and broker displays is you the user get to decide what you want as a display.

Fubar plugin came with the overhead of displays built in even if you didn't have Fubar installed. Take a look at the size of fubar plugin vs LibDataBroker.

I understand it's a pain to actually have to go get another addon and many people probably didn't read the changelogs when updating, but it can be just as simple and small as downloading a minimap button display, or as full fledged as the new Titan.

I hear a rumor that Fubar might eventually support LDB plugins natively which would be a good thing imo, but in the meantime we have Broker2Fubar which basically just adds Fubar Plugin to all LDB data objects.

Support for LDB in FuBar doesn't solve the problem though. It would be nice to have a lightweight library to give minimap button support I think. I know that I don't want to release my addon without the Fubar plugin unless I have a way to include a standalone mode because I don't want to force ppl to install any data broker if they don't want to.

Of course, I'm guessing that I'm one of the few who think that way and will probably end-up having to implement my own standalone support sooner or later but I'm grumpy about it :-).

CC does have a changelog function, it just doesnt show up upon updating nor is it sorted so atm it looks like a complete jumbled mess.

Quote from justcallmefred

Before , I used this with Fubar....I take it that isn't gonna happen anymore either.

Why do you say that?

Go back to an older version of BugSack+BugGrabber and come back in a week or two.

I am getting this error consistently on a full copy of BugSack (downloaded from wowace, the 3.0-beta2 version with libraries included and embedded.

-----------------
[2008/10/16 13:51:30-7679-x1]: BugSack-2.x.x.152\BugSack.lua:374: attempt to call field 'RegisterCallback' (a nil value)
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[1]":9: in function <[string "safecall Dispatcher[1]"]:5>
(tail call): ?:
AceAddon-3.0\AceAddon-3.0.lua:365: in function `EnableAddon'
AceAddon-3.0\AceAddon-3.0.lua:435: in function <Interface\AddOns\Ace3\AceAddon-3.0\AceAddon-3.0.lua:421>
<in C code>: in function `LoadAddOn'
Interface\FrameXML\UIParent.lua:991: in function `UIParentLoadAddOn':
Interface\FrameXML\UIParent.lua:241: in function `CombatLog_LoadUI':
Interface\FrameXML\UIParent.lua:389: in function `UIParent_OnEvent':
<string>:"*:OnEvent":1: in function <[string "*:OnEvent"]:1>

---

Quote from Meebo

CC does have a changelog function, it just doesnt show up upon updating nor is it sorted so atm it looks like a complete jumbled mess.

This. When the minimap button for BugSack mysteriously vanished, some of us did try reading the changelog (right-click on addon, select changelog). What appeared in the popup window was not much more useful than line noise. Sometimes it seems sorted by date, sometimes by revision number -- not as useful as it might sound due to all the commits from the old repository being mixed in with the ones from the current repo -- and sometimes they're either unsorted or sorted by some criterion which is not immediately apparent.

If there's a way on the user's end to sort the changelog displayed by Curse Client, I would appreciate any tips. Or if CC can be told to show only the commit/changelog messages between the currently installed version and the version that's about to be installed, that'd be even better. (Arguably for that we should just fire up an SVN client, or browse the SVN repo, but most CC users are probably not that familiar with dev tools.)

/threadjack over, sorry