I have found a new bug. In the _Search for Myself in Comments_ link, it no longer shows where people have replied to my comments. It does show, however, people saying "cow" then "fire" in the same comment.

mononatriumglutamat said:
Do you still recommend creating a separate bug thread for each bug? I would, because new bug reports would drown in the discussion of existing ones, if we just throw them in here.
I'm having trouble with the /posts.json endpoint ignoring the "id" parameter and /posts.xml just plain 403-ing on me.

Here's a thread I made before I saw this general bug report thread:
https://e621.net/forum_topics/25740

check the API page and read through this discussion. you no longer pass 'id' parameter, and only json API is a thing, at least for now.

777edge777 said:
The sorting method "date:" gives all posts posted exactly that long ago rather than all posts since then.

where did you get an idea that date:X is a sorting method? it's not. it never was.

pervynagaking said:
I don't know if it's been reported already, but searching "user:me" or "fav:me" returns nothing

really?
i get two results from fav:me

I get two results

Me too. Weird.

Something is weird with fav: anyway. Shows a warning message that fav: searches are unordered, BUT the favs are shown in the order I favorited them in (newest first), BUT the next/prev buttons move through favorites in a different order.

Maybe that's what was really meant by the warning message, but if so, I certainly don't find it obvious that "Searching favorites does not preserve the order they were added in." would mean that.

(this might have a similar cause as the 'visible set ordering vs set prev/next ordering' bug someone recently reported..)

savageorange said:

bipface said:
really?
i get two results from fav:me

Me too. Weird.

that's not the weird part, since there is a user named 'me', and those are his favorites, so it's working as intended

cloakedthief said:
http://webmshare.com/play/EGJBg
Here ya go.

when i fed it into ffmpeg it gave me the following warning:

[matroska,webm @ 000000000016fd40] Element at 0x90c3c ending at 0x90c4d exceeds
containing master element ending at 0x90c30

which definitely sounds like the kind of encoding error that could interfere with the detected length (though ffmpeg reported the correct length).
i losslessly reconstructed the webm with the following command: ffmpeg -i input.webm -c:v copy -c:a copy output.webm
and the error seems to have disappeared.
here's the result: https://webmshare.com/z0L0W
try uploading that instead.

e621.net/iqdb_queries.json doesn't seem to accept multipart form with file with it, always returns an error.
The only thing that works is e621.net/iqdb_queries.json?url= as long it's not e621 address. otherwise it errors out as well.

https://e621.net/forum_topics/25924

bipface said:

savageorange said:
Me too. Weird.

that's not the weird part, since there is a user named 'me', and those are his favorites, so it's working as intended

I guessed that was the case, but the short-hand worked before, so I'd suggest the search cheatsheet be updated to exclude the use of "me". And I'll have to keep my name in the clipboard. Thanks.

In the last 24 hours, e621 has stopped working with my VPN. I use Private Internet Access (PIA) and had to disable it to be able to post in the forums, send blips, use private messaging, etc.

When PIA is active, clicking Submit on any of these features gives me an error stating "An Unexpected Error Occurred. Log ID: (none)."

When I log out of PIA, these features work normally.

Posts and thumbnails are invisible and unlickable
I am not the only one with this problem
https://e621.net/forum_topics/25760
https://e621.net/forum_topics/25757

I am using the silk browser if that helps any.

asssalad said:
Posts and thumbnails will not register

what do you mean by 'will not register' ?
are they invisible ?
are they unclickable ?

Use of the order:score or any other image ordering syntax completely removes the ability to use keyboard shortcuts to navigate the site.

yiffhound098 said:
Use of the order:score or any other image ordering syntax completely removes the ability to use keyboard shortcuts to navigate the site.

can't reproduce; i went to /posts?tags=order%3Ascore, pressed d and it took me to page 2.
what browser+version are you using?

bipface said:
when i fed it into ffmpeg it gave me the following warning:

[matroska,webm @ 000000000016fd40] Element at 0x90c3c ending at 0x90c4d exceeds
containing master element ending at 0x90c30

