• 0

    posted a message on Where exactly are bug reports/tickets supposed to live?
    Quote from Allara
    You can't just start from any random page; clicking Tickets from the page you linked takes you to the global CurseForge tickets.


    I apologize for not magically intuiting that. They all say "Tickets". I'm still working out which ones link to here and which ones link elsewhere. Apparently they're context sensitive, so going to a WowAce project and clicking tickets leads to WowAce tickets, but going to a WowAce knowledge base and clicking tickets leads to Curseforge. "Of course," as you say.

    Do you understand now why those of us who are new might just be a little confused?


    What was your issue?


    Broken redirection links, as explained in the ticket.
    Posted in: General Chat
  • 0

    posted a message on Where exactly are bug reports/tickets supposed to live?
    Quote from Laibcoms
    Which add-on are you talking about? I view tickets over at curseforge with no problems at all. ^_^


    Examples are in the ticket.


    I can view tickets fine on WoWAce, doesn't lead me to CurseForge.


    Starting on http://www.wowace.com/knowledge-base/ (picking a page at random, since that's where I happen to be), I click the "Tickets" link and am sent to http://www.curseforge.com/projects/curseforge/tickets/

    Pretty much anything I try to do here leads to me to Curseforge. I had no idea that it was even possible to have projects that were "only" on WowAce; I thought the whole point of the merge was to move projects from WowAce to Curseforge.
    Posted in: General Chat
  • 0

    posted a message on Where exactly are bug reports/tickets supposed to live?
    Nope, I am not. Plain vanilla Firefox 3.

    I am sure the bouncing between sites all makes sense to the people who set it up, but I'm tired of getting lost. There are other bugs I can usefully work on, so I've given up on the problem. The next new user to get lost can work it out.
    Posted in: General Chat
  • 0

    posted a message on BugGrabber / BugSack -- Ace2'd
    The description page is incorrect. Bug reporting tickets are disabled (!) for BugSack, so I'm reporting it here.

    BugSack includes a FuBar plugin that displays the last 5 errors in the tooltip

    Not anymore! The soft requirements on LDB frontends or FuBar2whatever is not mentioned either.
    Posted in: General AddOns
  • 0

    posted a message on Where exactly are bug reports/tickets supposed to live?
    Quote from Seerah
    The project menu bar on the Barrel project page


    GAAAAAAHHHHHH

    There are 3 different "project pages" for Barrel. No two look like. Curse's "tickets" link is broken. Curseforge can't find Barrel at all. Wowace's "tickets" link tells me I don't have project permissions.

    Sorry if I'm sounding snippy, but being bounced between 3 different websites, all with inconsistent interfaces, is incredibly frustrating.
    Posted in: General Chat
  • 0

    posted a message on Where exactly are bug reports/tickets supposed to live?
    Quote from Seerah
    edit: also, BugSack has a minimap button now - you dont' need Barrel


    Barrel itself still has bugs, is still useful for things besides BugSack, is still breaking Bartender4, and so I'd like to still be able to find its single isolated-on-wowace ticket.
    Posted in: General Chat
  • 0

    posted a message on Where exactly are bug reports/tickets supposed to live?
    Quote from Seerah
    Barrel project page


    From where?

    Curse? Doesn't work, as reported above, all 403.

    Curseforge doesn't even find "Barrel" when I search for it. No search results at all.

    Wowace [edit: barrel's wowace project page] has a "post a ticket" link, but not a "view tickets" link.
    Posted in: General Chat
  • 0

    posted a message on Where exactly are bug reports/tickets supposed to live?
    Two separate problems, both leading to frustration with the current ticket system.

    The first one actually has its own ticket, after I finally beat the bug report page into submission. It's #793 on curseforge. Summary: trying to view curseforge tickets leads to 403 web errors on wowace.

    The second one is this: we're trying to track down a bug in the interaction between Bartender4 and Barrel. (The fact that enabling Barrel -- which would let me see *other* bugs from bugsack -- is itself causing bugs, does not make this any more fun.) Somebody in http://forums.wowace.com/showthread.php?t=13684 said they had submitted a ticket for Barrel, which is now http://www.wowace.com/projects/barrel/tickets/1-cannot-use-api-for-openallbags-while-barrel-enabled/

    You'll note that ticket is "ticket #1", and that there are apparently no other wowace tickets, and that this ticket cannot be seen from curseforge (which reports no tickets for Barrel). Also, trying to view/search any kind of tickets from wowace leads to curseforge, which makes the above Barrel ticket essentially inaccessible. I can't find a way to even see it other than just following the link from the thread above.
    Posted in: General Chat
  • 0

    posted a message on Omen3
    Quote from Xinhuan
    Next update there will be an option to change your bar's color.


    Got it, love it, thank you!
    Posted in: Raid AddOns
  • 0

    posted a message on What error handling addons do you guys use?
    Barrel will put minimap icons for those addons back onto the minimap, however:

    1) Running Barrel and Bartender4 at the same time causes UI errors each time you try to open your bags, preventing anything beyond the main backpack from opening.

    2) The drop-down menus from minimap icons added by Barrel do not themselves contain any options to show/hide the minimap icon. You have to configure those through Barrel. Which sort of makes sense, but can confuse and annoy people accustomed to the fubarplugin way.
    Posted in: General Chat
  • 0

    posted a message on Omen3
    Is it possible to get back the option to color the player's own threat bar something unique (bright red was what we'd use in Omen/Omen2)?
    Posted in: Raid AddOns
  • 0

    posted a message on BugGrabber / BugSack -- Ace2'd
    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
    Posted in: General AddOns
  • 0

    posted a message on Barrel (Official Topic)
    Quote from Loupyn
    I'm not sure if you are still going to work on Barrel, copystring, but I think there may be an issue with the old libraries in the current 0.1 version. Posted the ticket for you here: http://www.wowace.com/projects/barrel/tickets/1-cannot-use-api-for-openallbags-while-barrel-enabled/


    It's Barrel + Bartender4 that's doing it (added that to the ticket).

    I'll certainly look at it more tonight but I was up until almost 3am last night trying to track down this weird SetHeight bug attempting to use the OpenAllBags API call and needed sleep for work :P. If you aren't able to recreate the issue I'll see about updating the embedded libraries locally.


    Tossing in the generic "Ace3" package, which (iirc) should contain the most recent version of all those libraries, didn't help.
    Posted in: Data Broker AddOns
  • 0

    posted a message on BugGrabber / BugSack -- Ace2'd
    Quote from HunterZ
    Get Barrel if you want it to show up as a minimap icon.


    Amusingly, the current version of Barrel handles Omen and Bartender4, but throws errors with the current version of BugSack. At least BugSack still captures them correctly though!

    [2008/10/15 15:59:56-2-x13]: Barrel-0.1\Core.lua:306: attempt to index local 'dataobj' (a nil value)
    Barrel-0.1\Core.lua:265: in function `UpdatePosition'
    Barrel-0.1\Config.lua:94: in function <Interface\AddOns\Barrel\Config.lua:92>
    (tail call): ?:
    <in C code>: ?
    <string>:"safecall Dispatcher[2]":9: in function <[string "safecall Dispatcher[2]"]:5>
    (tail call): ?:
    AceConfigDialog-3.0\AceConfigDialog-3.0.lua:781: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:600>
    AceConfigDialog-3.0\AceConfigDialog-3.0.lua:829: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:821>
    (tail call): ?:
    <in C code>: ?
    <string>:"safecall Dispatcher[3]":9: in function <[string "safecall Dispatcher[3]"]:5>
    (tail call): ?:
    AceGUI-3.0\AceGUI-3.0.lua:264: in function `Fire'
    Ace3\AceGUI-3.0\widgets\AceGUIWidget-Slider.lua:47: in function <...dOns\Ace3\AceGUI-3.0\widgets\AceGUIWidget-Slider.lua:40>
    
      ---


    Still, better than nothing!
    Posted in: General AddOns
  • 0

    posted a message on BugGrabber / BugSack -- Ace2'd
    Quote from Ydrisselle
    Quote: Originally Posted by ant1pathy
    I can understand removing FuBar support, as not everyone uses that. But removing it from the minimap is just asinine; means I can never load JUST BugSack/BugGrabber and one other addon and see what errors it kicks.

    The minimap button was a FuBarPlugin feature.


    But FuBarPlugin was bundled/embedded with BugSack. We were able to use it just fine without ever having FuBar installed. Now it no longer Just Works; now users are required to be aware that BugSack is no longer a "front end" to BugGrabber, but rather an inaccessible middle layer (which rather raises the question, what's the point? why bother with really nice and readable formatting if you can't easily see it?)

    At the very least, give us a slash command back. That way we can continue to actually use BugSack -- especially important at this time of constant addon flux and debugging of a new patch -- while those of us who had never heard of "LDB" before today work out which of the new front ends we prefer.

    edit: the reason I'm semi-ranting and more than semi-annoyed is, like Panzerdoll says a couple posts down, this was all yanked out from under us with no warning, often while we were trying to update and debug other addons. Again, please, just give some slash command to view the frame and we'll find a "pretty" interface later.
    Posted in: General AddOns
  • To post a comment, please or register a new account.