Danbooru 2 Issues Topic

Two things:

1. I would also prefer not having Enter activate autocomplete.

2. Opening a post page in a new tab on mobile, with responsive mode disabled, is acting weird, but in a different way than before. Before, the image simply didn't load. Now, the image loads, but I can only scroll vertically, not horizontally. I also can't pinch zoom, but can double-tap zoom. And if I swipe right, the page disappears and I just see white. Reloading the page fixes all of these problems, and opening a post in the current tab does not have these problems.

The previous behavior of the Enter key was broken. Previously if you typed for example d.va, pressed Down to select d.va_(overwatch) from the autocomplete menu, then pressed Enter, it would search for d.va instead of d.va_(overwatch). You had to press Tab instead. This caused many missed searches.

Many people didn't know to use the Tab key for autocomplete and that Enter didn't work. It's not documented anywhere and it's not how autocomplete works on any other booru, or most other websites in general.

So the change was that if you use up/down to select a tag from the autocomplete menu, then press Enter, it accepts the completion. This is how it works on every other booru. The behavior of not submitting the search when you've already typed a complete tag is a bug that will be fixed.

I've noticed order:change takes quite some time for searches without any tags. Maybe limit to searches that include such?

Alternatively it can be indexed but that might not be a good idea given how frequently it updates. I don't know anything about the servers' performance.

evazion said:

The previous behavior of the Enter key was broken. Previously if you typed for example d.va, pressed Down to select d.va_(overwatch) from the autocomplete menu, then pressed Enter, it would search for d.va instead of d.va_(overwatch). You had to press Tab instead. This caused many missed searches.

Many people didn't know to use the Tab key for autocomplete and that Enter didn't work. It's not documented anywhere and it's not how autocomplete works on any other booru, or most other websites in general.

So the change was that if you use up/down to select a tag from the autocomplete menu, then press Enter, it accepts the completion. This is how it works on every other booru. The behavior of not submitting the search when you've already typed a complete tag is a bug that will be fixed.

I hope it will take shortened meta tags like rating:s into account because those aren't listed under autocomplete.

...and I hope it will behave as it always used to when your cursor is in the middle of a tag as well...

kuuderes_shadow said:

...and I hope it will behave as it always used to when your cursor is in the middle of a tag as well...

I hadn't happened across this, but yeah, that's also bad. You can just happen to have the cursor below the input box, type e.g. tail, hit Enter, and instead of searching for tail, now you have tail_bell or something in the box.

Laethiel said:

I hadn't happened across this, but yeah, that's also bad. You can just happen to have the cursor below the input box, type e.g. tail, hit Enter, and instead of searching for tail, now you have tail_bell or something in the box.

That wasn't actually what I was talking about*, but yes that's another thing.

*I meant when you had for instance yuki|kaze_(kantai_collection), with the | indicating where the blinking cursor is, having just amended the first 4 letters to change it from, for instance, hagikaze_(kantai_collection). Previously hitting enter would search for yukikaze_(kantai_collection). Now it changes it to nagato_yuki kaze_(kantai_collection)**. Given that I do this sort of thing a lot when going between kancolle characters, this is a real pain for me.

**and of course if you then wipe this error and type out the "yuki" part again it just does the same thing.

Ahh, I see. I just replicated your yukikaze example, and that's definitely not what I'd expect or want it to do.

Two more things:

1 - The * function is basically broken by this at the moment.
2 - Any "bug fix" had better not change the functionality of tab key - I don't want to start mass mistagging because some weird artist comes along who decides to call themselves something like "eyeb"* or something.

*eyeb then tab is the best way to get eyebrows_visible_through_hair, in case you're wondering, but there are hundreds of things I could have used as an example there - some of which actually exist, eg. loo would come up instead of looking at viewer - or look if you type an extra letter. Thanks to this update, of course, the problem is currently the other way around. Beforehand, of course, there was no problem.

Really, these are all quite basic features of the tab key, and most if not all this would have been brought up had this change actually been discussed beforehand rather than quietly enacted without telling anyone or asking for feedback. This would have then either enabled these problems to be removed before the change was made, or else led to the change being abandoned altogether as more hassle than it is worth, which would have been no bad thing tbh. Removing what is probably the second most used feature of the site (behind clicking on images to open them) is hardly some minor change.

Relax. These are bugs and not intentional changes. I am aware of the issues and am working on a better fix.

+1 for

1. I would also prefer not having Enter activate autocomplete.

The fix (issue #3549) was merged a couple days ago but is not yet deployed.

Most pages give me error 502. On hijiribe and safebooru.donmai.us too.
Trying to upload gives a long list of errors (when it doesn't 502).

worldendDominator said:

Most pages give me error 502. On hijiribe and safebooru.donmai.us too.
Trying to upload gives a long list of errors (when it doesn't 502).

Sounds like we've got sonohara server troubles again. Attempting to view site pages through sonohara directly, instead of the danbooru address shared by both servers, gets a Failbooru, whereas using the hijiribe address, as I am now for typing this response, works. These are the same symptoms that occurred when the sonohara server went down just over one week ago. (Search one or two pages back in this topic from this post, and you'll see.)

Hijiribe remained okay throughout that time, but both servers have to be working for any posts to be added to the site. As of now, the last post added was about 4 hours ago, so it would seem Sonohara's been down that long. Here's hoping Alfred can be able to fix it soon.

worldendDominator said:

Most pages give me error 502. On hijiribe and safebooru.donmai.us too.
Trying to upload gives a long list of errors (when it doesn't 502).

Same, I've been experiencing this on on/off basis since yesterday.

Ever since albert tried to upgrade the servers, they've been having connection problems. What's with the hardware he's using right now?

Any technical details? I do devops by trade and would love to offer any help I can.

FormerlyJ said:

Any technical details? I do devops by trade and would love to offer any help I can.

Most technical stuff is not discussed on the forums here, rather the github: https://github.com/r888888888/danbooru

I don't frequent there often but I do know it's pretty active.

I've been experiencing the same issues today, including the error 502 and the inability to upload.

It seems the 502 stopped happening here about one hour ago, the pages have been loading fine. But I still can't upload images.

Having issues uploading @albert https://ghostbin.com/paste/xw276