which definitely sounds like the kind of encoding error that could interfere with the detected length (though ffmpeg reported the correct length).
i losslessly reconstructed the webm with the following command: ffmpeg -i input.webm -c:v copy -c:a copy output.webm
and the error seems to have disappeared.
here's the result: https://webmshare.com/z0L0W
try uploading that instead.

That seems to have worked! Thank you.

Wording when falgging:

When flagging my own posts I noticed that it says to provide the post #

However, it says "inferior post #"

Shouldn't it be "superior post #"?

yiffhound098 said:
Use of the order:score or any other image ordering syntax completely removes the ability to use keyboard shortcuts to navigate the site.

Quick navigation while viewing posts relies on being able to quickly find the next and previous posts, this uses before/after id sorting, which means it doesn't work with custom sorting modes. I wasn't confident in the feature scaling well with custom sorting modes with ongoing site growth so didn't offer them.

Tags only allows ASCII characters now.

https://e621.net/post_sets/<Set_ID>/update_posts.json returns html response

When uploading pixiv images, e6 automatically adds old pixiv formatting for source https://www.pixiv.net/member_illust.php?mode=medium&illust_id=ID instead of new https://www.pixiv.net/en/artworks/ID

bipface said:
can't reproduce; i went to /posts?tags=order%3Ascore, pressed d and it took me to page 2.
what browser+version are you using?

kiranoot said:
Quick navigation while viewing posts relies on being able to quickly find the next and previous posts, this uses before/after id sorting, which means it doesn't work with custom sorting modes. I wasn't confident in the feature scaling well with custom sorting modes with ongoing side growth so didn't offer them.

It was the post navigation shortcuts rather than the search page navigation shortcuts that were not showing up, KiraNoot nailed it. I didn't know if it was a caching issue or an implementation limitation, good to know it's a limitation and not a bug. Would be cool to have in the future or another way to view full size posts in a slideslow-esq format. Thank you for the clarification!

The blacklisted tags all appear in a list under the search and mode bars, instead of being hidden in a collapsed list. Even worse: the blacklist occasionally just disables itself and I have to click 're-enable all'

kemonophonic said:
The news bar keeps reappearing every time I load a page even after clicking Dismiss.

Having the same issue.

this doesn't seem to have been mentioned since the initial release of this version of the site, but having to scroll down and press the submit button rather than being able to just hit enter to submit a tag edit is still really annoying.

darryus said:
this doesn't seem to have been mentioned since the initial release of this version of the site, but having to scroll down and press the submit button rather than being able to just hit enter to submit a tag edit is still really annoying.

I noticed this too, it's especially odd as enter is listed as a shortcut to submit tag changes on the keyboard shortcuts help page.

Pressing reply in the comments tab on a post just takes me to the top and does nothing else currently.

Pressing show tags dumps you at the top as well but does toggle the tags if I scroll back down. Would still prefer if you just showed me the tags

In flashes, if you hit "a" you go to the previous post instead of whatever "a" might do in the flash.

example flash:

https://e621.net/posts/856861?q=dragon_%28shrek%29

camkitty said:
Pressing reply in the comments tab on a post just takes me to the top and does nothing else currently.

+1, I can verify this. Happens on all comments I tried it on.

Not sure if this is already mentioned somewhere but using the search function "date:4_days_ago" or any different form of that no longer shows everything up until four days ago but specifically from the day that was four days ago. So instead of showing the same thing when searching for "date:week" and "date:7_days_ago" it gives different results.

Having trouble properly adding posts to a pool even though it's not even close to a thousand entries.

https://e621.net/posts/2187602

The post says that it's in the pool, but you can't go the previous or next page, and when I check the pool directly, they're not listed there, either.

The page doesn't warn you when adding an image to a set in which it already belongs. The notification says "added post to set". It used to say something like "error, post already in set".

I tried to create an alias request for gaslightdog with gaslight, and even after making the wikis identical, it still wont let me make the request. It tells me there are conflicting changes.

