Topic: General bug report thread - bugs here, bugs there, bugs everywhere, come here and report your bugs

Posted under Site Bug Reports & Feature Requests

hesitantalien3 said:
Almost every time I visit the site and browse a few images my wifi drops for a moment then returns. Wired connection stays on just fine, however webms occasionally don't work after the drop. This is my own personal internet connection and I am the only one who lives at my house or uses my internet

try browsing another gallery site (e.g. danbooru, pixiv, deviantart) and see if you get the same behaviour.
what hardware are you using specifically? a laptop? an android phone?
what leads you to believe the wifi drops out? e.g. does the symbol in the system tray switch briefly to the disconnected icon then back to normal? web pages yield an error if they were loading at the time?
you're sure there's no other network connection enabled at the same time? e.g. maybe you're actually using cellular internet, and the drop-out is switching from one tower to another

Genjar

Former Staff

The bulk updater no longer allows chaining tag actions from unalias to a new alias or implication.

For instance:

unalias x -> y
imply x -> z

...throws an error: Error: Antecedent tag must not be aliased to another tag (create implication x -> z)

This has massively reduced its usefulness. Unaliased tags are left at zero posts, so those cannot be easily aliased/implicated in another update. Since that requires them to have 20+ posts. Same goes for unimplicated tags that have less than 20 posts.

genjar said:
The bulk updater no longer allows chaining tag actions from unalias to a new alias or implication.

For instance:

unalias x -> y
imply x -> z

...throws an error: Error: Antecedent tag must not be aliased to another tag (create implication x -> z)

This has massively reduced its usefulness. Unaliased tags are left at zero posts, so those cannot be easily aliased/implicated in another update. Since that requires them to have 20+ posts. Same goes for unimplicated tags that have less than 20 posts.

I will see what I can do. As I have been adding sanity checks for aliases and implications to prevent them from breaking the site or corrupting posts, the lack of sanity checking that BUR relied on has been slowly vanishing. So I'm stuck in a situation of removing sanity checking from BUR, which is not a great situation, as they have huge potential for messing things up if they go wrong. Right now validation of each item takes place in isolation because there is no way to simulate that previous actions took place successfully. This forces me to create a simulation process and write a bunch of code for what amounts to a very hacky feature that I'm feeling more and more frustrated with by the day. All of the code that the BUR system interacts with has been designed without the concept of being run as part of a script, but created by hand inside a static system.

It's turned into one of those endless wells of pain and problems and I have to keep making them less useful so that we don't end up with totally invalid alias and implication state.

Updated

Genjar

Former Staff

kiranoot said:
It's turned into one of those endless wells of pain and problems and I have to keep making them less useful so that we don't end up with totally invalid alias and implication state.

Hmm. Would it be feasible to waive the 20+ post requirement for bulk updates? Then the re-aliases/implications could be easily done in subsequent bulk updates, after first unaliasing them. That'd still leave the important checks in place; the post count requirement doesn't seem like something that could result in a major mess...

genjar said:
Hmm. Would it be feasible to waive the 20+ post requirement for bulk updates? Then the re-aliases/implications could be easily done in subsequent bulk updates, after first unaliasing them. That'd still leave the important checks in place; the post count requirement doesn't seem like something that could result in a major mess...

I talked this over with Nimmy, and we agreed that it's causing more work and trouble than it's actually saving us. So it is going to be removed along with the wiki page requirements. I will likely have excised it from the code tomorrow along with some fixes for the uploader.

I still intend to try and fix the BUR validation process, but it may be deferred for a little bit so I don't want to just rip it out entirely.

I'm unable to login/change password or even accept the terms of agreement.

I'm using a firefox browser on my Android.

anytime I try to login I keep getting:

An unexpected error occurred

Log ID (none)

Ever since the transition to the new site i've had every time I login a "You have unread mail (2)" notification message and I've tried checking my messages, deleting said unread messages (at least I think I did), and turning off the notification but it just doesn't go away. Please help!

Color formatting doesn't work at all with the new table format. It actually breaks the format instead. The format also breaks code that appears after the table. The code block in my post will not display if it is posted after the table.

[table]
[tbody]
[td]Text without formatting.[/td]
[td][color=red]Text that is red.[/color][/td]
[/tbody]
[/table]
Text without formatting.Text that is red.

I just noticed that the 'Popular' page's API returns deleted posts amongst its results, whereas the page itself completely lacks the HTML of those posts i.e. if 5 out of 100 posts-per-page are deleted, the page's HTML only has the remaining 95, whereas its respective API result has all 100 results.

