• 0

    posted a message on JWowUpdater - A new java addons updater for ace2
    How can I remove a monitored, non WoWAce addon?

    Using jWowUpdater 1.87, and I have two non-ace addons that I've added:
    Clique / WOWINT / ID=5108
    Bongos2 / CURSE / ID=2003

    While going through the upgrade process for WoW 2.4, I deleted everything in my WTF and Addons folders. However, when I fired up JWU, while it showed the Ace addon list as empty (as it should), these two still showed up in my monitored list of Non WowAce addons.

    I can't figure out how to remove them. There's no option to individually delete them that I can find, even deleting my Addons folder seems to have no effect. They don't show up in the "delete and addon" list, either.

    Posted in: Updaters
  • 0

    posted a message on Fubar not showing up, plugins show an map
    Orionshock - good eye...

    Running with WoW is likely what borked my settings. I did, in fact, run WAU yesterday while I had WoW open (but minimized -DOH!). In fact, at the time, WoW gave me nice little kaboom when I exited - it popped up the "submit a bug report to bliz" dialog, which I hadn't ever had the pleasure of viewing :)

    decker12 - trying cleaning out the addon folder again, but use these settings:
    X Automatic Dependency Download
    Default mode WITH externals
    X Unpack Addons
    X Skip SVN working copies
    Skip Version Check
    Diagnostic Logging

    -J
    Posted in: FuBar AddOns
  • 0

    posted a message on Fubar not showing up, plugins show an map
    .. because, frankly, I didn't know what it should be set to.
    :)

    As of yesterday, all of the settings were whatever the "out-of-the-box" defaults were.
    After I ran WAU today, and started getting missing dependency errors, I thought that perhaps someone the WAU settings had gotten corrupted, so I went in and selected anything that looked even vaguely related to externals/dependencies, etc.

    Unfortunately, that didn't solve my problem, and I still had to manually install the dependencies.

    Based on your comment, I went back to WAU, changed the prefs to what's listed on the front page of
    http://www.wowace.com/wiki/WowAceUpdater

    i.e. :

    X Automatic Dependency Download
    Default mode WITH externals
    X Unpack Addons
    X Skip SVN working copies
    Skip Version Check
    Diagnostic Logging

    Then I manually deleted all the Fubar-** dirs in the inteface/Addons dir, and had WAU to a full reinstall of all addons.

    That seemed to work too. Fubar still show up fine. Only real difference is that with the "unpack addons" checked, all bazillion-and-one supporting libs show up in the Addon folder, and hence on the Addon page in WoW - whereas before, it was a nice compact list of only the top-level addons that I was using.

    So that seems to fix it too. But something must have changed between yesterday and today to cause this problem in the first place. I've never had to manually download dependencies, or monkey with the WAU preferences before today.

    Thanks for the tip, btw. :)
    Posted in: FuBar AddOns
  • 0

    posted a message on FuBar 3.0
    Me too. Dependency information is messed up somehow.
    See my post here for fix:
    http://www.wowace.com/forums/index.php?topic=9490.msg155928#msg155928
    Posted in: FuBar AddOns
  • 0

    posted a message on Fubar not showing up, plugins show an map
    I think that somehow the dependency information has gotten jacked up.
    I was having the exact same problem - my Fubar bar disappeared.

    Worked fine yesterday, but today after I ran WAU, it was gone.

    I saw 15 errors, like so:
    LibRock-1.0\LibRock-1.0.lua:310: attempt to index local 'LibStub' (a nil value)
    LibRockConfig-1.0\LibRockConfig-1.0.lua:15: LibRockConfig-1.0 requires LibRock-1.0
    LibRockConfig-1.0\LibRockConfig-1.0.lua:15: in main chunk
    LibRockEvent-1.0\LibRockEvent-1.0.lua:14: LibRockEvent-1.0 requires LibRock-1.0
    LibRockEvent-1.0\LibRockEvent-1.0.lua:14: in main chunk
    and a bunch more ".. requires LibRock-1.0"

    Manually installing LibRock-1.0 fixed the problem, and Fubar shows up again.
    This problem seems to be happening elsewhere as well. I previously had BugSack installed, but it mysteriously vanished after the latest WAU run.

    I went back to WAU and had it install BugSack again, but after launching WoW, it showed up as "missing dependencies" in the AddOn page.

    Sooo, went back to WAU and manually installed !BugGrabber, and then it worked just fine.

    I double checked my preferences in WAU, and I have:

    X Automatic Dependency Download
    X Default mode WITH externals
    Unpack Addons
    X Skip SVN working copies
    Skip Version Check
    Diagnostic Logging

    I didn't change anything in my WAU settings between yesterday and today.
    Soooo, it looks like somehow the dependency information is hosed?
    Posted in: FuBar AddOns
  • To post a comment, please or register a new account.