There is a bug I tried posting a image that no one else posted on here before all tags were correct everything was fine but when I pressed upload it said duplicate pic even tho when I clicked the duplicate pic link it was different image

Uh, I had Incest blacklisted, and whent I checked this post.

https://e621.net/posts/2186784?q=sparrow_%28artist%29#

I noticed that somehow the incest tag wasn't in my blacklist list, but, I don't remember ever removing that tag.

And If I did, I doubt It.

Edit: Appearently I had incest [lore] blacklisted and not "incest" which is weird because I don't remember disabling that.

james0704 said:
but when I pressed upload it said duplicate pic even tho when I clicked the duplicate pic link it was different image

you could start by actually showing us those pictures
it's not really the kind of issue that can be diagnosed by imagination alone

An option to disable aliases showing up in auto-completion would be nice. It's potentially a nice feature, I guess, but it for me it's getting in the way more than anything.

darryus said:
An option to disable aliases showing up in auto-completion would be nice. It's potentially a nice feature, I guess, but it for me it's getting in the way more than anything.

settings → advanced → custom css:
.autocomplete-antecedent, .autocomplete-arrow {display : none !important;}

Attempting to upvote your own comment gives you an error message at the top of the screen that reads:

.

I'd imagine there's supposed to be an actual error message there.

Something must of changed in the content security policy for scripts, my userscripts didn't work until I set a custom CSP to script-src 'self' 'unsafe-inline' with Laboratory by Mozilla.

bipface said:
settings → advanced → custom css:
.autocomplete-antecedent, .autocomplete-arrow {display : none !important;}

that dosn't remove the entries from the list, it just makes it so you don't see what's being aliased to the thing showing up on the list.

for example starting to type "fem" into the tag field/search bar still shows "genitals, orgasm, masturbation, gynomorph, and girly", and when typing "feral" or "anthro" the list is filled to the brim with completely useless tags, when typing colors "black", "yellow", etc. the background tags are almost all pushed completely off the list now. I'd like the option to not have these items show up at all since they tend to push more useful tags down or off the list.

The autocomplete function was really cool and was almost as useful as TinyAlias was for editing and this change kinda just made almost pointless.

it was brought to my attention that my character tag https://e621.net/posts?tags=lucy_%28%E1%BC%A9%CE%BC%CE%AD%CF%81%CE%B1%29 doesn't seem to be displaying any images?

darryus said:
for example starting to type "fem" into the tag field/search bar still shows "genitals, orgasm, masturbation, gynomorph, and girly", and when typing "feral" or "anthro" the list is filled to the brim with completely useless tags, when typing colors "black", "yellow", etc. the background tags are almost all pushed completely off the list now. I'd like the option to not have these items show up at all since they tend to push more useful tags down or off the list.

i see what you mean now; the problem isn't exclusive to e621: https://imgur.com/6diUHbg
you wouldn't expect mei and touko to be popping up at the same level as female_orgasm for that search; perhaps alias matches should have half the precedence of direct matches.

i'd suggest making an issue of it on danbooru: https://github.com/danbooru/danbooru/issues

If you search for a nonexistent user's favorites, the site should return no posts rather than ignoring the fav: tag.

When you attempt to vote on a comment that you had already voted on prior to the change in how the system tracks up/down votes, the resulting error either says "." or says the last notification pop-up you've seen (for example "Added post to set").

Filtering searches by post comment number doesn't work. I try and search using comments:>0 and I'm not given any results.

benevorelent said:
Filtering searches by post comment number doesn't work. I try and search using comments:>0 and I'm not given any results.

try comment_count:>0 or commenter:any

Pictures won't show up and I don't know why.

Scripts are not working

New alias and implication requests get posted mostly in General forum section instead of Tag Alias and Implication Suggestions. Not sure if it matters which method is used to submit them.

millcore said:
Post the bugs you've found here please, and 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 spot.

Blacklist doesn’t work. I keep seeing “My Little Pony” sometimes along with that abhorrent Arthur series porn.

