On 14 Jan 2009, at 18:38, summea wrote:
> > Hi all, > > My shared hosting provider updated Rails last week with no prior > warning... so I've spent the last week finding what's been broken in > my Rails app and finding out how to fix those problems. > > I've noticed that parts of the app that still have some type of error > are parts of the app that are from the original app version. Other > parts of the app that do work were made in a slightly newer version of > Rails (though not with the current version that I was upgraded to > unexpectedly.) There doesn't seem to be a difference in how I wrote > (or generated,) the code for the models, views, and controllers... > but somehow one side works (the slightly newer Rails-created MVC) > while the other side (the older, original MVC) do not work. > > Is there a way (that I've missed,) whereby I can refresh all of the > MVC for my app so that it's as if I had generated MVC files in the new > Rails? I remember reading about a way to do something like that in > the past in Rails, but I can't remember what I'm searching for. Any > idea? Well you could use the generators to regenerate all that jazz but it would overwrite everything you've done. You'd probably learn more by working out what the differences are and fixing them. Fred > > > Thanks, > Andy > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
