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

Posted under Site Bug Reports & Feature Requests

The protocol on source URLs is automatically "corrected" from http to https

This is a problem on post #2844671
because in Firefox 90.0.1 (64-bit) on Manjaro Linux, all source URLs on this posts lead to an internal page that says:
Error: Secure connection failed

When I manually remove the s from the URL protocol, the pages open without an error.

I created a flag, "inferior of another" and it does not show up in https://e621.net/post_flags?search%5Bcreator_name%5D=AoBird, but it does at https://e621.net/post_flags?commit=Search even though it properly shows me as a creator. It also doesn't shown in the API when searching by creator.

The specific one I'm talking about https://e621.net/post_flags?commit=Search&search%5Bpost_id%5D=2842253

Might be connected to that flag count almost reset when we switched to NG as I already had a couple of hundred flags before that.

anyone else having trouble signing in on mobile? I literally type in the same exact credentials on my desktop and phone one character at a time to make sure i'm not going crazy. both are the exact same but only my desktop logs in while on mobile it says incorrect username/password. I've tried and failed with new passwords/password resets. I did just change my username though, but even my old one doesn't work either.

My blacklist dosent filter avatars anymore? I havent changed anything. I clicked on a post that picked up on 3 things on my blacklisted but only one applied to the post itself and the other two to two avatars in the comment sections. So the site seemed to register avatars, however when I only disabled the tag was in the post itself the avatars still load.

I have tried going back and forth and doing it again and all that.

Updated

iago1 said:
Thumbnails in image description fields haven't worked right in a long time. Instead of showing a thumbnail, they instead show a link with a text like "post #2857290".

For example: https://e621.net/posts/2856374

I could imagine that's deliberate, to avoid having images in the description. Parent/child posts are there to relate posts in a way that show with thumbnails, and there's pools for collecting a series of posts with navigable links. Having additional thumbnails in the description would add clutter for something that should try to be short, so thumb #xxx is replaced with post #xxx to maintain the reference/link just without the thumbnail.

iago1 said:
Thumbnails in image description fields haven't worked right in a long time. Instead of showing a thumbnail, they instead show a link with a text like "post #2857290".

For example: https://e621.net/posts/2856374

This is intentional. Thumbnails are large and introduce clutter in that area. If there is a relationship that is what parent/children are for, or maybe a pool.

It seems the thumbnails for images won't load. Don't know if anyone else is experiencing this.

We are aware of failure to load images. It will be fixed shortly.

Edit: Things should be back again.

taranuka said:
It seems the thumbnails for images won't load. Don't know if anyone else is experiencing this.

It seems the certificate for anything downloadable has expired today, august 1st, it requires renewal.

I propose this CSS is applied to all users:

#wiki-page-body {margin:2em 0 2em 0}

It adds some blank space above and below the content of wiki pages.

The show_or_new wiki page link format doesn't work any more. For example:

https://e621.net/wiki_pages/show_or_new?name=anthro

Leads to a "This wiki page does not exist." message, with a "Posts" section that contains whatever the last four images posted on the site were. Clicking on the "view all" next to posts takes you to the main /posts page.

This affects links posted in the forum (as above), as well as links in the "Preview Final Tags" view. It does not appear to affect the ? links next to tags in the post view, which redirect to the correct (numeric) wiki link.

bitWolfy

Former Staff

wat8548 said:
The show_or_new wiki page link format doesn't work any more. For example:

https://e621.net/wiki_pages/show_or_new?name=anthro

Leads to a "This wiki page does not exist." message, with a "Posts" section that contains whatever the last four images posted on the site were. Clicking on the "view all" next to posts takes you to the main /posts page.

This affects links posted in the forum (as above), as well as links in the "Preview Final Tags" view. It does not appear to affect the ? links next to tags in the post view, which redirect to the correct (numeric) wiki link.

The links in the "preview final tags" are probably just using the wrong format. Not sure why.
The correct format uses the title parameter, like this: https://e621.net/wiki_pages/show_or_new?title=anthro

This issue does not affect normal wiki links using the [[anthro]] format: ex. anthro.

Edit: traced it back, the issue with the "preview final tags" thing is from pull request #290 – it made the uploader form link to the wiki pages instead of search results, but used the wrong format. I made a ticket about it.

Updated

blacklists are STILL broken. my blacklists are formatted the way the site wants them, my blacklists are turned on, yet i STILL see unwanted and blacklisted images appearing in my searches.

bitWolfy

Former Staff

