Adds the framework for having two different ways to start a method thread. One way has already been implemented, the other way is directed to by a link on a user's page.
Changes thread_id to message_thread_id because of conflict with built-in methods.
Changes the name to message_thread_id everywhere I could find
Fixes the dependent:destroy issue by actually implementing the feature.
Starting the photos setup
Makes appropriate migration and model
Starts on photo indexing. For now, we're just going to use URL's (or maybe placekittens) as placeholders
Adding missing associations between Users and Photos. I suppose we actually need a join table here.
Adds in the infrastructure for PhotoTaggings
Adds a photo top bar with tagged photos vs. uploaded photos, and a create new photo button if it's us. By default, we're on the uploaded photos page, which for now is just a bunch of links.
Structure around going to photos pages is in place, including appropriate links.
Incorporating comments and replies into showing a photo, using previously existing models and templates.
Adds association between photo and comment, including migration. It's a little weird that all comments have a photo_id (or lack thereof), though...
Breaks out into a PhotoComment model instead of building too much functionality into normal Comments
Makes all of the other necessary changes around the existence of PhotoComments
More refactoring changes to get the comments/replies framework to work correctly with photos (this time with regard to likes)
Adding editing and updating for a photo comment
Puts in the relevant controller actions, and some more logic for the differences between a photo comment scenario and a normal comment scenario.
Photo original comment with editing seems to work
Now replying works as desired as well; had to add a case to the repliesController.