I'm getting logged out, like, every couple of days, despite checking "remember me." Getting SUPER annoying. Not exactly sure if this is a bug, but it's certainly an unwelcome change, and I haven't seen it documented anywhere.

taufox said:
I'm getting logged out, like, every couple of days, despite checking "remember me." Getting SUPER annoying. Not exactly sure if this is a bug, but it's certainly an unwelcome change, and I haven't seen it documented anywhere.

I'm getting this too every few days. Didn't happen much on the original site.

May have already been reported, but:

Clicking 'Show tags' in the Comments listing always goes to page top

To clarify: I mean the general index of comments accessible via the Comments link in the top bar, not 'comments within a /post/show/* page. And 'show tags' does *work* -- the tags appear -- it's just that it also jumps to the top of the page, which is awkward.

(I suspect it's supposed to jump back to an anchor defined for that particular comment entry, but the anchor isn't actually defined? Something like that)

Platform info: Firefox 73 (with some addons), Arch Linux x86_64.

savageorange said:
May have already been reported, but:

Clicking 'Show tags' in the Comments listing always goes to page top

To clarify: I mean the general index of comments accessible via the Comments link in the top bar, not 'comments within a /post/show/* page. And 'show tags' does *work* -- the tags appear -- it's just that it also jumps to the top of the page, which is awkward.

(I suspect it's supposed to jump back to an anchor defined for that particular comment entry, but the anchor isn't actually defined? Something like that)

Platform info: Firefox 73 (with some addons), Arch Linux x86_64.

ah, yes the problem is the 'show tags' link has href='#', which is a hack to make it show the hand cursor when you hover over it.
it needs a .preventDefault() in the event handler code, or remove the href and use CSS for the cursor.

for reference, Danbooru doesn't have the 'show tags' link at all; the tags are always visible

bipface said:
for reference, Danbooru doesn't have the 'show tags' link at all; the tags are always visible

Much more preferred, and how it was before IIRC

I just found something absolutely annoying that I'd like to you guys to check out to see what's going on.

I have two queries:
1st - order:favcount date:4_days_ago favcount:>=400
2nd - order:favcount date:5_days_ago favcount:>=400

The first one goes OK but there's a problem with the second one, the results from the first query should be included in this one since I'm setting an older date but they're not, they're two completely different sets of pics.

Upload page and all help pages are missing document title. In code it's just <title></title>.

I know it's a minor issue, but a bit annoying when you have opened multiple tabs and can't tell which is which.

Also, all links on upload page should open in a new tab to prevent loss of entered data in fields when clicked. This should be obvious.

harleycs said:
I just found something absolutely annoying that I'd like to you guys to check out to see what's going on.

I have two queries:
1st - order:favcount date:4_days_ago favcount:>=400
2nd - order:favcount date:5_days_ago favcount:>=400

The first one goes OK but there's a problem with the second one, the results from the first query should be included in this one since I'm setting an older date but they're not, they're two completely different sets of pics.

Yeah, this one has been reported.
ago syntax is broken in this specific way:
4_days_ago should mean 'everything from 4 days ago until now'
but actually it means 'everything posted 4 days ago (and not later)'.

Range syntax doesn't seem to work to fix this either.

There might be a way to do what you want with some new query syntax, but I haven't seen any genuine, semi-complete documentation of the new syntax yet.

harleycs said:
I just found something absolutely annoying that I'd like to you guys to check out to see what's going on.

I have two queries:
1st - order:favcount date:4_days_ago favcount:>=400
2nd - order:favcount date:5_days_ago favcount:>=400

is this better?
order:favcount age:..4days favcount:>=400
order:favcount age:..5days favcount:>=400

webm appears to both be and not be a tag simultaneously. when viewing a post it's in the tag list but when looking at the wiki or searching for it it's aliased to animated.

also custom text for search links dosn't work right {{webm|searching for it}} show's like this searching for it when it should show like this, searching for it