bonk_2025 said:
blacklists are STILL broken. my blacklists are formatted the way the site wants them, my blacklists are turned on, yet i STILL see unwanted and blacklisted images appearing in my searches.

There is STILL nothing wrong with blacklists.
If something is working for literally everyone except for you, chances are, the issue is on your side.

Feel free to DMail me your blacklist, and examples of a posts that it fails to filter out.

It looks like custom anchor text for tag search links is no longer supported, if it ever was.

The DText help page specifies the format {{a list of tags|Some Text}}, followed by an example of what currently renders when you type it: Some Text

Wiki links still work: [[wiki page|Some Text]] Some Text

"insect" is a tag, but insect in the tags redirects to arthropod. It's impossible to search specifically for "insect" unless you directly click on the tag itself, but if you try to look up insect alongside something else then it redirects to arthropod. Please make it so "insect" doesn't automatically link to arthropod pls.

bitWolfy

Former Staff

sutando_powah said:
"insect" is a tag, but insect in the tags redirects to arthropod. It's impossible to search specifically for "insect" unless you directly click on the tag itself, but if you try to look up insect alongside something else then it redirects to arthropod. Please make it so "insect" doesn't automatically link to arthropod pls.

... What? No, it doesn't.
insectoid is aliased to arthropod. Insect implies arthropod - that is, every post that's tagged insect will also be tagged arthropod - but it does not get automatically redirected to it: https://i.imgur.com/P5yi9eJ.png

When a thread contains multiple BURs, voting on one BUR removes the ability to vote on any of the other BURs I've not yet voted on in the thread, until the page is reloaded. Removing my vote also doesn't allow me to recast my vote until the page is reloaded.

Pale Moon 29.3.0

Is the blacklist bugged or is it just not possible to have the blacklist filter posts by whether or not they're favorited? I know you can use "fav:*username*" to only show posts that are favorited by the specified user as well as "-fav:*username*" to hide all posts that are favorited by the user. But trying to setup the blacklist to hide certain posts UNLESS they are favorited (eg. "fox -fav:*username*") doesn't seem to work.

Im not sure if it's not working correctly or if the blacklist function is just unable to check what posts are favorited and by who.

bitWolfy

Former Staff

~keaton said:
Is the blacklist bugged or is it just not possible to have the blacklist filter posts by whether or not they're favorited? I know you can use "fav:*username*" to only show posts that are favorited by the specified user as well as "-fav:*username*" to hide all posts that are favorited by the user. But trying to setup the blacklist to hide certain posts UNLESS they are favorited (eg. "fox -fav:*username*") doesn't seem to work.

Im not sure if it's not working correctly or if the blacklist function is just unable to check what posts are favorited and by who.

You can't use other people's favorites in the blacklist. It's not a bug, just a limitation of the system.
fav:me can be used to mean your own favorites, so fox -fav:me will blacklist all posts with foxes except for the ones you have favorited.

bitwolfy said:
You can't use other people's favorites in the blacklist. It's not a bug, just a limitation of the system.
fav:me can be used to mean your own favorites, so fox -fav:me will blacklist all posts with foxes except for the ones you have favorited.

Didn't know you could use "Me" instead of my whole username, that fixes it. Thanks a bunch. 🙏🏾

lance_armstrong said:
Looks like I can do it, but I also think its existence needs to be justified by actual use first. The e621 upload predates the FurAffinity "source" by several years.

I don't see why that's relevant? The point of the tag is to say "heads up, the only source we know of is not as good as this one".

Also I stumbled upon a post mistagged with avoid_posting: post #2200236

onemoreanonymous said:
I don't see why that's relevant? The point of the tag is to say "heads up, the only source we know of is not as good as this one".

Turns out I can't edit the category. At least for meta.

Bug #1
General tags are listed under 'Artists' section. Go to Artists, change order to 'Post count' and you can see non-artist tags at the top of the list, like duo, blush, fox, sheath.

Bug #2
In the user's about section, words are broken in the middle when wrapping, which makes the text painful to read. For example see bitWolfy or Mairo.
It's because of CSS word-break property that is set to break-all. To fix this it should be removed or set to normal changed to break-word.

Updated

ebea57 said:
Bug #2
In the user's about section, words are broken in the middle when wrapping, which makes the text painful to read. For example see bitWolfy or Mairo.
It's because of CSS word-break property that is set to break-all. To fix this it should be removed or set to normal.

In the meantime, we can fix it ourselves with custom CSS:

.about-section p {word-break: normal}

It actually wasn't great for the long links on my profile, but we can play around with it.

Updated

lance_armstrong said:
It actually wasn't great for the long links on my profile, but we can play around with it.

Yeah. I checked other possible values for word-break and it seems like break-word is the solution for both issues - long links look good and words are not broken in the middle as well. So use break-word instead of normal or break-all.

bitwolfy said:
There is STILL nothing wrong with blacklists.
If something is working for literally everyone except for you, chances are, the issue is on your side.

Feel free to DMail me your blacklist, and examples of a posts that it fails to filter out.

I've been having this same issue though, my blacklist hasn't been working for over a week now. It used to work fine, so I'm not sure what changed.

My blacklist hides posts on the search page as usual, but if I'm going through post by post it doesn't hide posts but loads them as though the blacklist had been disabled. (It isn't, I've toggled that setting multiple times and it has no effect.)
All of my blacklist terms are on their own line so it shouldn't be a formatting issue there, and the blacklisted tags will show up in the sidebar as though they were being flagged properly, it's just that the image or video will load fully regardless. I've tried with different browsers (brave and firefox, on both my tablet and desktop) and it's consistently not hiding posts that should be blacklisted.

bitWolfy

Former Staff

shameheap said:
I've been having this same issue though, my blacklist hasn't been working for over a week now. It used to work fine, so I'm not sure what changed.

My blacklist hides posts on the search page as usual, but if I'm going through post by post it doesn't hide posts but loads them as though the blacklist had been disabled. (It isn't, I've toggled that setting multiple times and it has no effect.)
All of my blacklist terms are on their own line so it shouldn't be a formatting issue there, and the blacklisted tags will show up in the sidebar as though they were being flagged properly, it's just that the image or video will load fully regardless. I've tried with different browsers (brave and firefox, on both my tablet and desktop) and it's consistently not hiding posts that should be blacklisted.

You mean using the "next" and "back" buttons on the post page?
Yeah, you will still see the blacklisted posts using those. The blacklist is processed in your browser, not on the server – the site does not know that the image is blacklisted until the page loads.
The images themselves should be replaced with a white box with "Blacklisted" in black letters on it, though. Do you mean that this does not happen?

The videos don't get replaced with a placeholder though, that's an actual issue that has gone unfixed for a while now.

bitwolfy said:
You mean using the "next" and "back" buttons on the post page?
Yeah, you will still see the blacklisted posts using those. The blacklist is processed in your browser, not on the server – the site does not know that the image is blacklisted until the page loads.
The images themselves should be replaced with a white box with "Blacklisted" in black letters on it, though. Do you mean that this does not happen?

The videos don't get replaced with a placeholder though, that's an actual issue that has gone unfixed for a while now.

Yes, sorry, I meant the white box doesn't appear. I think I have primarily noticed this with videos so that would explain it. Is there any chance that issue will get fixed?

bitWolfy

Former Staff

shameheap said:
Yes, sorry, I meant the white box doesn't appear. I think I have primarily noticed this with videos so that would explain it. Is there any chance that issue will get fixed?

Sorry, I doubt that there is an ETA on the issue with videos not being hidden.

Updated

It was previously reported that Comments on was broken and only shows the recent comments. Someone mentioned there was a limit of 300 forum #313328

This comment from yesterday comment #5930189 still appeared on "Comments on" and today it disappeared while the oldest comment at the moment is from two days ago comment #5928467.

Was that a bug or "Comments on" only shows the comments on the previous 300 uploads?

Apparently the top part of the upload page when clicked on somewhere will hide some sections to look more compact on top of reorganizing the inputted tags, but there is no visual indication to show that this is the case.

Updated

Tom Fishbach -> It needs two c's in his name (From DNP list).

https://twokinds.fandom.com/wiki/Tom_Fischbach

shameheap said:
I've been having this same issue though, my blacklist hasn't been working for over a week now. It used to work fine, so I'm not sure what changed.

My blacklist hides posts on the search page as usual, but if I'm going through post by post it doesn't hide posts but loads them as though the blacklist had been disabled. (It isn't, I've toggled that setting multiple times and it has no effect.)
All of my blacklist terms are on their own line so it shouldn't be a formatting issue there, and the blacklisted tags will show up in the sidebar as though they were being flagged properly, it's just that the image or video will load fully regardless. I've tried with different browsers (brave and firefox, on both my tablet and desktop) and it's consistently not hiding posts that should be blacklisted.