What's the point of having undo buttons on the post changes page if they don't do anything?

wat8548 said:
What's the point of having undo buttons on the post changes page if they don't do anything?

they might do something if you're logged in as a moderator or admin

bitWolfy

Former Staff

wat8548 said: What's the point of having undo buttons on the post changes page if they don't do anything?

bipface said: they might do something if you're logged in as a moderator or admin

You can undo your own changes, but not someone else's. Although, it does not remove the edit, it just creates a new one that reverts it.
I'm honestly not sure if this is the intended behavior, but it does kinda make sense not to allow everyone to just roll back a bunch of changes.

For the last couple of days, when I click to log in after putting in my username and PW, the site gets stuck loading my log in status. When I click the "sign in" tab again, it gets me out of the loading and my account is logged on.

I think there is a bug on the mobile browsers as well. I keep seeing things I’ve blacklisted and I have to manually remove them in the search bar. Is this a new bug or is it an old one?

maria_kauffman said:
I think there is a bug on the mobile browsers as well. I keep seeing things I’ve blacklisted and I have to manually remove them in the search bar. Is this a new bug or is it an old one?

I noticed this today too although for me it's just random posts. (I am using a computer)
Like I will see a post that is supposed to be blacklisted and when I click on the post, it tells me the tags that are blacklisted and it still gives me the option to turn the blacklist off, even though it didn't blacklist the image in the first place like it should have.
But for some reason this is just for random posts because when I disable my blacklist on the main page, blacklisted images do appear.

when I click reply to insert a quote, my browser scrolls to the top of the page and no quote is inserted. IE, firefox, chrome, opera. no extensions running.

If type:sfw or flash are on blacklist, it still loads flash "enable flash" page, and disables keyboard shortcuts when going through posts (since doing it that way does not skip blacklisted posts)

james34 said:
I'm unable to login/change password or even accept the terms of agreement.

I'm using a firefox browser on my Android.

anytime I try to login I keep getting:

An unexpected error occurred

Log ID (none)

I'm having the same problems...

Clicking on reply in the comment section still fails too often, just taking you to the top of the page

bitWolfy

Former Staff

The favorites displayed on the user's profile page are behaving strangely.

The page displays the user's last six favorited posts, which is correct.
However, instead of being displayed in the order in which they they were added to favorites (newest first, like uploads), they are instead ordered by upload date (oldest first).

Removing .order(created_at: :desc) here may or may not fix it.

bitwolfy said:
Removing .order(created_at: :desc) here may or may not fix it.

probably also need to change the next line
Post.where(id: ids)
since it would be translating to just select ... where post.id in (x, y, z)

The API shows the size of sample images to have a max width of 850px, but most samples (roughly id:<2100000) are max 800px in both dimensions.
I'm guessing the way samples are generated was changed recently and the API just calculates the sizes on the fly (making it inaccurate for images uploaded before the change)?

While adding tags to a post and getting suggestions while typing, using the mouse to add a tag from the dropdown list works like you'd expect it to, but using the arrow keys to scroll through the list erases the entire text box and replaces it with that tag only! And once done, it seems like there's no way to undo it.

I guess this is a known issue already, but either way, please take a look at it. It's very annoying to do by mistake.

butt said:
While adding tags to a post and getting suggestions while typing, using the mouse to add a tag from the dropdown list works like you'd expect it to, but using the arrow keys to scroll through the list erases the entire text box and replaces it with that tag only! And once done, it seems like there's no way to undo it.

I guess this is a known issue already, but either way, please take a look at it. It's very annoying to do by mistake.

what browser, version, OS ?
doesn't happen to me on firefox 56 (windows)

butt said:
While adding tags to a post and getting suggestions while typing, using the mouse to add a tag from the dropdown list works like you'd expect it to, but using the arrow keys to scroll through the list erases the entire text box and replaces it with that tag only! And once done, it seems like there's no way to undo it.

I guess this is a known issue already, but either way, please take a look at it. It's very annoying to do by mistake.

I am also not seeing this on windows 10, under Chrome 85 at this time. I think this might be an extension causing trouble? The lack of undo is because browsers are really weird about how they process input and undo states. It's not currently possible to customize or push undo states, so javascript based edits are frequently invisible to the undo system.

