Topic: (OLD) The Bug Report Thread

Posted under Site Bug Reports & Feature Requests

This topic has been locked.

Butterscotch said:
https://e621.net/forum/show/86981

Kinda wish they would find a way to fix this (yes, I know it was manually turned off by Varka). Not having a readily accessible tag history page for images and users is a pain in the dick.

Updated by anonymous

Char said:
It's my understanding that this section of the site has been temporarily disabled due to it causing performance issues server-side. I guess this is just how Varka decided to disable it. :P

Was gonna report this but people seem aware.

*shrug*

Updated by anonymous

So I try to go to any other page of the search and get a 404.

Updated by anonymous

corgi_bread said:
Kinda wish they would find a way to fix this (yes, I know it was manually turned off by Varka). Not having a readily accessible tag history page for images and users is a pain in the dick.

Agreed. I was trying to check out a tagging issue around the "flare" "character:flare" and "flare_(character)" tags earlier, and I can't view tag history to see whether I've got the right picture... it's aggravating.

Updated by anonymous

Sorry for not dipping into this thread earlier, I derped and didn't look in the forums. >_<

tag history should now be working like a champ; I did have to disable searching beyond the first page though as a web crawler was going through each and every link and bringing the site to its knees from this one poorly optimized page. Lemme know if I do actually need to find a solution to allow more than the first page to be accessible or if it doesn't matter.

Updated by anonymous

Varka said:
Sorry for not dipping into this thread earlier, I derped and didn't look in the forums. >_<

tag history should now be working like a champ; I did have to disable searching beyond the first page though as a web crawler was going through each and every link and bringing the site to its knees from this one poorly optimized page. Lemme know if I do actually need to find a solution to allow more than the first page to be accessible or if it doesn't matter.

I'd say just the main page. <meta> description tags should be enough.... imo

Edit: Referring to each post page and disable tag history for bots/crawlers

Updated by anonymous

Varka said:
Sorry for not dipping into this thread earlier, I derped and didn't look in the forums. >_<

tag history should now be working like a champ; I did have to disable searching beyond the first page though as a web crawler was going through each and every link and bringing the site to its knees from this one poorly optimized page. Lemme know if I do actually need to find a solution to allow more than the first page to be accessible or if it doesn't matter.

Not a problem for an image's tagging history, but user tagging history needs more than 1st page.
Couple reasons I've used in the past.
1: I check my previous edits to see if someone un-did a fix I did previously.

2: Finding multiple examples of a person's bad tagging so they can be warned/punished for their repeated bad tagging, frequently I've run into bad taggers that edit the same image 3, 4, and more times in a row, which fills a single page very quickly.
Some people fill multiple pages in a day, and trying to find their bad tags to use as an example won't be possible in a single page.

Updated by anonymous

mrnotsosafeforwork said:
blacklist does not work for profile pics, that is all

Seems to be working for me.

Updated by anonymous

Clicking "x comments below threshold" clears the entire page (leaves it white).

mrnotsosafeforwork said:
blacklist does not work for profile pics, that is all

Fine over here.

Updated by anonymous

Varka said:
...Lemme know if I do actually need to find a solution to allow more than the first page to be accessible or if it doesn't matter.

It matters. I'll list the three main reasons I can think of but in short: it's used a lot so if you can get it up and working again, it would be a good thing for those of us who use it.