Hmm, blacklist works by editing the DOM/rendered source, right? I guess a bug in the JS showed up (or browsers[addons?] messed with it). The fact that it happens on multiple devices and browsers though...

Updated

New bug popped up with Firefox today, despite no updates. Literally in the middle of my session browsing the site. Sudden;y, holding CTRL and clicking no longer opens links in a new tab. Instead I get a red ERROR: banner with a close button. Nothing else. Tested, and no problems with Chrome, or any other websites.

bitWolfy

Former Staff

drax99 said:
New bug popped up with Firefox today, despite no updates. Literally in the middle of my session browsing the site. Sudden;y, holding CTRL and clicking no longer opens links in a new tab. Instead I get a red ERROR: banner with a close button. Nothing else. Tested, and no problems with Chrome, or any other websites.

Just CTRL-clicking? Normal clicking does not do that?
You should check that the "Mode" dropdown in the sidebar is set to "View.

bitwolfy said:
Just CTRL-clicking? Normal clicking does not do that?
You should check that the "Mode" dropdown in the sidebar is set to "View.

Thanks, that worked. never even noticed that setting

Just ran into a weird glitch with the Favorite system.

post #2921064

This shows up in my Favorites, but when I view the image it has a green +favorite button.
When I click on that button esix thinks for a moment and then does a red status-message stating: Error: You have already favorited this post

This means
a) The display is incorrect
b) I can't actually un-favorite this image if I wanted to

This image had a couple different variants initially uploaded if memory serves. I think I favorited one of the other variants initially.

bitWolfy

Former Staff

tredfg543 said:
Just ran into a weird glitch with the Favorite system.

post #2921064

This shows up in my Favorites, but when I view the image it has a green +favorite button.
When I click on that button esix thinks for a moment and then does a red status-message stating: Error: You have already favorited this post

This means
a) The display is incorrect
b) I can't actually un-favorite this image if I wanted to

This image had a couple different variants initially uploaded if memory serves. I think I favorited one of the other variants initially.

That happens to people occasionally.

I'm not entirely sure why, but here's how you fix it:
1. Go to id:2921064
2. Switch "Mode" in the sidebar to "Unfavorite"
3. Click the post thumbnail
4. Switch "Mode" back to "View"
5. The post should now be unfavorited
After you do that, you can favorite it again normally if you want.

bitwolfy said:
That happens to people occasionally.

I'm not entirely sure why, but here's how you fix it:
..........

That cleaned it up, thanks!

I'm pretty sure the bug is going to be a weird edge case regarding posts being Flagged and/or Removed. I know Favorite state usually migrates from the removed post to the surviving post, but there's a gremlin in that code somewhere, I think. The post in question I think initially had two or three different versions, which ultimate condensed down to the one version on the site now.

Attempting to use the m or f tags appears to yield no results. Historically, they would translate into the male and female tags respectively. Is this deliberate?

bitWolfy

Former Staff

weeboon said:
Attempting to use the m or f tags appears to yield no results. Historically, they would translate into the male and female tags respectively. Is this deliberate?

Yes. All one-letter tags are invalid.

They are rather ambiguous. What might seem obvious to you might not be so to someone else.
Besides, if this was a thing, then for the sake of fairness we would probably need to have one-letter aliases for the other gender tags as well (gynomorph, andromorph, herm, maleherm), which is even more impractical.

Updated

bitwolfy said:
Yes. All one-letter tags are invalid.

They are rather ambiguous. What might seem obvious to you might not be so to someone else.
Besides, if this was a thing, then for the sake of fairness we would probably need to have one-letter aliases for the other gender tags as well (gynomorph, andromorph, herm, maleherm), which is even more impractical.

That’s true, but they don’t appear like that in the tag list?

m/m still works, but technically isn’t 1 letter.

bitwolfy said:
Yes. All one-letter tags are invalid.

They are rather ambiguous. What might seem obvious to you might not be so to someone else.
Besides, if this was a thing, then for the sake of fairness we would probably need to have one-letter aliases for the other gender tags as well (gynomorph, andromorph, herm, maleherm), which is even more impractical.

This worked like, 2 days ago. Why change it only now? And how are m and f ambiguous?

There's no good way to link to entries in the Mod Actions history, but it appears that all of the single-letter tags had their existing aliases removed and their categories changed to Invalid at 1:30 this morning (or ~16 hours ago as of this post). You can also see this by looking at the tag category history.