I added a post to a pool. It worked, but instead of the interface telling me that it worked, I got this on the browser console:

Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'self' ads.dragonfru.it js-agent.newrelic.com bam.nr-data.net https://www.google.com/recaptcha/ https://www.gstatic.com/recaptcha/ https://www.recaptcha.net/ https://mc.yandex.ru/ https://yastatic.net 'nonce-2NblawTili9ZP3v5kCR+Dw=='". Either the 'unsafe-inline' keyword, a hash ('sha256-NWIA1uZFXuZ3fbgGQ4ZfUKmN744OJQLjVXb5mZDGrLk='), or a nonce ('nonce-...') is required to enable inline execution.

b @ jquery-3.5.0.min.js:2
globalEval @ jquery-3.5.0.min.js:2
text script @ jquery-3.5.0.min.js:2
(anonymous) @ jquery-3.5.0.min.js:2
l @ jquery-3.5.0.min.js:2
(anonymous) @ jquery-3.5.0.min.js:2

This happens in both Chrome and Firefox for me.

bipface said:
what browser, version, OS ?
doesn't happen to me on firefox 56 (windows)

Firefox 80, Windows. I don't use any add-ons that would interfere with it, I think.

I forgot to mention, though, I have "enable auto-complete" turned off in my settings (so that I can repeat searches easily instead of having to type them out over and over). That might break the auto-complete feature for tag entry.

EDIT: Yep! Tag entry works as intended with "enable auto-complete" on. I would personally appreciate having auto-complete work properly in tag entry regardless if I have it enabled for searches, since it's such a useful feature.

Updated

butt said:
Firefox 80, Windows. I don't use any add-ons that would interfere with it, I think.

I forgot to mention, though, I have "enable auto-complete" turned off in my settings (so that I can repeat searches easily instead of having to type them out over and over). That might break the auto-complete feature for tag entry.

EDIT: Yep! Tag entry works as intended with "enable auto-complete" on.

That's just firefox treating the field like you want it to be filled with a previous entry, which is why it deletes it all. Not something I can fix on my side.

kiranoot said:
That's just firefox treating the field like you want it to be filled with a previous entry, which is why it deletes it all. Not something I can fix on my side.

No, it's not a question of a previous entry. It's e621's native dropdown menu. This is what the bug looks like - the only thing that happened between pic 1 and 2 was me pushing the down arrow once.

The dropdown looks and acts exactly the same regardless if I have auto-complete on or not, it's just that it doesn't work properly with auto-complete off, using the arrow keys.
Clicking the dropdown, though, works as intended even with auto-complete off.

Updated

butt said:
No, it's not a question of a previous entry. It's e621's native dropdown menu. This is what the bug looks like - the only thing that happened between pic 1 and 2 was me pushing the down arrow once.

Can confirm - it's an issue in both Chrome and Firefox.

Seems like the auto-complete does not get turned off properly. With it disabled, the dropdown shouldn't even appear.

butt said:
No, it's not a question of a previous entry. It's e621's native dropdown menu. This is what the bug looks like - the only thing that happened between pic 1 and 2 was me pushing the down arrow once.

The dropdown looks and acts exactly the same regardless if I have auto-complete on or not, it's just that it doesn't work properly with auto-complete off, using the arrow keys.
Clicking the dropdown, though, works as intended even with auto-complete off.

Okay, found the root cause for this, put in a fix and have deployed it. It should now be properly respecting the settings and not initializing a broken copy of the autocomplete code for the tags editor anymore.

kiranoot said:
Okay, found the root cause for this, put in a fix and have deployed it. It should now be properly respecting the settings and not initializing a broken copy of the autocomplete code for the tags editor anymore.

Yep, it works without any issues for me now. Thanks!

wat8548 said:
Why does post #2387200 not list post #2386061 as a child post, but post #2386061 does list post #2387200 as its parent post?

My guess would be because #2386061 was flagged at the time (now deleted).

Not sure if it's intentional on KiraNoot's part or a happy accident, but I can see why it would be desirable to have deleted posts still link up to their parent, but you don't want parents to link down to their deleted children. Although I can see where you're coming from, since I just assumed parent/child was a symmetrical relationship.

kaworu said:
My guess would be because #2386061 was flagged at the time (now deleted).

Not sure if it's intentional on KiraNoot's part or a happy accident, but I can see why it would be desirable to have deleted posts still link up to their parent, but you don't want parents to link down to their deleted children. Although I can see where you're coming from, since I just assumed parent/child was a symmetrical relationship.

The relationship is still symmetrical. You can see in the json output, under "relationships" on the very bottom, that #2387200 still has #2386061 listed as its child. It's just that the site only displays active children, much like the search page does not show deleted posts unless you deliberately search for them.

The speciestags: metatag doesn't seem to work. No matter what number or range I put next to it, it gives me zero results.