1, While I've rarely seen enough edits on an image's tag history to make it multipaged, I have often wanted to see the original first couple of edits to see if something was added by the uploader (who may have known more about the image's origins) or by someone else afterwards (who was more likely to be guessing). So if an image actually did get enough edits to become multi-paged in it's edit history, then I'd be frustrated if I needed to see where a certain tag added came from, etc. Some editing styles fill up a tag history faster than others. That's normal and fine but it would start to cause unrealistic problems if you're limited to only being able to look at the first page of history on anything.

2, Also, sometimes you need to crawl through your own tag history to track down an image you know you edited a couple days ago, and don't want to hazard searching through the entire category just to refind it or double check you didn't goof on it. If you tag hundreds of images in a week, it won't be on the first page of your own tag history anymore. I tried to do that just today and that's why I'm here. I was going to report it as a bug/glitch. Because it is. And I use it for this now and then on a semi-regular basis to double-check things so that would be nice to have it back.

3, The third reason I can see is probably mostly for management's use: needing to review a member's history to see if they're truly a bad tagger or just made a few goofs. Being able to contrast their earlier history to the present history can be important for deciding if they're a troll or not. Also useful for anyone who comes across a tag vandal since someone eventually needs to go back through and re-add a bunch of tags, and you'd want to be sure you got them all if it extends beyond just the first page or not.

Updated by anonymous

Butterscotch said:
Seems to be working for me.

i happen to have "gay" and "Tricksta" blacklisted, yet, i seen a gay Tricksta pic as an avatar

Updated by anonymous

mrnotsosafeforwork said:
i happen to have "gay" and "Tricksta" blacklisted, yet, i seen a gay Tricksta pic as an avatar

I tried blacklisting your avatar and... it worked.

Updated by anonymous

When trying to delete low res post #87560 I got following error:

error description

PostSet::PostAlreadyExistsError in PostController#destroy

PostSet::PostAlreadyExistsError

RAILS_ROOT: /home/e621/e621-production
Application Trace | Framework Trace | Full Trace

/home/e621/e621-production/app/models/post_set.rb:91:in add_post' /home/e621/e621-production/app/models/post.rb:112:in give_sets_to_parent'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in method_missing' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/associations/association_collection.rb:392:in method_missing_without_paginate'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/associations/association_proxy.rb:215:in map' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/associations/association_proxy.rb:215:in send'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/associations/association_proxy.rb:215:in method_missing' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/associations/association_collection.rb:392:in method_missing_without_paginate'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/will_paginate-2.3.16/lib/will_paginate/finder.rb:168:in method_missing' /home/e621/e621-production/app/models/post.rb:110:in give_sets_to_parent'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:136:in transaction' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/transactions.rb:182:in transaction'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/transactions.rb:188:in transaction' /home/e621/e621-production/app/models/post.rb:107:in give_sets_to_parent'
/home/e621/e621-production/app/models/post_methods/deletion_methods.rb:13:in destroy_with_reason' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:136:in transaction'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/transactions.rb:182:in transaction' /home/e621/e621-production/app/models/post_methods/deletion_methods.rb:8:in destroy_with_reason'
/home/e621/e621-production/app/controllers/post_controller.rb:373:in destroy' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/base.rb:1333:in send'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/base.rb:1333:in perform_action_without_filters' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/filters.rb:617:in call_filters'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/filters.rb:610:in perform_action_without_benchmark' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/benchmarking.rb:68:in perform_action_without_rescue'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activesupport-2.3.18/lib/active_support/core_ext/benchmark.rb:17:in ms' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activesupport-2.3.18/lib/active_support/core_ext/benchmark.rb:17:in ms'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/benchmarking.rb:68:in perform_action_without_rescue' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/rescue.rb:160:in perform_action_without_flash'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/flash.rb:151:in perform_action' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/base.rb:532:in send'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/base.rb:532:in process_without_filters' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/filters.rb:606:in process'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/base.rb:391:in process' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/base.rb:386:in call'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/routing/route_set.rb:438:in call' Request Parameters: {"mode"=>"0", "id"=>"87560", "reason"=>"Better quality & resolution posted: post #390870"} Show session dump Response Headers: {"Set-Cookie"=>"blacklisted_tags=poprocks&pulsar&smudge_proof&equestria_girls&twilight_sparkle_%28mlp%29+winged_unicorn+-princess_celestia_%28mlp%29+-princess_luna_%28mlp%29+-princess_cadance_%28mlp%29+-nightmare_moon_%28mlp%29&twilight_sparkle_%28mlp%29+winged_unicorn+-unicorn&mega_mewtwo_y&mega_mewtwo_y&megamewtwo&tyrranux&pyruvate&minecraft&user%3Aesprites&user%3Asetirpse&pool%3A2817; path=/\nblacklist_avatars=true; path=/\nblacklist_users=false; path=/", "Content-Type"=>"", "Cache-Control"=>"no-cache"} [/section] Also the link to which I was redirected, and where I got this error, was https://e621.net/post/destroy which doesn't look right.

Updated by anonymous

Xch3l said:
Clicking "x comments below threshold" clears the entire page (leaves it white).

Adding to this, I found that this is in the actual (blank) page:

<html>
  <head>
    <style type="text/css">.barbados { display: none !important; }</style>
  </head>
  <body/>
</html>

Did somebody barbados hacked that ooooor?

How did I get this: Go to any post with comments below threshold (they're usually in lol_comments or where a tag war had occured). Click the "X comments below threshold" and watch the page disappear.

Apparently, clicking that (or "x comments hidden" in the comments listing) rewrites the entire page.

Updated by anonymous

Xch3l said:
Adding to this, I found that this is in the actual (blank) page:

<html>
  <head>
    <style type="text/css">.barbados { display: none !important; }</style>
  </head>
  <body/>
</html>

Did somebody barbados hacked that ooooor?

No, it's css that states that elements that have class attribute of "barbados" should not be displayed. But comments under threshold seems to have "bad-comment" class instead.

Updated by anonymous

Gilda_The_Gryphon said:
No, it's css that states that elements that have class attribute of "barbados" should not be displayed. But comments under threshold seems to have "bad-comment" class instead.

Duh, I know that (indeed, comments below threshold have "bad-comment" as their class name). What I don't know is why this happens. The whole page being rewritten with that...

Updated by anonymous

Xch3l said:
Adding to this, I found that this is in the actual (blank) page:

<html>
  <head>
    <style type="text/css">.barbados { display: none !important; }</style>
  </head>
  <body/>
</html>

Did somebody barbados hacked that ooooor?

How did I get this: Go to any post with comments below threshold (they're usually in lol_comments or where a tag war had occured). Click the "X comments below threshold" and watch the page disappear.

you blacklisted barbados

Updated by anonymous

Aurali said:
you blacklisted barbados

Oh, so basically user blacklisting is not working. I've just tried to click "comments below threshold" on post #392931 with user:SnoWolf in blacklist and "Apply blacklisted users to forum posts, comments, Dmails, and blips" checked in settings, and I also got redirected somewhere.

Updated by anonymous

Aurali said:
you blacklisted barbados

Who would know that! I was testing that but forgot to remove that line... riiiiight!

Gilda_The_Gryphon said:
Oh, so basically user blacklisting is not working. I've just tried to click "comments below threshold" on post #392931 with user:SnoWolf in blacklist and "Apply blacklisted users to forum posts, comments, Dmails, and blips" checked in settings, and I also got redirected somewhere.

See? User blacklisting is borked :/

Also, I remember that the username was in the classname for the comment in a post ("comment username", now it's just "comment ")

Updated by anonymous

Xch3l said:
Who would know that! I was testing that but forgot to remove that line... riiiiight!

See? User blacklisting is borked :/

Also, I remember that the username was in the classname for the comment in a post ("comment username", now it's just "comment ")

looks like someone removed the code for comments to add the username class to the comment section. Shouldn't be too hard for Tony to fix. Works fine for forum posts though

Updated by anonymous

Munkelzahn said:
I'm the only person who uses the bugtracker :-(

of course, Tony doesn't see any point of it since he only has eyes on e621. And I was already tossing the code base aside for a fresh version anyway, Really hated bringing ancient code (really crappy code honestly) to the 21st century...

Updated by anonymous

I'm not seeing the numbers/posts per page that I wanna see for my profile. Fix/address this big problem! Thank you.

Updated by anonymous

Protego said:
I'm not seeing the numbers/posts per page that I wanna see for my profile. Fix/address this big problem! Thank you.

Not sure what you mean, the "posts per page" setting works fine.

Updated by anonymous

Fixed

Tried to suggest an Alias with https://e621.net/tag_alias/new , but keep getting error "NoMethodError in ForumController#create
undefined method downcase' for nil:NilClass RAILS_ROOT: /home/e621/e621-production Application Trace | Framework Trace | Full Trace ..." [/section]

Updated by anonymous

Fixed

Just got this while attempting to add the "penis" tag to a post.

ActiveRecord::UnknownAttributeError in PostController#update

unknown attribute: reason
RAILS_ROOT: /home/e621/e621-production

Application Trace | Framework Trace | Full Trace
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/base.rb:2926:in assign_attributes' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/base.rb:2922:in each'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/base.rb:2922:in assign_attributes' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/base.rb:2795:in attributes='
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/base.rb:2485:in initialize' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/base.rb:725:in new'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/base.rb:725:in create' /home/e621/e621-production/app/models/post_methods/tag_methods.rb:215:in commit_tags'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:136:in transaction' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/transactions.rb:182:in transaction'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/transactions.rb:188:in transaction' /home/e621/e621-production/app/models/post_methods/tag_methods.rb:80:in commit_tags'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activesupport-2.3.18/lib/active_support/callbacks.rb:178:in send' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activesupport-2.3.18/lib/active_support/callbacks.rb:178:in evaluate_method'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activesupport-2.3.18/lib/active_support/callbacks.rb:166:in call' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activesupport-2.3.18/lib/active_support/callbacks.rb:93:in run'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activesupport-2.3.18/lib/active_support/callbacks.rb:92:in each' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activesupport-2.3.18/lib/active_support/callbacks.rb:92:in send'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activesupport-2.3.18/lib/active_support/callbacks.rb:92:in run' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activesupport-2.3.18/lib/active_support/callbacks.rb:276:in run_callbacks'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/callbacks.rb:344:in callback' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/callbacks.rb:251:in create_or_update'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/base.rb:2585:in save_without_validation' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/validations.rb:1089:in save_without_dirty'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/dirty.rb:79:in save_without_transactions' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/transactions.rb:229:in send'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/transactions.rb:229:in with_transaction_returning_status' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:136:in transaction'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/transactions.rb:182:in transaction' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/transactions.rb:228:in with_transaction_returning_status'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/transactions.rb:196:in save' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/transactions.rb:208:in rollback_active_record_state!'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/transactions.rb:196:in save' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/base.rb:2680:in update_attributes_inside_transaction'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/transactions.rb:229:in send' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/transactions.rb:229:in with_transaction_returning_status'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:136:in transaction' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/transactions.rb:182:in transaction'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/transactions.rb:228:in with_transaction_returning_status' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/base.rb:2675:in update_attributes'
/home/e621/e621-production/app/controllers/post_controller.rb:277:in update' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/base.rb:1333:in send'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/base.rb:1333:in perform_action_without_filters' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/filters.rb:617:in call_filters'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/filters.rb:610:in perform_action_without_benchmark' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/benchmarking.rb:68:in perform_action_without_rescue'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activesupport-2.3.18/lib/active_support/core_ext/benchmark.rb:17:in ms' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activesupport-2.3.18/lib/active_support/core_ext/benchmark.rb:17:in ms'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/benchmarking.rb:68:in perform_action_without_rescue' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/rescue.rb:160:in perform_action_without_flash'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/flash.rb:151:in perform_action' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/base.rb:532:in send'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/base.rb:532:in process_without_filters' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/filters.rb:606:in process'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/base.rb:391:in process' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/base.rb:386:in call'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/routing/route_set.rb:438:in call' Request Parameters: {"id"=>"396438", "reason"=>"", "post"=>{"hide_anon"=>false, "old_tags"=>"anus breasts canine female interspecies lonbluewolf lying male neckerchief on_back pawpads penetration predator/prey_relations pussy raccoon reverse_cowgirl_position size_difference straight sweat vaginal vaginal_penetration wide_hips wolf", "parent_id"=>"", "hide_google"=>false, "rating"=>"Explicit", "source"=>"http://www.furaffinity.net/view/11972884/", "description"=>"", "tags"=>"Penis anus breasts canine female interspecies lonbluewolf lying male neckerchief on_back pawpads penetration predator/prey_relations pussy raccoon reverse_cowgirl_position size_difference straight sweat vaginal vaginal_penetration wide_hips wolf"}} Show session dump Response Headers: {"Content-Type"=>"", "Cache-Control"=>"no-cache", "Set-Cookie"=>"blacklisted_tags=gore; path=/\nblacklist_avatars=true; path=/\nblacklist_users=false; path=/"} Hope this helps. [/section]

Updated by anonymous

Fixed

AmericanExistence said:
The post you see above. Not showing that again. It's incredibly long.

Well, I just tried to edit my above post, and got this.

ActiveRecord::UnknownAttributeError in ForumController#update

unknown attribute: values
RAILS_ROOT: /home/e621/e621-production

Application Trace | Framework Trace | Full Trace
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/base.rb:2926:in assign_attributes' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/base.rb:2922:in each'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/base.rb:2922:in assign_attributes' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/base.rb:2795:in attributes='
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/base.rb:2485:in initialize' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/base.rb:725:in new'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/base.rb:725:in create' /home/e621/e621-production/app/controllers/forum_controller.rb:245:in update'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/base.rb:1333:in send' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/base.rb:1333:in perform_action_without_filters'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/filters.rb:617:in call_filters' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/filters.rb:610:in perform_action_without_benchmark'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/benchmarking.rb:68:in perform_action_without_rescue' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activesupport-2.3.18/lib/active_support/core_ext/benchmark.rb:17:in ms'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activesupport-2.3.18/lib/active_support/core_ext/benchmark.rb:17:in ms' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/benchmarking.rb:68:in perform_action_without_rescue'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/rescue.rb:160:in perform_action_without_flash' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/flash.rb:151:in perform_action'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/base.rb:532:in send' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/base.rb:532:in process_without_filters'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/filters.rb:606:in process' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/base.rb:391:in process'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/base.rb:386:in call' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/routing/route_set.rb:438:in call'
Request

Parameters:

{"id"=>"89695",
"forum_post"=>{"category_id"=>"1",
"title"=>"",
"body"=>"Just got this while attempting to add the \"penis\" tag to a post.\r\n\r\nActiveRecord::UnknownAttributeError in PostController#update\r\n\r\nunknown attribute: reason\r\nRAILS_ROOT: /home/e621/e621-production\r\n\r\nApplication Trace | Framework Trace | Full Trace\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/base.rb:2926:in assign_attributes'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/base.rb:2922:in each'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/base.rb:2922:in assign_attributes'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/base.rb:2795:in attributes='\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/base.rb:2485:in initialize'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/base.rb:725:in new'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/base.rb:725:in create'\r\n/home/e621/e621-production/app/models/post_methods/tag_methods.rb:215:in commit_tags'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:136:in transaction'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/transactions.rb:182:in transaction'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/transactions.rb:188:in transaction'\r\n/home/e621/e621-production/app/models/post_methods/tag_methods.rb:80:in commit_tags'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activesupport-2.3.18/lib/active_support/callbacks.rb:178:in send'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activesupport-2.3.18/lib/active_support/callbacks.rb:178:in evaluate_method'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activesupport-2.3.18/lib/active_support/callbacks.rb:166:in call'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activesupport-2.3.18/lib/active_support/callbacks.rb:93:in run'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activesupport-2.3.18/lib/active_support/callbacks.rb:92:in each'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activesupport-2.3.18/lib/active_support/callbacks.rb:92:in send'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activesupport-2.3.18/lib/active_support/callbacks.rb:92:in run'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activesupport-2.3.18/lib/active_support/callbacks.rb:276:in run_callbacks'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/callbacks.rb:344:in callback'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/callbacks.rb:251:in create_or_update'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/base.rb:2585:in save_without_validation'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/validations.rb:1089:in save_without_dirty'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/dirty.rb:79:in save_without_transactions'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/transactions.rb:229:in send'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/transactions.rb:229:in with_transaction_returning_status'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:136:in transaction'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/transactions.rb:182:in transaction'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/transactions.rb:228:in with_transaction_returning_status'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/transactions.rb:196:in save'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/transactions.rb:208:in rollback_active_record_state!'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/transactions.rb:196:in save'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/base.rb:2680:in update_attributes_inside_transaction'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/transactions.rb:229:in send'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/transactions.rb:229:in with_transaction_returning_status'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/connection_adapters/abstract/database_statements.rb:136:in transaction'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/transactions.rb:182:in transaction'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/transactions.rb:228:in with_transaction_returning_status'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/base.rb:2675:in update_attributes'\r\n/home/e621/e621-production/app/controllers/post_controller.rb:277:in update'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/base.rb:1333:in send'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/base.rb:1333:in perform_action_without_filters'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/filters.rb:617:in call_filters'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/filters.rb:610:in perform_action_without_benchmark'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/benchmarking.rb:68:in perform_action_without_rescue'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activesupport-2.3.18/lib/active_support/core_ext/benchmark.rb:17:in ms'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activesupport-2.3.18/lib/active_support/core_ext/benchmark.rb:17:in ms'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/benchmarking.rb:68:in perform_action_without_rescue'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/rescue.rb:160:in perform_action_without_flash'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/flash.rb:151:in perform_action'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/base.rb:532:in send'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/base.rb:532:in process_without_filters'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/filters.rb:606:in process'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/base.rb:391:in process'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/base.rb:386:in call'\r\n/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/routing/route_set.rb:438:in call'\r\nRequest\r\n\r\nParameters:\r\n\r\n{\"id\"=>\"396438\", \r\n \"reason\"=>\"\", \r\n \"post\"=>{\"hide_anon\"=>false, \r\n \"old_tags\"=>\"anus breasts canine female interspecies lonbluewolf lying male neckerchief on_back pawpads penetration predator/prey_relations pussy raccoon reverse_cowgirl_position size_difference straight sweat vaginal vaginal_penetration wide_hips wolf\", \r\n \"parent_id\"=>\"\", \r\n \"hide_google\"=>false, \r\n \"rating\"=>\"Explicit\", \r\n \"source\"=>\"http://www.furaffinity.net/view/11972884/\", \r\n \"description\"=>\"\", \r\n \"tags\"=>\"Penis anus breasts canine female interspecies lonbluewolf lying male neckerchief on_back pawpads penetration predator/prey_relations pussy raccoon reverse_cowgirl_position size_difference straight sweat vaginal vaginal_penetration wide_hips wolf\"}}\r\nShow session dump\r\n\r\nResponse\r\n\r\nHeaders:\r\n\r\n{\"Content-Type\"=>\"\", \r\n \"Cache-Control\"=>\"no-cache\", \r\n \"Set-Cookie\"=>\"blacklisted_tags=gore; path=/\nblacklist_avatars=true; path=/\nblacklist_users=false; path=/\"}\r\n\r\nHope this helps."}} Show session dump Response Headers: {"Content-Type"=>"", "Cache-Control"=>"no-cache", "Set-Cookie"=>"blacklisted_tags=gore; path=/\nblacklist_avatars=true; path=/\nblacklist_users=false; path=/"} [/section]

Updated by anonymous

Yeah, expect to see a bunch of errors for now (and please don't report them yet), we're still working on the database.

Updated by anonymous

tony311 said:
Yeah, expect to see a bunch of errors for now (and please don't report them yet), we're still working on the database.

So, should we stop poking it? creating or editing stuff?

Updated by anonymous

OK, database should work fine now. Please report any further errors you get :)

Updated by anonymous

Fixed

Selecting "None" for extra theme changes theme to autumn after refreshing page.

Updated by anonymous

Gilda_The_Gryphon said:
Selecting "None" for extra theme changes theme to autumn after refreshing page.

Should be fixed now.

Updated by anonymous

The new reason field in the tag history page is breaking the frame to the right.
For me anyway, using Chrome newest version.

Updated by anonymous

The Trending Tag field is not showing the list of tags, also using newest version of Chrome as well.

Updated by anonymous

Halite said:
The new reason field in the tag history page is breaking the frame to the right.
For me anyway, using Chrome newest version.

Intentional, there's just too damn much information in the table to have it scale to the browser size (which usually isn't nearly wide enough).

furcrazy666 said:
The Trending Tag field is not showing the list of tags, also using newest version of Chrome as well.

The one on the left side of the post index? Shows tags for me.

Updated by anonymous

Tried to suggest an Alias (pooh_bear -> winnie_the_pooh ) and got error:

"NoMethodError in ForumController#create

undefined method rstrip!' for nil:NilClass RAILS_ROOT: /home/e621/e621-production Application Trace | Framework Trace | Full Trace /home/e621/e621-production/app/controllers/forum_controller.rb:51:in create'
/usr/local/rvm/gems/ree-1.8.7-2011.03/gems/actionpack-2.3.18/lib/action_controller/base.rb:1333:in send' /usr/local/rvm/gems/ree-1.8.7-2011.03/gems/actionpack-2.3.18/lib/action_controller/base.rb:1333:in perform_action_without_filters'
/usr/local/rvm/gems/ree-1.8.7-2011.03/gems/actionpack-2.3.18/lib/action_controller/filters.rb:617:in call_filters' /usr/local/rvm/gems/ree-1.8.7-2011.03/gems/actionpack-2.3.18/lib/action_controller/filters.rb:610:in perform_action_without_benchmark'
/usr/local/rvm/gems/ree-1.8.7-2011.03/gems/actionpack-2.3.18/lib/action_controller/benchmarking.rb:68:in perform_action_without_rescue' /usr/local/rvm/gems/ree-1.8.7-2011.03/gems/activesupport-2.3.18/lib/active_support/core_ext/benchmark.rb:17:in ms'
/usr/local/rvm/gems/ree-1.8.7-2011.03/gems/activesupport-2.3.18/lib/active_support/core_ext/benchmark.rb:17:in ms' /usr/local/rvm/gems/ree-1.8.7-2011.03/gems/actionpack-2.3.18/lib/action_controller/benchmarking.rb:68:in perform_action_without_rescue'
/usr/local/rvm/gems/ree-1.8.7-2011.03/gems/actionpack-2.3.18/lib/action_controller/rescue.rb:160:in perform_action_without_flash' /usr/local/rvm/gems/ree-1.8.7-2011.03/gems/actionpack-2.3.18/lib/action_controller/flash.rb:151:in perform_action'
/usr/local/rvm/gems/ree-1.8.7-2011.03/gems/actionpack-2.3.18/lib/action_controller/base.rb:532:in send' /usr/local/rvm/gems/ree-1.8.7-2011.03/gems/actionpack-2.3.18/lib/action_controller/base.rb:532:in process_without_filters'
/usr/local/rvm/gems/ree-1.8.7-2011.03/gems/actionpack-2.3.18/lib/action_controller/filters.rb:606:in process' /usr/local/rvm/gems/ree-1.8.7-2011.03/gems/actionpack-2.3.18/lib/action_controller/base.rb:391:in process'
/usr/local/rvm/gems/ree-1.8.7-2011.03/gems/actionpack-2.3.18/lib/action_controller/base.rb:386:in call' /usr/local/rvm/gems/ree-1.8.7-2011.03/gems/actionpack-2.3.18/lib/action_controller/routing/route_set.rb:438:in call'
Request

Parameters:

{"forum_post"=>{"category_id"=>"2"},
"tag_alias"=>{"reason"=>"Same character. http://www.imdb.com/character/ch0000620/ says \"Winnie the Pooh (Character) ...\".",
"name"=>"pooh_bear",
"alias"=>"winnie_the_pooh"}}
Show session dump

Response

Headers:

{"Content-Type"=>"",
"Set-Cookie"=>"blacklisted_tags=; path=/\nblacklist_avatars=true; path=/\nblacklist_users=false; path=/",
"Cache-Control"=>"no-cache"}"

Updated by anonymous

Extras overlap other containers,

If you are using a mobile device or have a screen less then 1500 px wide, then the tag history stretches too wide

thumb # is broken

the news option is WAY too blue now

also why the hell are all the links debolded, things don't look clickable anymore

certain themes don't mix right with certain "extras"

and You haven't properly repaired the error finding system,

Updated by anonymous

Aurali said:
Extras overlap other containers,

I noticed but I don't really think it's a big deal.

Aurali said:
If you are using a mobile device or have a screen less then 1500 px wide, then the tag history stretches too wide

Intentional, it just has to be wide to show all of the information.

Aurali said:

thumb # is broken

Fix is already submitted.

Aurali said:
the news option is WAY too blue now

The news bar is slightly brighter than the main content div but it's not a big deal.

Aurali said:
also why the hell are all the links debolded, things don't look clickable anymore

I don't recall that ever changing.

Aurali said:
certain themes don't mix right with certain "extras"

So don't use them together.

Aurali said:
and You haven't properly repaired the error finding system,

Indeed, but at least it makes fixing bugs a hundred times easier.

Updated by anonymous

tony311 said:
I noticed but I don't really think it's a big deal.

It can make data hard to read

Intentional, it just has to be wide to show all of the information.

If you are gonna design for the web then do it right, more and more people are using mobile devices, that are at most 1200 pixels wide, that should be your max point, nothing more, You should find a way to fix it.

Fix is already submitted.

thank you

The news bar is slightly brighter than the main content div but it's not a big deal.

Eh, it's eye grabbing, so I guess that's not a big deal.

I don't recall that ever changing.

user pages had bolded links, like main links, It still shows on the other websites.

So don't use them together.

I'm reporting things.

Indeed, but at least it makes fixing bugs a hundred times easier.

It looks extremely unprofessional to see a "cannot find post" page. if you want to make it easier, make a param that calls a developer mode result. I used that when I was doing tests on function call back time to make sure this giant PoS actually ran at decent speeds.

Updated by anonymous

furcrazy666 said:
The Trending Tag field is not showing the list of tags, also using newest version of Chrome as well.

I'm having the same issue in FF, but only after I search for a specific tag. If I view the main posts page, the trending tags are displayed.

Main page: http://i.imgur.com/4Hab1bu.jpg

Searched tag page: http://i.imgur.com/qg2BfqB.jpg

This occurs both when I am logged in or out. Have cleared cache and all offline data and disabled plugins but it still persists.

Updated by anonymous

Did the trending tags list do anything different when you searched for a tag?

Updated by anonymous

type:jpg
type:png
type:gif
type:swf

When I search for any one of these metatags (and no other tags) on the e621 front page, everything works fine:
https://e621.net/

But when I search for any one of these metatags (and no other tags) from anywhere else, for example from a post, e621 gives me this error:

Nobody here but us chickens!

The page cannot be found. Either you made a typo in the URL or someone gave you a bad link.

Searching for any one of these metatags in combination with at least one other tag works from anywhere, though. Example:
type:gif animated

Updated by anonymous

Visiting a link to a deleted pool is not handled gracefully. Instead of a page like the ones for deleted posts, it's a detailed error page:

ActiveRecord::RecordNotFound in PoolController#show

Couldn't find Pool with ID=3183
RAILS_ROOT: /home/e621/e621-production

Application Trace | Framework Trace | Full Trace
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/base.rb:1620:in find_one' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/base.rb:1603:in find_from_ids'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activerecord-2.3.18/lib/active_record/base.rb:620:in find' /home/e621/e621-production/app/controllers/pool_controller.rb:19:in show'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/base.rb:1333:in send' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/base.rb:1333:in perform_action_without_filters'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/filters.rb:617:in call_filters' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/filters.rb:610:in perform_action_without_benchmark'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/benchmarking.rb:68:in perform_action_without_rescue' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activesupport-2.3.18/lib/active_support/core_ext/benchmark.rb:17:in ms'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/activesupport-2.3.18/lib/active_support/core_ext/benchmark.rb:17:in ms' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/benchmarking.rb:68:in perform_action_without_rescue'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/rescue.rb:160:in perform_action_without_flash' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/flash.rb:151:in perform_action'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/base.rb:532:in send' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/base.rb:532:in process_without_filters'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/filters.rb:606:in process' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/base.rb:391:in process'
/usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/base.rb:386:in call' /usr/local/rvm/gems/ree-1.8.7-2012.02/gems/actionpack-2.3.18/lib/action_controller/routing/route_set.rb:438:in call'
Request

Parameters:

{"id"=>"3183"}
Show session dump

Response

Headers:

{"Cache-Control"=>"no-cache",
"Content-Type"=>"",
"Set-Cookie"=>"blacklisted_tags=f%C3%A6ces&applebeans&gore&hyper&growth&diaper&vore&sting&bee_sting&phoenix-d&ballbusting&cock_and_ball_torture&chiron178&rimming+-group_sex+-threesome&you+know+i+love+you%2C+char+%3C3; path=/\nblacklist_avatars=true; path=/\nblacklist_users=false; path=/"}

Updated by anonymous

Munkelzahn said:
Searching for any one of these metatags in combination with at least one other tag works from anywhere, though. Example:
type:gif animated

Known issue, just make sure the gif/png/etc. isn't the last part of the URL, if possible

Snowy said:
Visiting a link to a deleted pool is not handled gracefully. Instead of a page like the ones for deleted posts, it's a detailed error page:

Caused by "pretty" error pages being disabled (don't know why they're disabled though).

Updated by anonymous

tony311 said:
Did the trending tags list do anything different when you searched for a tag?

Do you mean before the update or since I posted?

I still don't get a list when I search for a tag. I should also note that it does this if I type one in the search box or click a tag.

Updated by anonymous

:3 Okay, let me try explaining this again.

tony311 said:
Known issue, just make sure the gif/png/etc. isn't the last part of the URL, if possible

Don't worry about this tony unless you want to add a "/" at the end of the url, Varka mishandled the nginx redirect for files ending in an extension, adding the redirect under the root for the website instead of just under the public folder like it was originally designed to be under.

Caused by "pretty" error pages being disabled (don't know why they're disabled though).

You and Varka removed it because it was sending emails to someplace, and instead of just blackholing the emails, you removed the entire error handling system. To fix it you either have to re add the error handler to the vendors, or build your own.

Updated by anonymous

logitech said:
Do you mean before the update or since I posted?

Before. I can "fix" it, but only by making it show the top 30 or whatever tags being used in the last day regardless of what you're searching for. Looking at the code, I can't really figure out why it was working while searching tags in the first place, since the reason it doesn't show any is fairly obvious.

Note: Due to us redoing that trending tags system to use way, way fewer queries, making it show search-specific popular tags may be impossible.

Updated by anonymous

tony311 said:
Note: Due to us redoing that trending tags system to use way, way fewer queries, making it show search-specific popular tags may be impossible.

Use the same query, sorting tags from most used to least used on the posts returned

Updated by anonymous

tony311 said:
Should be fixed now.

Currently not showing any tags, even when clicking a tag in the list. I expected it to return the most popular combination of tags that are tagged with the tag selected/searched, or at least based off the block of images on the page I'm currently looking at- not give a blank list.

Updated by anonymous

With the "Hexagon Clean" base theme, the frontpage mascot image gets tiled instead of centered. Tested on Chrome, Firefox and (god help me) Internet Explorer.

Updated by anonymous

Gilda_The_Gryphon said:
I don't know how about others but for me trending tags seem to work when "*", or alternative "~" is added to search.

So, for example:
death scat gore - no trending tags.
death scat* gore - there are trending tags
death scat gore * - there are trending tags
~death ~scat gore - there are trending tags

Hence "the reason it doesn't show any is fairly obvious" - it only shows trending tags if there's no query, or if there is a query but it includes 'related' tags, i.e. wildcards and the ~ modifier. I have no idea why it showed trending tags before even without either of those, or why it only shows the list with those (or no search at all).

Updated by anonymous

tony311 said:
Hence "the reason it doesn't show any is fairly obvious" - it only shows trending tags if there's no query, or if there is a query but it includes 'related' tags, i.e. wildcards and the ~ modifier. I have no idea why it showed trending tags before even without either of those, or why it only shows the list with those (or no search at all).

I would rather throw Trending Tags completely out the window if it meat getting a consistant list of tags. Often I used the listing to pick out a few tags I wanted to search according to my query prior, and with the functionality as it is now, it's actually driving me to go use a more intelligent and easier to use system at another site until fixed. :/

Updated by anonymous

Having the list of the most common tags in a given search was rather helpful to weed out related images with certain tags, or to include other related tags. Infact, the behavior of "trending tags" has been more like "the most common tags related to your search." That's /way/ more helpful than "30 tags unrelated to the images shown in your search, but are just common on the website"

Luckily, for now, a somewhat similar functionality can be had just by adding a " *" to the end of one's search.

**though i should say that this by-no-means makes up for the missing feature**

Updated by anonymous

WoofyTheBunny said:
Having the list of the most common tags in a given search was rather helpful to weed out related images with certain tags, or to include other related tags. Infact, the behavior of "trending tags" has been more like "the most common tags related to your search." That's /way/ more helpful than "30 tags unrelated to the images shown in your search, but are just common on the website"

Luckily, for now, a somewhat similar functionality can be had just by adding a " *" to the end of one's search.

x10000 It's loads easier to quickly weed out something you're not interested at all that's commonly associated with the tag you searched for. Like I may search for 'equine' but not want it inundated with MLP stuff (not harping on anyone, it's just an easy example).

For now I guess I can use the asterisk trick. Perhaps someone could make a greasemonkey script to do the same thing for you.

Updated by anonymous

Searching for status:deleted returns page without any picture, and

404 Not Found - https://e621.net/deleted-preview.png

error in firebug console. I reported it some time ago, but for a brief moment after update it was working okay.

Updated by anonymous

When requesting to read a Wiki entry using the API I get the following error:

Template is missing

Missing template wiki/show.erb in view path app/views

list works fine though. Haven't checked the others since I have no use for them (say, correct an existing entry or create a new one while I'm at it)

Updated by anonymous

I'm getting an error when trying to alias hyper_penis to hyper (which is short for hyperphallic according to the alias history.)

I'm getting the error that hyper_penis is already aliased to something, but from what I can see it's being used as a root tag, meaning the error message is misleading.

Error: hyper_penis is already aliased to something

edit: I've since looked this up but it took me a bit to figure out what I now suspect is going on. The error I believe is because of the current linkage that hyper_penis is associated with the general concept of hyper. The message should explain what's really up - something along the lines of "cannot alias hyper_penis to hyper because hyper_penis implies hyper"... even so I'm not sure this is a legitimate objection anyways in the general case if I'm understanding this all correctly.

Updated by anonymous

Char

Former Staff

ragswift said:
I'm getting an error when trying to alias hyper_penis to hyper (which is short for hyperphallic according to the alias history.)

I'm getting the error that hyper_penis is already aliased to something, but from what I can see it's being used as a root tag, meaning the error message is misleading.

Error: hyper_penis is already aliased to something

edit: I've since looked this up but it took me a bit to figure out what I now suspect is going on. The error I believe is because of the current linkage that hyper_penis is associated with the general concept of hyper. The message should explain what's really up - something along the lines of "cannot alias hyper_penis to hyper because hyper_penis implies hyper"... even so I'm not sure this is a legitimate objection anyways in the general case if I'm understanding this all correctly.

It's because hyper_cock is currently aliased to hyper_penis. The system won't let you "chain" aliases together, so you can't alias hyper_cock to hyper_penis to hyper_whatever.

Second, I'm not sure that I agree with hyperphallic being aliased to hyper to begin with. We have tags for several different "hyper" things, so I'm not sure why hyperphallic would be an exception. It just needs to be aliased to hyper_penis like hyper_cock currently is (which wouldn't be a chain).

Updated by anonymous

Description tracking needs a major overhaul. Histories say click to show even when there's no change, and the description history page shows tag edits as description edits. We need a link for all description changes by single users on their profile pages, since the description column doesnt fit on the tag history page, which should also be fixed.

Updated by anonymous

I'm sorry if this has been said already/ is an easy fix, but I am having an odd problem with tags.

I can add a tag to a search with no problem, and if I click on an image, I can see them all. However, the second it searches with a tag, the trending tags says 'No Tags" and will refuse to display any new tags that could be added to the filter.

This makes it difficult to filter certain categories, is there any way to fix this, or is it intended?

Updated by anonymous

SX_men said:
I'm sorry if this has been said already/ is an easy fix, but I am having an odd problem with tags.

I can add a tag to a search with no problem, and if I click on an image, I can see them all. However, the second it searches with a tag, the trending tags says 'No Tags" and will refuse to display any new tags that could be added to the filter.

This makes it difficult to filter certain categories, is there any way to fix this, or is it intended?

https://e621.net/forum/show/90154

Updated by anonymous

123easy said:
I would rather throw Trending Tags completely out the window if it meat getting a consistant list of tags. Often I used the listing to pick out a few tags I wanted to search according to my query prior, and with the functionality as it is now, it's actually driving me to go use a more intelligent and easier to use system at another site until fixed. :/

Reiterating. Multiple years of tags working great, and now that section is completely useless. :/

Updated by anonymous

123easy said:
Reiterating. Multiple years of tags working great, and now that section is completely useless. :/

But it was an incredibly massive hit on database performance, so we had to strip it down. Maybe if we can figure out how to do it sanely it'll work how it used to do, but no promises. Clarification: showing "No tags" when searching is a bug, it should still just show the top 30 tags on posts uploaded in the last 24 hours (not taking into effect your query, because that's the performance hit).

Updated by anonymous

tony311 said:
But it was an incredibly massive hit on database performance, so we had to strip it down. Maybe if we can figure out how to do it sanely it'll work how it used to do, but no promises. Clarification: showing "No tags" when searching is a bug, it should still just show the top 30 tags on posts uploaded in the last 24 hours (not taking into effect your query, because that's the performance hit).

I would love it to do that, but the current no-tags-lists bit really sucks v_v

Updated by anonymous

123easy said:
I would love it to do that, but the current no-tags-lists bit really sucks v_v

It's already fixed in the next update (again, so it'll always show top 30 tags on posts uploaded in the last day regardless of what you're searching for).

Updated by anonymous

tony311 said:
It's already fixed in the next update (again, so it'll always show top 30 tags on posts uploaded in the last day regardless of what you're searching for).

That's all I wanted. Yay!

Updated by anonymous

tony311 said:
But it was an incredibly massive hit on database performance, so we had to strip it down. Maybe if we can figure out how to do it sanely it'll work how it used to do, but no promises. Clarification: showing "No tags" when searching is a bug, it should still just show the top 30 tags on posts uploaded in the last 24 hours (not taking into effect your query, because that's the performance hit).

That's really something you guys should be offloading to memcache, not the db.

Updated by anonymous

tony311 said:
It's already fixed in the next update (again, so it'll always show top 30 tags on posts uploaded in the last day regardless of what you're searching for).

Gilda_The_Gryphon said:
I don't know how about others but for me trending tags seem to work when "*", or alternative "~" is added to search.

So, for example:
death scat gore - no trending tags.
death scat* gore - there are trending tags
death scat gore * - there are trending tags
~death ~scat gore - there are trending tags

Honestly I would much prefer if it showed the current wiki entry for a non-~ non-* tag, if one exists, and only a single tag has been searched on. Then maybe have a toggle for this behavior on-page or in settings? It would encourage good tagging some.

Updated by anonymous