The Mod Actions page also lists what the old aliases were, which was invalid_tag for all but m and f, which were indeed aliased as weeboon describes.

It strikes me that some kind of "alias history" for tags would be quite useful in cases like this. Even searching for deleted aliases doesn't return any relevant results.

EDIT: I believe this is the relevant BUR. I'm pretty sure deleted aliases being fully deleted and not searchable is a bug.

bitWolfy

Former Staff

wat8548 said:
For some reason, the bull_horn tag claims to have 0 posts, despite having at least 4 pages' worth.

The original tag was bull_horns, which got aliased to bull_horn a few days ago.
The post counter just never caught up for some reason. Both should be fixed now.

aobird said:
I created a flag, "inferior of another" and it does not show up in https://e621.net/post_flags?search%5Bcreator_name%5D=AoBird, but it does at https://e621.net/post_flags?commit=Search even though it properly shows me as a creator. It also doesn't shown in the API when searching by creator.

The specific one I'm talking about https://e621.net/post_flags?commit=Search&search%5Bpost_id%5D=2842253

Might be connected to that flag count almost reset when we switched to NG as I already had a couple of hundred flags before that.

This took a while but should be fixed now.

Not sure if it's just me or not, but I'm having a issue with no images being displayed. Posts, favorites or specific links are all showing as either blank or placeholder. Is this a bug or has something gone wrong on my end?

Same here, I can't see any picture; but strangely I can when click on original size, someone knows why happen this?

thunderkitten said:
Not sure if it's just me or not, but I'm having a issue with no images being displayed. Posts, favorites or specific links are all showing as either blank or placeholder. Is this a bug or has something gone wrong on my end?

I'm having the same problem, I don't know what browser the others having this problem are having but I'm using Puffin Web Browser on iOS. I can still access the site on my laptop however.

The site recently had to change the way javascript is compiled. It might have something to do with that.
If anyone else is experiencing this issue please write which browser you are using, preferably also the version if you know that and on which OS you are.

iOS 9, Safari, echoing the same issues. No images shown for me unless I press the download button.
Yeah, I know iOS 9 is ungodly old, but everything's worked fine for me until now, and it looks like others are having the same issue, so I don't quite think it's a "my device is too old" scenario.

noire_vala said:
I'm having the same problem, I don't know what browser the others having this problem are having but I'm using Puffin Web Browser on iOS. I can still access the site on my laptop however.

Puffin Browser iOS 14.7.1

I'll have to try and figure out what browser support level iOS 9 Safari would be at. Right now the support level is somewhat dynamic as of the change that was forced on me. It targets browser support for all browsers where worldwide usage is above 0.25%. I don't see a reason to exclude anyone since we're not doing anything particularly fancy and targeting older support shouldn't be too hard, but I don't know how the new compiler toolchain will play ball. It doesn't look like it supports targeting full ES5 like the old one was set at.

On the other hand, yeeesh, some of this stuff is truly ancient.

If anyone can give an error message from a console or something that would be wonderful, since then I can do my best to target polyfill support around whatever is currently breaking it. It sounds like this is fully mobile, so I don't even know if that is possible.

I'm unable to see even a thumbnail of any post on my old iPad running 9.3.5 iOS I think uhhhh, it works fine on my newer I phone device and I restarted the app and device and logged out and in. Not even a list of blacklisted tags shows as no thumbnail previews appear to be even loading. 3: ah yes and I'm using safari cause this thing doesn't support chrome or Firefox which is perplexing. It's like, old but it can't be that old. Edit: it's an eleven year old iPad :(

Updated

Yeah, looking into it, apparently accessing console is nigh impossible - even on a jailbroken device. Seems like Apple's intended solution for devs is to hook your iPad up to a Mac and use Safari on the PC to debug it... But I don't have a Mac, so that's infeasible for me.

Really hope this gets squared away, though. I'm surprised by the fact there are actually other iOS 9 users here who could use this fix, and the fact even recent iOS browsers seem to be affected gives me a bit of hope we won't be left by the wayside. I definitely ain't able to just buy a new iPad after all.

Guessing out my ass here, as I'm not savvy in web development, but would it be possible to just use the old JavaScript for older / affected user agents?

I have deployed a test version that tries to target older browsers to https://e926.net/ if you are able to see thumbnails there but are not able to see them on the main site, please let me know. If you are still unable to see thumbnails on e926 then I will have to investigate further.

I am unfortunately unable to test this myself as I don't own any devices this old that already don't support loading the site at all.