Yeah, that's why I asked you to do the tests without AnkhUp enabled; we already know it's leaking a global "db" upvalue. It only causes an error when more than one addon is doing the same thing; in your case, Wardrobe's global "db" was overwriting AnkhUp's, so when AnkhUp tried to look up a setting, it was looking at Wardrobe's settings and not finding what it wanted.

I've been busy and haven't had time to finish the other stuff I'm working on in AnkhUp... I do have days off coming up this week though, so it won't be too much longer.

Well, it's not any of these: Atlas*, AtlasLoot*, BankItems, BigWigs*, GatherMate*, GemHelper, HandyNotes*, Omen, RatingBuster, or Recount. I have all of those, and no leaked global "db". (Asterisks mean "this addon and all of its plugins/modules.")

It's also not something that doesn't use Ace3, which rules out AlphaMap, BeanCounter, CT_*, Chronos, CurseProfiler, DBM-*, Earth, eCastingBar, Enchantrix*, FeatureFrame, Fire, FireTree, FluidFrames, GroupCalendar, Gymnast, Khaos, MobInfo2, Monkey*, QuestHelper, Satellite, Sea, and Stubby. (BTW, BeanCounter, Enchantrix*, and Stubby are parts of the Auctioneer suite, which you don't appear to have anymore, so you should just be able to delete them.)

As for the rest, rather than enable them all one by one, you can do a "binary search" to speed things up -- log in with half (say, everything that starts with A-G) enabled. If there's no global "db", log out, disable those, enable the other half. Once you've found the half with the problem, disable half of those, and continue until you're down to a single addon. I'd recommend going somewhere quiet (i.e. not Dalaran) to do this; it shouldn't take more than 5 minutes.

Well, it's some Ace3 addon... if you really want to find out which one (and report the problem to its author so they can fix it too) you'd have to disable all of your addons, and enable them one at a time, and run the script after each one. As soon as you don't get "Doesn't exist!" then the last addon you enabled is also leaking its "db" upvalue as a global variable.

If you know which addons you have that use Ace3, you can narrow it down by skipping over those that don't. If you're not sure, and have a lot of addons, post a list and I'll help you figure out which ones it might be (I can also tell you definitively which ones it's not if they're ones I use).

Well, db being a global is a problem, but it shouldn't cause the problem you're having unless some other addon is also doing the same thing. Can you log in without AnkhUp enabled and type:

This should provide some clue as to which other addon is also leaking its db as a global, and I'll upload a fix for AnkhUp later tonight. I've got a few other things I'm tweaking that I'm not quite satisfied with yet.

1) Open Core.lua in a text editor and change line 34 from:
to:
2) Log into WoW with only AnkhUp enabled.

3) Do whatever it is that previously triggered those errors.

4) Take a screenshot (or more than one) of all the debug messages printed, and post it here. Note where the errors occurred.

Both of those errors indicate that your settings somehow disappeared between the time the addon loaded and the time those function were called. Try deleting the saved variables file for AnkhUp:

World of Warcraft\WTF\Account\<YOUR ACCOUNT NAME>\<Server Name>\<Character Name>\SavedVariables\AnkhUp.lua

This must be done while you are not logged in.

Fixed.