Danbooru

Read the rules before proceeding!

Topic: DanbooruUp, tag completion for Firefox, Chrome, Opera

Posted under General

10half

DB Uploader extension issue is logged in Github although I'm not sure whether the fix will be on the Danbooru side or the extension side.

  • ID: 84788
  • Permalink
  • lastsinz

    Hm, the tag autocompletion works on the searching field but not on the tagging field. I'm not very up to date with this thing, is this supposed to happen or has there already been a fixed version?

  • ID: 84968
  • Permalink
  • v571866

    the uploader works fine, with a few problems, notably the unhandled exception error, but the upload proceeds normally.

  • ID: 84969
  • Permalink
  • DschingisKhan

    lastsinz said:

    Hm, the tag autocompletion works on the searching field but not on the tagging field. I'm not very up to date with this thing, is this supposed to happen or has there already been a fixed version?

    Not that I've seen. Is someone working on this? Where does the source live these days? Because not having completion on the upload and edit pages is pretty miserable.

  • ID: 84971
  • Permalink
  • fireattack

    Sal.N said:

    Find artist aside, but you can still use it. The image will be uploaded normally despite showing error.

    Yeah i know. but i rarely upload just use it for "find artist" feature :s

  • ID: 84997
  • Permalink
  • zigzag

    Any idea if/when tag autocompletion for the tagging field will be fixed? I've grown very fond of it.

  • ID: 85075
  • Permalink
  • Kadoya

    Might be just me, but for some reason I can't upload with this anymore. Normally (or at least these days) I can upload just fine (with that error screen) but now it just does not go through.

  • ID: 85255
  • Permalink
  • v571866

    I have been checking the upload queue and seeing multiple pending entries alongside completed ones.

    I'm assuming all pending entries are made with the uploader.

    I guess i have to use the normal upload page for now.

  • ID: 85259
  • Permalink
  • v571866

    Sorry for the bump and doublepost.

    Still expecting an update/ETA on the fix.

    It still uploads fine but it can no longer update the tag listing.

  • ID: 85610
  • Permalink
  • zigzag

    The extension crashes Opera on the front page for me. I'm guessing it's searching for something that was on the old front page (tag update?).
    The autocomplete was working in the search field for a while, but then it stopped as well.

    I tried using it on Chrome, but I guess without a tag update it wouldn't work anyway since I've never run it there before.

  • ID: 85887
  • Permalink
  • Fred1515

    zigzag said:
    The extension crashes Opera on the front page for me. I'm guessing it's searching for something that was on the old front page (tag update?).
    The autocomplete was working in the search field for a while, but then it stopped as well.

    I'm using Opera 12.14 and haven't experienced any crashes, and autocompletion still works in the search field. Are you sure it's not some other extension that causes the crash?

  • ID: 85888
  • Permalink
  • itsonlyaname

    Been poking at the code for a few hours,

    It seems like the autocomplete does still work on opera, but only if you had already downloaded the tags.
    Getting the tags seem to rely on the tag API call with "limit=0" to return all tags in existence at once, something which no longer works now. (At a rate of 20 tags per link, and maybe... 200,000 active tags? it'd be around 10k calls to download all of them, easily taking 30-120 min depending on how much requests you spam at once... Not a nice option.)
    Thus a "clear tags" will break it beyond repair - it's auto-update & "Update after post submission" might also break stuff, best to turn that off for now.

    With a clean install (just updated the html so the '<>' button appeared again), i couldn't get it to work at all, since it could only download 20 tags.
    Fixing the rightclick -> upload to danbooru on chrome is simply updating the url in the code.

    Also, albert tweeted 2 days ago that he is planning to eventually add autocomplete to danbooru itself, or import this extension.

    Updated by itsonlyaname

  • ID: 85890
  • Permalink
  • zigzag

    Having it built in would be excellent.

  • ID: 85901
  • Permalink
  • Kadoya

    I may have done something stupid when I cleared my tags and updated. I literally have 0 tags when
    I try using the tag autocomplete. Is there's a solution or do I have to wait till Albert eventually implement it to Danbooru itself?

    Updated by Kadoya

  • ID: 86590
  • Permalink
  • zatchii

    I'm aiming to have a fully Danbooru 2 compatible version within a week or so.

  • ID: 86889
  • Permalink
  • reese

    Best news I've heard all day.

  • ID: 86891
  • Permalink
  • Kikimaru

    zatchii said:

    I'm aiming to have a fully Danbooru 2 compatible version within a week or so.

    Not-sure-if-serious-or-April-Fools.

  • ID: 86925
  • Permalink
  • itsonlyaname

    It's serious :) albert also mentioned he was working together with zatchii on it when closing issues on github.

  • ID: 86947
  • Permalink
  • zatchii

    Appy-polly-loggies for the neglect!

    0.5.0 is up on the web page, and should fix most of the problems people have been having since the upgrade. I'll push out auto-updates and upload it to the Chrome and Opera stores in just a bit.

    The main new feature is Danbooru 2 compatibility. Tag updates, completion in the tag edit box, uploads, etc. should all be working again.

    The tag updating now uses JSON, so the update URI in Firefox should point to a .json file. Preferences should be updated automatically, but it's something to watch out for if you're using a non-standard setup.
    You'll need to be logged in for tag updates to work, so check that if you're getting 403 errors.

    The tag dump that returns all tags on the site is still a little wonky. You may notice the extension fetch a backup dump from pianosite.net for bootstrapping.

    The extension source code is now hosted on Github

    Firefox 3.0 is sadly no longer supported. Consider upgrading to 3.5 or later.

    I'm sure there are bugs, so post them here, or file an issue on Github if you prefer.

  • ID: 87519
  • Permalink