millcore said:
Post the bugs you've found here. Please be as specific and as constructive as possible; the more info about the issue you include the easier it will be for us to fix it.

Other forums you can check:
https://e621.net/forum_topics/25717 - List of changes that are NOT bugs
https://e621.net/forum_topics/25748 - Quick FAQ/Q&A thread
https://e621.net/forum_topics/25718 - For documentation problems
https://e621.net/forum_topics/25716 - The theme/aesthetic issues (please read the main post before using)

If you find other bugs floating around in the forum you can post a link to those forums here so they don't get lost.
If you already made another thread for a bug then please go edit [Bug] at the start of the title so it's easy to
Hopefully you got that.

bitwolfy said:
The relationship is still symmetrical. You can see in the json output, under "relationships" on the very bottom, that #2387200 still has #2386061 listed as its child. It's just that the site only displays active children, much like the search page does not show deleted posts unless you deliberately search for them.

Good to know, thanks.

grievre said:
The speciestags: metatag doesn't seem to work. No matter what number or range I put next to it, it gives me zero results.

I don't believe that's a meta used by e621 but actually a carry over from the base danborru code.

grievre said:
The speciestags: metatag doesn't seem to work. No matter what number or range I put next to it, it gives me zero results.

Will look into this, it's probably a missing check for it somewhere, or it's named something else.

EDIT:
Looks like count tags always use the "short names" which for species is spec so the correct tag name is spectags: I'll make sure that the documentation lists this.

Updated

Remember when E6 displayed thumbnails and avatars on the 3DS? Good times. New 3DS, latest OS version, L2 Cache enabled, CPU set to 804 MHz. Have tried desktop and mobile versions. Possibility of outdated JavaScript on the 3DS's end. static1 urls work fine. I can only see tags when searching. The rest of the site is operational. In fact, this comment was typed entirely on my 3DS. It's not too big of an inconvenience, but it's slightly annoying.

kaworu said:
My guess would be because #2386061 was flagged at the time (now deleted).

Actually, it wasn't, but I believe your comment has let me find the actual bug. You can see in the moderation history that the post was flagged twice, the first one getting erroneously resolved and the second one coming five days later. I'm pretty sure that, at the time I wrote that comment, the post was not flagged - and it wouldn't have made a difference if it was, as I can assure you flagged-but-not-yet-deleted posts *do* show up in child post lists, having flagged quite a few myself. (This is obviously desirable behaviour, because what if the flag is wrong?)

It seems the site might be coping badly with this particular edge case. Perhaps it saw the flag being marked as "resolved", and incorrectly assumed the resolution had been in favour of deletion?

Anyway, I have an unrelated bug. The pokémon_(species) wiki page has had rather messed up formatting for a while, with sections coming apart from other sections and rogue [/section] tags showing up in the rendered HTML. After a great deal of blind experimentation, I have managed to fix these issues. You can't tell from the diff, but all my changes involved inserting newlines in places where there shouldn't really need to be newlines. In particular, apparently typing .h5 in a section completely breaks the section, unless it is surrounded by newlines on both sides. Similar rules appear to apply to consecutive nested sections, as seen in the unmoored "Generation VII Pokémon" section at the bottom of this old version, except in this case just inserting a newline before the preceding closing [/section] appears to suffice. These rules are baffling and unnecessary, and seem more likely to be the result of DText parsing bugs than any documented behaviour.

corrupt_specturion said:
Remember when E6 displayed thumbnails and avatars on the 3DS? Good times. New 3DS, latest OS version, L2 Cache enabled, CPU set to 804 MHz. Have tried desktop and mobile versions. Possibility of outdated JavaScript on the 3DS's end. static1 urls work fine. I can only see tags when searching. The rest of the site is operational. In fact, this comment was typed entirely on my 3DS. It's not too big of an inconvenience, but it's slightly annoying.

We are not making an effort to support browsers with wildly outdated browser/JS versions anymore. It's a huge time sink. If you turn JS off it should allow you to browse the site. This hasn't worked since March when the whole site was updated.

Updated

kiranoot said:
We are not making an effort to support browsers with wildly outdated browser/JS versions anymore. It's a huge time sink. If you turn JS off it should allow you to browse the site. This hasn't worked since March when the whole site was updated.

I understand completely. I don't think you can turn off JavaScript on the 3DS browser, though, unless I can do it with some obscure Chinese Homebrew that I've never heard of. '~'

An account's blacklist doesn't work when JavaScript is disabled, and there's no indication of any kind that a blacklisted post would be hidden from search results if JavaScript was enabled.

