Leaving the #order call in #last_three_comments caused the generated SQL to
have two conflicting ORDER BY components, which caused the query to return
invalid results. I removed the problem by removing #last_three_comments which
I consider a premature optimization.
commit 740296e86fdd080e6e787c5c024a6b609782d82f
Author: The Lambda Calculus <code@thelambdacalculus.net>
Date: Mon Oct 10 16:49:35 2011 -0400
Wrote rspec for atom feed validation. [Finishes issue #1408]
commit e2999cbe588bcb32f35f05120743627cf3b31f56
Author: The Lambda Calculus <code@thelambdacalculus.net>
Date: Thu Sep 29 18:28:14 2011 -0400
Adjusted placement of invalid 'link' elements outside of 'author' element. Feed now validates, though warnings/suggestions still exist. [Issue #1408]
locally when Resque tried to constantize Jobs::Mail Object.const_get("Jobs") returned our Jobs module but when it tried to const_get("Mail") it returned the Mail gem.
added copyright
Rack 1.2's request.url method is buggy, as it gets the host part from
HTTP_X_FORWARDED_HOST, but the port from SERVER_PORT (which should be
used in conjuction with SERVER_ADDR).
This way, if the app is run behind a reverse proxy, it will create a
URL with <public_host>:<private port>, and pass this to Facebook,
so Facebook will redirect back to the URL with the wrong port.
Upgrading Rack requires upgrade to Rails 3.1.
This temporary solution configures OmniAuth using a copy of the newer
version of Rack::Request.
This becomes a problem when having this widget
instantiated looking at the followed_tags stream
With the former code de/selecting aspects was
only refreshing the followed_tags stream, not
loading aspect stream posts
With previous css selector two textareas where
returned, causes reset of the post text when
selecting new aspects for the second time on
the left nav. Related to #2102
