I cannot find a good reason for this problem to be occurring. That said, if you still have the item and are willing to continue testing, you can try this file:
https://dl.dropboxusercontent.com/u/22711625/Geppetto.lua
Otherwise, I'll continue my own tests as soon as I can get to a testing realm.
Thank you for your testing and...

I fixed the error with battle pets, and a few more subtle things.
However, after switching my client's locale to German, I could not replicate your problem. I'm uploading a new version, with all of my smaller fixes. If you're still having trouble with it, could you respond with the following information?
Which Toy is it getting s...

Sorry but its still not working for me in german, it now showing up the icon and when I klick on it it just says "loading" forever :(
You may also add an option to ignore and item so you can sell in in auction house later without the addon poppung up all the time.
Hmm. Does it actually learn the Toy, or does it text just update...

For the love of
Alright, try 0.1d going up right now - it completely disables that chunk of code rather than cherry-picking the previous issue.
Doesn't work for me other than to spam the "What the ****" error line contained in your code.

This addon doesn't gather any information from your other characters - it is character specific. I suspect that whatever item it shows you've completed was previously looted from another mob, as several of the achievement's criteria pre-date the introduction of the Timeless Isle.
If you're sure it's a bug, could I get a screenshot...

Simply undoing it won't be trivial, but I'll add some detection for Outfitter and upload a new version this evening.
Edit: Check out 2.4c!
I read in the change log that you moved the button due to a conflict with oQueue, hover now it's conflicting with Outfitter, is there a way you can float it to the left or at least let me know...

Woops, alright, try version 1.0e. If you're still running into issues with that, see if you can narrow down exactly what causes it.
oh sorry, forgot to mention that the error happened during pet battles, with the new version I randomly get this one:

Not sure what scenario this was popping up in, but I took a look and tightened up some of the safety checks involved. Try out the newest version and see what you get.
8x ABiggerBag\ABiggerBag.lua:270: bad argument #1 to 'strsub' (string expected, got nil)

This is the correct fix for the current bug. Unlike commenting out line 106, this preserves all functionality. Replace line 105 with the following:
if (type(obj) == "table" and type(rawget(obj, 0)) == "userdata" and type(obj.GetName) == "function") and (type(obj.IsForbidden) == "function" and not obj:IsForbidden()) then

I can't seem to replicate the issue. Can you answer a few questions?
a) Are you on version 1.0b? Earlier versions would occasionally see this error.
b) When does this happen? Every time you mouseover a character? Sometimes? Cross-realm only? When it dies? Something else?
c) Does this still occur if you turn off TipTac?
If you...

Y'know, I actually have the skeleton for that in the code, just never got to hooking it up. Look for it shortly. =)
Thank you for making this great, much-needed addon! I still have an idea for improvement, though: it would be even better if Festival also remembered what you have in your own bank, not just in your bags.

If it's coming up blank, it likely ran into an issue while attempting to load and the error was suppressed by some part of your addon setup. The most common issue is the one noted below involving Alliance characters - if you're not Horde, try the new download coming up!
If you are Horde, lemme know and we'll see if we can hunt thi...

Thanks for the report! I've had one other person come up with this error, but wasn't able to replicate it. I suspect the problem is stemming from the fact that I don't actually have any Alliance high-enough level to have currencies beyond just gold, so something slipped through the cracks.
Fixing this is my top priority - check ba...

I'm not likely to add "pick 'n' choose" configuration for this addon. You have the option of toggling it with /ook whenever you need to speak in plain english.
If it really bothers you, the "wikket" translation is handled separately from the swear filtering, and you're welcome to comment it out in your local copy, around line 327....

It still works fine, just check Load Out-of-Date AddOns at the addon selection screen. =)
But yes, I do intend to bump the TOC number so WoW thinks it's up-to-date, plus add some tweaks. I've been doing my research into hozen linguistics and turned up some new vocabulary, plus I'll do a bit of cleanup to make the translations more...

For some reason this doesn't work for me.
Mod is installed and enabled.
/ook doesn't toggle it on.
Doesn't work at all? It defaults to on, and there's no notification when you type /ook (which I should probably change). The filters on incoming messages should always work, at the very least, though the outgoing filter might c...

HotKey Fix v1.1 Available Now. Fixes graphical error, adds Dominos support.
You're basically correct, yaahoo, though I added checks to avoid looping through those buttons if BT/Dominos aren't loaded. I also fixed an issue where HotKey texts would get "left behind" if you moved a BindPad action out of a slot.
I think you need to...

Thank you! Nice patch for a first aid.
But there are many issues where each one is somewhat minor but difficult to solve.
Happy to contribute, Tageshi. One of my guildmates greatly missed the feature, so I just took the simplest route to making it work with the Blizzard UI, and then added Bartender support for good measure. It's...

I've written a patch to re-enable HotKey text for the Blizzard UI and Bartender4.
http://www.wowinterface.com/downloads/info21493.html
It is not exhaustively tested and may contain bugs, but appears to be functional in my limited testing. It might also work with other action bar addons, if they are sufficiently similar to the Bli...

Does the user really care about the distinction between cameraDistanceMax and cameraDistanceMaxFactor? Would they ever have reason to change one independently of the other?
If you can't answer yes to either, you might merge them into a single slider from 1-200 and hide the finer details in the name of usability.