This creates an unnoticed but significant difference in UX between browsing while logged in and browsing while logged out. Specifically, that posts in the default blacklist are removed entirely from search results while logged out, JavaScript enabled or not, but that posts in the account's blacklist aren't while logged in.

Firefox 80 on FreeBSD and Firefox 79 on Android, both with the extension NoScript.

cinnamoncrunch said:
An account's blacklist doesn't work when JavaScript is disabled, and there's no indication of any kind that a blacklisted post would be hidden from search results if JavaScript was enabled.

This creates an unnoticed but significant difference in UX between browsing while logged in and browsing while logged out. Specifically, that posts in the default blacklist are removed entirely from search results while logged out, JavaScript enabled or not, but that posts in the account's blacklist aren't while logged in.

Firefox 80 on FreeBSD and Firefox 79 on Android, both with the extension NoScript.

There are some misconceptions about how the blacklist works here.

Without scripts the blacklist cannot run. It was a choice made to allow the site to work without Javascript, since images are no longer visible until scripts run(prevents flash of unblacklisted content,) while scripting is enabled. This is controlled through use of <noscript> tags and CSS rules. If you enable scripts on the page after it has been loaded without scripts enabled, it will not operate properly. If you require a blacklist, whitelist the domain so that it can properly run scripts and <noscript> tags are not executed. Running both will give you broken results.

As for logged out vs logged in. The default blacklist is both editable without logging in(from the posts menu at the top click "Blacklist"), and also shows what content has been blacklisted below the search box, which can be expanded and turned on and off. The only difference between logged out and logged in blacklist is that logged in blacklist cannot be edited from the menu, and has to be edited from the account page. Both run the same code paths and obtain their information from the same place.

The only content that cannot be viewed without logging in, is adult content of young characters; those posts are filtered out before being sent to the clients. All other content is controlled client side by the blacklist and can be freely toggled in and out of view without reloading the page.

As a footnote, running the site without javascript enabled is fully unsupported. If it works, great, if it's broken, that's more or less to be expected. A cursory effort was made to try to make it so you could view images, but that's it.

Updated

Something weird is happening with the muzzle_growth tag. When I type it into the search bar or some other tag input, the site's autocomplete offers two options: muzzle_growth itself, and a muzzle_growth -> snout_growth alias. Picking muzzle_growth puts in muzzle_growth, and picking the alias replaces it with snout_growth. The muzzle_growth wiki shows it aliased to snout_growth. Additionally, the muzzle_growth listing claims to have 68 posts while snout_growth claims 28, but they return the same results when searched (which is definitely more than 28). I don't see this behavior with other aliased tags, so I'm not sure why this specific one is offering to autocomplete the original tag along with its alias, or why the alias selection shows the wrong count.

Using Pale Moon 28.12.

watsit said:
Something weird is happening with the muzzle_growth tag. When I type it into the search bar or some other tag input, the site's autocomplete offers two options: muzzle_growth itself, and a muzzle_growth -> snout_growth alias. Picking muzzle_growth puts in muzzle_growth, and picking the alias replaces it with snout_growth. The muzzle_growth wiki shows it aliased to snout_growth. Additionally, the muzzle_growth listing claims to have 68 posts while snout_growth claims 28, but they return the same results when searched (which is definitely more than 28). I don't see this behavior with other aliased tags, so I'm not sure why this specific one is offering to autocomplete the original tag along with its alias, or why the alias selection shows the wrong count.

tally_mark shows a similar problem, showing in the autocomplete popup with 41 posts despite being aliased to tally_marks.

watsit said:
Something weird is happening with the muzzle_growth tag. When I type it into the search bar or some other tag input, the site's autocomplete offers two options: muzzle_growth itself, and a muzzle_growth -> snout_growth alias. Picking muzzle_growth puts in muzzle_growth, and picking the alias replaces it with snout_growth. The muzzle_growth wiki shows it aliased to snout_growth. Additionally, the muzzle_growth listing claims to have 68 posts while snout_growth claims 28, but they return the same results when searched (which is definitely more than 28). I don't see this behavior with other aliased tags, so I'm not sure why this specific one is offering to autocomplete the original tag along with its alias, or why the alias selection shows the wrong count.

Using Pale Moon 28.12.

Looks like a simple case of the post count being wrong in the database so it just had to be recounted. If you run across others just make a list of them and poke them to me in a dmail and I'll push through count corrections on them.

igeho said:
Hey, I’m using mobile and webm posts won’t play.

Not sure about other mobile OSs but if you're on iOS (Apple), it never has.

You will need a third-party app to play webm videos, such as PlayerXtreme.