Dress to Impress, a big fancy Neopets customization tool!
f54683464f
One time I did a thing called Camo to try to get our HTTPS pages working, because images.neopets.com not supporting HTTPS is crazy >_> I've diasbled it these days, but it had debug behavior to append `?NO_CAMO_CONFIG` to all proxied URLs when Camo was not configured. When an item had no thumbnail URL for some reason (mall spider needs fixing, maybe?), this caused Rails to try to map that empty string into the path `/assets/?NO_CAMO_CONFIG`, which made Rails complain that it was trying to load an asset that doesn't exist. This is probably a sign that using `image_tag` for URLs that *should* be external URLs, but aren't strictly *guaranteed* to be, is unwise - but, for now, I've just disabled that behavior. I hope Rails has a better escape hatch for the empty string :P |
||
|---|---|---|
| .sass-cache | ||
| app | ||
| autotest | ||
| config | ||
| db | ||
| doc | ||
| lib | ||
| public | ||
| script | ||
| spec | ||
| test | ||
| tmp | ||
| vendor | ||
| .gitignore | ||
| bundle | ||
| Capfile | ||
| config.ru | ||
| Gemfile | ||
| Gemfile.lock | ||
| isntall | ||
| LICENSE | ||
| Rakefile | ||
| README | ||
An extension of Dress to Impress (PHP) that runs on Ruby on Rails. I wanted to use Rails initially for Impress, but hoped that using PHP would allow me to attract more developers. Looks like that wasn't the case, so I just went with what I loved and made the items database in Rails. Future Impress sections will likely find themselves in this project, rather than the PHP project.