Danbooru

Danbooru 2 Issues Topic

Posted under General

Ah, okay.

It freaked me out and I ended up changing my password, lol.

Anybody getting this error while trying to upload from NicoNico Seiga?
error: Resolv::ResolvError - no address for lohas.nicoseiga.jphttps
Was forced to upload using the lohas address instead of the image page URL.

nanami said:

Anybody getting this error while trying to upload from NicoNico Seiga?
error: Resolv::ResolvError - no address for lohas.nicoseiga.jphttps
Was forced to upload using the lohas address instead of the image page URL.

I'm getting a no address for lohas.nicoseiga.jphttps error instead, worked around it by using the direct image link.

nanami said:

Anybody getting this error while trying to upload from NicoNico Seiga?
error: Resolv::ResolvError - no address for lohas.nicoseiga.jphttps
Was forced to upload using the lohas address instead of the image page URL.

Unbreakable said:

I'm getting a no address for lohas.nicoseiga.jphttps error instead, worked around it by using the direct image link.

This is fixed in the code but not deployed yet.

Site update

Changes
Fixes
  • Fixed multiple issues with NicoSeiga uploads. Added support for multiple new NicoSeiga posts types (manga posts, R-15 and anonymous posts).
  • Fixed issue with new notes being mispositioned after resizing the image.
  • Fixed admins not being able to upload videos more than two minutes long (topic #14647).
  • Fixed moderators not being able to replace images on older posts.
  • Fixed the batch bookmarklet not working with certain DeviantArt posts.
  • Fixed issue with the tag sidebar for searches being blank sometimes.
  • Fixed Nijie uploads not fetching full commentary when the commentary was too long.
  • Fixed issues with ArtStation cover url uploads.

Full changelog: https://github.com/danbooru/danbooru/compare/production-2020.06.03-043848-utc...production-2020.06.17-063517-utc

I'm not sure if this is the right place for this, but is anyone else having issues when on mobile where the link to see the full sized image doesn't work? I have to long press and click open in new tab to get the full size images to load now.

Edit: Found a workaround in settings to just have all images load at full resolution, but it may still be an issue for others.

Updated

Would it be possible to have a meta tag qualifier for, say, family:any/none? I would like to filter out posts with no parents or children so I don't have to keep checking said posts for the best version (it's not always the parent), and while child:none parent:none achieves that, you can't get the reverse. If you want check non-family posts and then family posts, you'd have to see the parents separate from their children, making browsing more difficult.

The backend can use the conditionals that the child and parent qualifiers use, or if not, then WHERE parent_id IS NOT NULL OR has_children = true / WHERE parent_id IS NULL AND has_children = false.

Updated

EMUltra3 said:

Would it be possible to have a meta tag qualifier for, say, family:any/none?

If OR'ing metatags is a possibility, then the family:any that you want to achieve could be done with a ~parent:any ~child:any search. Right now that isn't supported (and I'm not sure if it's possible), but going forward that may be the best solution to avoid creating a whole bunch of new metatags for various scenarios.

I don't see it in the changes - is it just me or the sidebar no longer shows the most searched tags?

indexador2 said:

I don't see it in the changes - is it just me or the sidebar no longer shows the most searched tags?

They're still shown for me. What search are you not seeing it on?

Minor update
  • Fixed "view original" link not opening original image on mobile.
  • Fixed the tag sidebar on the front page not showing popular tags sometimes.
  • Fixed IQDB 599 errors during uploads.
  • Fixed file size not appearing during uploads.

BrokenEagle98 said:

If OR'ing metatags is a possibility, then the family:any that you want to achieve could be done with a ~parent:any ~child:any search. Right now that isn't supported (and I'm not sure if it's possible), but going forward that may be the best solution to avoid creating a whole bunch of new metatags for various scenarios.

This is on the roadmap. It's doable but the search parser will need to be rewritten to allow for it.

DreamFromTheLayer said:

In the post versions / tag history page, what is the purpose of the checkbox? It doesn't seem to do anything.

I you check at least one an "Undo selected" link will appear at the lower top bar allowing you to revert multiple changes at once.