I see no images anywhere still.
I saw some other replies trying to find the setting that is messing up, but I still can't see any image at all.
All avatars are replaced by a white square with black words that read “IMAGE PLACEHOLDER”
This is maddenning. The only way I can get to see any picture is tapping on the “Random” button and then, once in a post (on which no image at all is displayed still), tap on the “Download” option.

(Edit after reading some more replies.)

I'm using the latest version of Opera Mini for Android 4.4.2 and with JavaScript enabled. Device: Huawei CHC-U03

angievee said:
Android 4.4.2

good lord; what device are you using ?
is there any way to update android on it ?

The following metatag searches are currently not working correctly:

date:month..year - No relative terms (ex: day, week, month, etc) currently return results for this. Absolute dates do work.
comments:## - No value in place of ## will return results.
speciestags:## - No value in place of ## will return results.
date:decade - Returns results from ten or more years ago, instead of from the last ten years.
source:example.com - I'm not sure if this is a bug, but this only returns posts with a source field starting with "example.com", not posts with a source field simply containing it.
notes:whatever - No word or string in place of "whatever" currently returns results.
delreason:whatever - No word or string in place of "whatever" currently returns results.
hideanon:true/false - Both currently return all posts.
hidegoogle:true/false - I don't know what is hidden from Google crawling, but if something is supposed to be hidden, both of these still return all posts.
order:desclength - Both this and the _asc variant currently return all posts in the default order.
order:comments - Both this and the _asc variant currently return all posts in the default order.

Side notes:
- I think the documentation for the ago syntax could be clarified. Ex: it currently seems to say that date:5_weeks_ago will return posts that were posted within the last 5 weeks, but it actually returns posts from whichever day was exactly 5_weeks_ago.
- On the cheatsheet, "notelocked:true" has an extra colon in it.

metalforever666 said:
Blacklisting doesn't seem to work for me. I'm using Mozilla Firefox.

I'm having the same issue on Chrome mobile and it's ever since the new update. Blacklisting isn't working on multiple posts.

@metalforever666:

More information needed.
What version of firefox, what OS, what hardware platform?

Personally I can verify that blacklisting works on : FF 74, Arch Linux, x86_64, normal desktop PC.

@zinczombie
Same; more info needed:

• version of chrome
• OS ( I presume 'Android', but specific version number of Android has also been shown to be relevant)
• hardware platform

Some people have reported a problem with Chrome, other Chrome users have no problem. In the case of mobile you might need to consult the Apps manager in order to find out what version you are running.

You also say "Isn't working on multiple posts". Then do you mean to imply that it is working on some posts? This is an important distinction, since so far we've only had people reporting 'works fine' or 'doesn't work at all'.

komuros said:
The following metatag searches are currently not working correctly:

date:month..year - No relative terms (ex: day, week, month, etc) currently return results for this. Absolute dates do work.
[..]
date:decade - Returns results from ten or more years ago, instead of from the last ten years.
[..]

Side notes:
- I think the documentation for the ago syntax could be clarified. Ex: it currently seems to say that date:5_weeks_ago will return posts that were posted within the last 5 weeks, but it actually returns posts from whichever day was exactly 5_weeks_ago.

See bipface's post above; the age: metatag seems to be the new way to do this (but yeah, last I checked it wasn't documented)

