Matchu
8aa4aa6e30
Drop NewsPosts model
...
We never ended up really using this lol, and it has an attr_accessible I want to be rid of so let's just fully trash it while we're at it!
2023-10-23 19:05:04 -07:00
Matchu
b5442d0f3f
news posts read from the database, with a campaign-supplement classname option :)
2015-09-26 20:37:03 -07:00
Matchu
b11d7a8c9c
oh dang, did we just fix most of the mixed content?
2015-08-05 20:11:08 -04:00
Matchu
b639453f61
on a fresh copy of the site, hide the latest contribution section
2015-07-16 18:39:43 -04:00
093ae27ae8
get upset when we neopets.com bans us :P
2015-07-15 00:09:17 -04:00
0e6f823154
toggle whether a donation campaign is advertised
2015-02-25 13:49:18 -06:00
41da9d0629
swap the homepage forms back in anticipation of Neopets.com uptime
2014-09-19 07:26:30 -05:00
8e3a2f59e9
swap the new outfit forms because downtime
2014-09-17 22:48:48 -05:00
d588253c4c
campaign banner on homepage is pretty
2014-09-11 18:09:00 -05:00
dd0a3cd350
dont allow blank name submissions in modeling hub small form
2014-04-16 11:11:15 -05:00
a375707e40
handle errors from neopia, finally!
2014-04-04 15:53:53 -05:00
8e93d603fa
list prank colors as fake on the homepage, unless pranks are funny today
2014-03-27 22:44:18 -05:00
8ace3111f7
oops; put impress_user field on model-a-pet homepage form
2014-01-20 16:03:40 -06:00
03c76fe882
Update missing body ID prediction to handle, say, the Maraquan Mynci.
...
It turns out that some pets for seemingly nonstandard colors have the
standard body type anyway, and vice-versa. This implies that we should
stop relying on a color's standardness, but, for the time being, we've
just revised the prediction model:
Old model:
* If I see a body_id, I find the corresponding color_ids, and it's wearable
by all pet types with those color_ids.
New model:
* If I see a body_id,
* If it also belongs to a basic pet type, it's a standard body ID.
* It therefore fits all pet types of standard color (if there's
more than one body ID modeled already). (Not really,
because of weird exceptions like Orange Chia. Should that be
standard or not?)
* If it doesn't also belong to a basic pet type, it's a nonstandard
body ID.
* It therefore only belongs to one color, and therefore the item
fits all pet types of the same color.
2014-01-20 15:29:01 -06:00
fb6df82570
ugh, push temporary version without new items
2014-01-20 14:46:50 -06:00
00841e45d2
modeling i18n
2014-01-20 13:56:19 -06:00
72b174c9b3
store all neopets usernames for logged-in users, but breaks closet_hangers#index
2014-01-18 21:55:01 -06:00
8288b8a10d
username form, backed by localstorage for guests; not yet backed by db for logged-in users
2014-01-17 11:12:56 -06:00
813cfbddea
filter customizations by missing body ids
2014-01-10 16:25:03 -05:00
fd106d7dba
basic modeling buttons
...
no behavior yet, nor are they filtered
2014-01-10 16:25:03 -05:00
949fa2a77a
i18n newest items headers
2014-01-10 16:25:02 -05:00
342f8ef859
remove unused outfits.new.newest_items.header i18n key
2014-01-10 16:25:02 -05:00
7dd2646dbb
add basic caching - TODO: avoid these computations in the controller
2014-01-10 16:25:02 -05:00
9a4e114964
oh yum, this is really starting to come together :)
2014-01-10 16:25:02 -05:00
85e1973f55
yummy mockups for newest items progress bars
2014-01-10 16:25:02 -05:00
7c6e607612
basic neopia api integration
2014-01-10 16:25:02 -05:00
c7237d7d44
fix a bunch of precompiled-asset-missing errors
2013-03-05 22:26:14 -06:00
5dddb6dbdc
i18n for outfits/new.js
2013-01-10 18:24:12 -06:00
f82d3683f5
i18n for pet_query.js
2013-01-10 16:47:46 -06:00
7aa49f70be
refactor outfits.new for hierarchy
2013-01-09 18:40:35 -06:00
744c10495d
i18n for outfits#new (and layouts#application), including caching
2013-01-09 17:15:23 -06:00
99669b8e4e
cache homepage latest contribution
2012-08-09 22:59:35 -04:00
f6d34841ec
cache newest items on homepage and items#index
2012-08-09 22:35:30 -04:00
5e89287537
durr, don't cache new items on the homepage
2012-08-08 23:05:32 -04:00
5cec28e29b
fix logout bug: stop caching authenticity_token fields
...
Many forms on the site contain a hidden authenticity_token field,
unique to each visitory. If a user submits a request with an
invalid authenticity_token, Rails assumes that it's a CSRF attempt
and logs out the user. So, if we happen to cache those forms with
authenticity_token fields, all users who use that form will have
the same authenticity_token (valid for only the first user who
saw the form, invalid for everyone else), and all requests made
through that form will log out the user. Bad news.
So, we stopped caching those forms. Yay!
2012-08-07 17:32:51 -04:00
72237f225c
modeling hub
2012-08-06 21:15:31 -04:00
a6e4398e54
take homepage latest contribution and new items out of cache block - should probably cache them later, but, for now, meh
2012-08-01 15:11:08 -04:00
c2a0c5de74
new frontpage layout, yay
2012-08-01 13:34:54 -04:00
4c510f91db
search by username
2011-08-05 11:28:11 -04:00
5f4cd9ddbf
new! tags to point to Your Items
2011-07-31 22:55:29 -04:00
037cb1e95a
your items link on home
2011-07-31 18:45:53 -04:00
7640369332
drop donate bar into items, outfits#show
2011-07-09 11:45:30 -04:00
211d08204d
add Donate Now! button to campaign progress on home
2011-07-04 23:23:28 -04:00
f9e3266a3b
change wording a bit
2011-07-04 17:52:34 -04:00
323cf772bc
actually dynamic progress bar, on home page too
2011-07-01 15:38:13 -04:00
ca155314fa
home page caching, reset top contributors only when necessary
2010-12-11 09:37:39 -05:00
b7fb5a952b
Revert "implement head.js"
...
This reverts commit 12ffa33f4f
2010-12-06 18:50:13 -05:00
6cc892ff83
remove unnecessary wardrobe.js dependency on home page
2010-12-06 18:13:38 -05:00
12ffa33f4f
implement head.js
2010-12-05 21:18:52 -05:00
0399e0a38f
remove tell the world link
2010-11-30 16:52:38 -05:00
