Danbooru

Danbooru 2 Issues Topic

Posted under General

This topic has been locked.

BrokenEagle98 said:

For the artist editing issue noted above, commit 026a64c went live a few hours ago. I also just verified that editing artists works again.

I just checked, and it still works for me. Full disclosure though, it only works on Twitter when I use it with Google Chrome...

Yesterday I tried using "Batch to Danbooru" but only resulted in a blank page. Now it's fine.

I mis-guessed the copyright of post #2497272, and another user removed the tag. It has no copytags now, but the previous one is still showing up in the webpage title and tagged filename. This isn't an issue with my computer's cache, because it's also there when I check on mobile.

EDIT: Seems it is a cache issue, but on both sides. Now I have a tab where it doesn't show up, and a tab where it does...

EDIT 2: The name is there on Hijiribe, but not Sonohara. I assume this is just a cache/syncing issue that will automatically clear up... Sorry for wasting everyone's time with this post

Updated

Provence said:

Would it be possible to implement adding the source via the tag script?
I just tried it with that: source:https://exhentai.org/g/969119/722513d6e3/ on post #2464634
This could become neccessary if there are a lot of posts uploaded but without source.
So if I find the source, I've to manually fill in the source field. Since this works with parents, ratings, pools and every tag category, I thought it might also work with sources, but apparantly no?

@Provence

Commit d86e7b1 for issue #2664 and issue #2679 went live today, so you can now add the source through the edit dialogue box or via a tag script. I also verified this functionality myself.

BrokenEagle98 said:

@Provence

Commit d86e7b1 for issue #2664 and issue #2679 went live today, so you can now add the source through the edit dialogue box or via a tag script. I also verified this functionality myself.

Also note that now you can use double quotes in source metatag now, both when editing and searching, to allow spaces. So, queries like source:"Image board" or source:"One*punch man*" are possible now. The only restriction is that you can't use double quotes inside quoted strings - at least for now.

post #2503993
My comment there is pretty much saying everything: Is it possible or could it get implemented that there exist multiple parent for one post? The user DanbooruBlacklist wrote a comment containing all posts, but wouldn't it be more convenient to have a child-parent relationship?

Provence said:

post #2503993
My comment there is pretty much saying everything: Is it possible or could it get implemented that there exist multiple parent for one post? The user DanbooruBlacklist wrote a comment containing all posts, but wouldn't it be more convenient to have a child-parent relationship?

No, it would break existing architecture practically for nothing. If you need to, do it the other way around or use notes and/or comments.

evazion said:

@Provence: That may be the CSS for bigger thumbnails I gave you, I couldn't test it on the mod queue so it might have broken stuff there.

This seems to be the case. Just visited the queue without it and it looked normal.
Well, luckily, there are other ways to keep track of pending posts.

I've noticed wildcards don't work consistently when there's parentheses and/or other symbols.
For example, *_(cosplay) shuten_douji_(fate/grand_order)_(cosplay) will result an empty set, but *_(cosplay) shimakaze_(kantai_collection)_(cosplay) works correctly.
For another example, alternate_costume cosplay has post #2511932 in its set, which has alternate_costume, cosplay and taihou_(kantai_collection)_(cosplay) tagged. But it doesn't appear when searching for *_(cosplay) alternate_costume, and *_(cosplay) alternate_costume taihou_(kantai_collection)_(cosplay) returns an empty set.

As an aside, exclusions don't seem to work with wildcards.
For instance, I have both elizabeth_bathory_(fate/grand_order) and elizabeth_bathory_(brave)_(fate), which are subsets of lancer_(fate/extra_ccc. As such, the searches elizabeth_bathory*(fate* and lancer_(fate/extra_ccc) elizabeth_bathory*(fate* give the same result.
However, lancer_(fate/extra_ccc) -elizabeth_bathory*(fate* will not remove the variants from the results.

To be fair I don't know if the combination of exclusion and wildcard is actually a feature that has been implemented, but the cheatsheet doesn't mention it being unavailable. If it's not a feature it might be worth adding a note of it in the cheat sheet, below the part where wildcards and or-searches don't mix.