Danbooru changelog discussion thread

Posted under Bugs & Features

Also, unrelated to above, but I noticed a weird glitch where some members would have a displayed upload threshold of zero (despite it being clearly 15 as normal mechanically). Don't really know what the cause is nor do I have a Github account, but someone should probably look at that.

Knowledge_Seeker said:

Also, unrelated to above, but I noticed a weird glitch where some members would have a displayed upload threshold of zero (despite it being clearly 15 as normal mechanically). Don't really know what the cause is nor do I have a Github account, but someone should probably look at that.

It was this:

forum #350836 says:

new uploaders can now only upload at most one post per minute, until they have at least one approved post

When someone has no approved uploads, every upload will set their upload ratio to zero for one minute.

nonamethanks said:

new uploaders can now only upload at most one post per minute, until they have at least one approved post

They should also be limited to 5 slots until they have at least one approved post, I think.

Follow up on forum #355673 and forum #355948

Meeplee said:

I just noticed one of my saved searches has been frozen for at least 30 days now (there have been posts for the query since), is there anyway I can force it to refresh?

Update: I tried changing the labels to see if it helped. No luck. Fully re-creating the saved search also didn't fix it.

The query is simply: "narmaya_(granblue_fantasy)"

Meeplee said:

I just access my searches through the "Saved Searches" button that appears on the website header. I have 60ish searches saved and that's the only one that's frozen. Not doing anything different for this one.

Edit 1: Tried again, same query, different label with just "testing", still stuck.

Edit 2: I fixed it temporarily by changing the query to exclude an unrelated tag, so now it refreshes properly. I'm guess there's some caching problem with the old one. I'll give it a few days to clear and then maybe try restoring it to see what happens.

So today, about 20 days later, I tried recreating the saved search back again with the original query. It's still stuck. I can live with the workaround one, but there's definetely some issue there.

Don't get me wrong, I really appreciate all the new updates to the site, but is there a point in showing the total amount of pending BURs to non-admins? It's not like users below admin can do much to decrease their amount (besides approving artist BURs but that still probably wouldn't make that much of a dent).

I've noticed two new bugs within the last 3 or 4 hours.

  • I can no longer open drop down menus by pressing and holding on thumbnails on iPads, regardless of browser. This makes opening images in new tabs impossible.
  • Blacklists no longer work on parent/child menus.

Placeholder1996 said:

  • Blacklists no longer work on parent/child menus.

That blacklist issue has temporarily made the site basically unusable for me. Hope it's not even remotely intentional.

Say you've blacklisted gore (just a common example). You click some image from a search/homepage because it looks cute, but it's in a set and like the 4th image has unexpected gore in it. Surprise, you're gonna be looking at gore today.

This is a huge issue that makes blacklists completely useless, personally mine is quite large so it has a big impact.

Placeholder1996 said:

I've noticed two new bugs within the last 3 or 4 hours.

  • I can no longer open drop down menus by pressing and holding on thumbnails on iPads, regardless of browser. This makes opening images in new tabs impossible.
  • Blacklists no longer work on parent/child menus.

On the main danbooru page, I can’t zoom in or out on mobile (iPhone/Safari). If I tap the search bar, I can’t zoom out without refreshing the page.

TanashiZuki said:

That blacklist issue has temporarily made the site basically unusable for me. Hope it's not even remotely intentional.

Say you've blacklisted gore (just a common example). You click some image from a search/homepage because it looks cute, but it's in a set and like the 4th image has unexpected gore in it. Surprise, you're gonna be looking at gore today.

This is a huge issue that makes blacklists completely useless, personally mine is quite large so it has a big impact.

I can't imagine them doing that on purpose, it's a really big problem. Hopefully it'll be fixed soon

Placeholder1996 said:

I've noticed two new bugs within the last 3 or 4 hours.

  • I can no longer open drop down menus by pressing and holding on thumbnails on iPads, regardless of browser. This makes opening images in new tabs impossible.
  • Blacklists no longer work on parent/child menus.

Blacklists work again. I haven't checked the drop down menus yet. Drop down menus also work again. Thanks to whoever fixed those.

baconmeh2 said:

On the main danbooru page, I can’t zoom in or out on mobile (iPhone/Safari). If I tap the search bar, I can’t zoom out without refreshing the page.

I can zoom in, and I had that no new tabs problem too but it’s also fixed

I've just noticed that both production-2025.05.31 and production-2025.06.10 both list a change that allows mods to clear out key items from a user upon banning them (delete recent uploads, forum posts, comments and votes). Are these different methods to perform the same action of clearing items from a user or was this a duplicated item that made its way into both changelogs (or maybe it faced a regression?).

WRS said:

I've just noticed that both production-2025.05.31 and production-2025.06.10 both list a change that allows mods to clear out key items from a user upon banning them (delete recent uploads, forum posts, comments and votes). Are these different methods to perform the same action of clearing items from a user or was this a duplicated item that made its way into both changelogs (or maybe it faced a regression?).

That interface was refined and some bugs were squashed.
I usually try to condense the changelog from the commit list, and I didn't remember work was done on it during the previous deployment too, so I ended up writing about it in both instances. I'll remove it from the 05/31 changelog.

1 43 44 45 46 47 48 49 50 51