I tried to reformulate your queries; I inserted a tag in order to reduce the number of results to <750 pages.
(base # of pages for intersex is 377 at my configured page size)

• age:1month..1year intersex returns results from the last year, excluding the newest ~29? days. Number seems to be REQUIRED.
• age:<10years intersex returns results from the last decade. 'decade' doesn't appear to have any effect as a query term
• age:<5weeks intersex -- results from the last 5 weeks

bipface said:
good lord; what device are you using ?
is there any way to update android on it ?

Not that I know of, and trying to update always ends up with a phone with no OS to launch.

Huawei CHC-U03

angievee said:
Huawei CHC-U03

i see… that does limit your options,
however, since that phone does at least claim to have a modern CPU, it would be worth seeing if you can install Firefox or Chrome.

unfortunately diagnosing the site on opera mini is hard to justify; the browser isn't actively developed; there's not much up-to-date information about debugging it; and also this:

if you can find a way to disable this feature, i'd suggest trying that as well

Having a strange issue after the site update regarding favorites. Not sure if this is a bug, but I thought I would post it here anyways.

In the old site, searching fav:[username] would be the same as going to your account, my favourites.

After the update, it seems that searching fav:[username] sorts results by the date the post was uploaded. But navigating to account, my favourites sorts posts by when the posts were favourited.

I want fav:[username] to show up by when the user favourited the post, but I could not find any setting to change that. Is there a tag I can use to change this functionality that I am just missing?

ws32 said:
Having a strange issue after the site update regarding favorites. Not sure if this is a bug, but I thought I would post it here anyways.

In the old site, searching fav:[username] would be the same as going to your account, my favourites.

After the update, it seems that searching fav:[username] sorts results by the date the post was uploaded. But navigating to account, my favourites sorts posts by when the posts were favourited.

I want fav:[username] to show up by when the user favourited the post, but I could not find any setting to change that. Is there a tag I can use to change this functionality that I am just missing?

you should be able to search ordfav:362723 to get that ordering
but it's not working for me, i have no idea why

the code is right there
https://github.com/zwagoth/e621ng/blob/7d928d1fc1dcb732d71edfb7d9297bee0fd10506/app/logical/post_query_builder.rb#L448

bipface said:
you should be able to search ordfav:362723 to get that ordering
but it's not working for me, i have no idea why

the code is right there
https://github.com/zwagoth/e621ng/blob/7d928d1fc1dcb732d71edfb7d9297bee0fd10506/app/logical/post_query_builder.rb#L448

The site doesn't use SQL for search anymore, and elasticsearch doesn't contain enough information(or natively support a way to include enough metadata) to order posts by arbitrary metadata. The favorites page specifically asks for posts a different way to get them in the order that they were added in.

So as of right now, there is no such thing as "search" and "preserve external order information" so it applies to sets, pools, favorites, etc.

There are some potential workarounds that people have floated me, but I haven't had time to look into and test them. Still working on getting themes set up and wrangled a bit.

"https://e621.net/iqdb_queries.json" returns HTTP#500 "An unexpected error occurred." for queries that have no results while "https://e621.net/iqdb_queries" results in correct "No similar posts found." message.

jack'lul said:
"https://e621.net/iqdb_queries.json" returns HTTP#500 "An unexpected error occurred." for queries that have no results while "https://e621.net/iqdb_queries" results in correct "No similar posts found." message.

This endpoint currently does not support alternative response formatting very well. The whole thing was hacked in and reworked close to release to get it to work as a proxy for the backend, which differs significantly from the base danbooru version(at least at the time, it looks like they may have reworked theirs too since then.)

bipface said:
i see… that does limit your options,
however, since that phone does at least claim to have a modern CPU, it would be worth seeing if you can install Firefox or Chrome.

unfortunately diagnosing the site on opera mini is hard to justify; the browser isn't actively developed; there's not much up-to-date information about debugging it; and also this:

(wikipedia)

Opera Mini requests web pages through Opera Software's compression proxy server. The compression server processes and compresses requested web pages before sending them to the mobile phone. The pre-processing increases compatibility with web pages not designed for mobile phones. However, interactive sites which depend upon the device processing JavaScript do not work properly.

if you can find a way to disable this feature, i'd suggest trying that as well

Yeah, that's Opera Mini's main attractive: It saves you data downloaded from the web. Pretty uselful if you're browsing with mobile data instead of WiFi. Thing is that the developers were aware of the incompatibilities since, like, five years ago, so they added the option to enable and disable such compression. I tried with both enabled and disabled and I still can't see any pictures.

Nonetheless, thanks for your help, I'll go check Firefox as you suggested.

kiranoot said:
elasticsearch

ah, say no more

though, i'm impressed to see that you've already managed to squeeze a lot more functionality out of it than… a certain other Lucene-based booru ¬_¬