Comments on: Upgrading to Rails 1.2 http://blog.spotstory.com/2007/04/19/upgrading-to-rails-12/ Mon, 19 May 2008 23:03:19 +0000 http://wordpress.org/?v=2.8.4 hourly 1 By: hervalicio.us » User expected, got User? http://blog.spotstory.com/2007/04/19/upgrading-to-rails-12/comment-page-1/#comment-8804 hervalicio.us » User expected, got User? Mon, 19 May 2008 23:03:19 +0000 http://blog.spotstory.com/2007/04/19/upgrading-to-rails-12/#comment-8804 [...] By far one of the most annoying and unhelpful messages on Rails ever. the “User expected, got User” message tends to pop up now and then when using plugins such as acts_as_commentable or acts_as_taggable, that define models on the vendor/plugins. The solution, as pointed out by the localhost:3000 blog (nice blog name, I must say ;)), is moving any models that relate to models on your application to your own /models folder. The reason behind the problem is that the libs don’t get reloaded on each server request, whereas the models are (some thoughts on things that reload here). So theoretically, plugins that define models inside them are a bad bad practice. There’s another less intrusive way to make the plugins workm though: you can add the plugins on the ‘reloadable path’, as explained on spotstory: [...] [...] By far one of the most annoying and unhelpful messages on Rails ever. the “User expected, got User” message tends to pop up now and then when using plugins such as acts_as_commentable or acts_as_taggable, that define models on the vendor/plugins. The solution, as pointed out by the localhost:3000 blog (nice blog name, I must say ;)), is moving any models that relate to models on your application to your own /models folder. The reason behind the problem is that the libs don’t get reloaded on each server request, whereas the models are (some thoughts on things that reload here). So theoretically, plugins that define models inside them are a bad bad practice. There’s another less intrusive way to make the plugins workm though: you can add the plugins on the ‘reloadable path’, as explained on spotstory: [...]

]]> By: hervalicio.us » Blog Archive » User expected, got User? http://blog.spotstory.com/2007/04/19/upgrading-to-rails-12/comment-page-1/#comment-8680 hervalicio.us » Blog Archive » User expected, got User? Mon, 12 May 2008 02:56:57 +0000 http://blog.spotstory.com/2007/04/19/upgrading-to-rails-12/#comment-8680 [...] Sem dúvida uma das mensagens mais irritantes que já tive o desprazer de encontrar nas andanças pelo Rails, a infame “User expected, got User” tende a aparecer, quando se utilizam plugins como o acts_as_commentable ou o acts_as_taggable, que definem Models dentro do diretório vendor/plugins. A solução, como apontado pelo blog localhost:3000 blog (belo nome para um blog, diga-se de passagem ;)), é simples (apesar de meio “xunxo”): basta mover os models do plugin para o diretório apps/models de sua aplicação. A razão por trás do problema é que as libs (e o conteúdo do diretório vendor) não são carregadas a cada request, quando utilizando o modo “development”, diferentemente de todo o conteúdo do /app . Teoricamente, definir models dentro de plugins é uma má pratica, e deve ser evitado. Vale notar que o problema não acontece em modo production, onde os models não são recarregados o tempo todo. Existe ainda uma maneira menos intrusiva de adicionar os plugins ao ‘reloadable path’, fazendo com que eles sejam recarregados junto da aplicação, conforme explicado neste link: [...] [...] Sem dúvida uma das mensagens mais irritantes que já tive o desprazer de encontrar nas andanças pelo Rails, a infame “User expected, got User” tende a aparecer, quando se utilizam plugins como o acts_as_commentable ou o acts_as_taggable, que definem Models dentro do diretório vendor/plugins. A solução, como apontado pelo blog localhost:3000 blog (belo nome para um blog, diga-se de passagem ;)), é simples (apesar de meio “xunxo”): basta mover os models do plugin para o diretório apps/models de sua aplicação. A razão por trás do problema é que as libs (e o conteúdo do diretório vendor) não são carregadas a cada request, quando utilizando o modo “development”, diferentemente de todo o conteúdo do /app . Teoricamente, definir models dentro de plugins é uma má pratica, e deve ser evitado. Vale notar que o problema não acontece em modo production, onde os models não são recarregados o tempo todo. Existe ainda uma maneira menos intrusiva de adicionar os plugins ao ‘reloadable path’, fazendo com que eles sejam recarregados junto da aplicação, conforme explicado neste link: [...]

]]> By: skwpspace – Rails 2.0 dependency system problems http://blog.spotstory.com/2007/04/19/upgrading-to-rails-12/comment-page-1/#comment-6925 skwpspace – Rails 2.0 dependency system problems Wed, 27 Feb 2008 22:31:16 +0000 http://blog.spotstory.com/2007/04/19/upgrading-to-rails-12/#comment-6925 [...] http://blog.spotstory.com/2007/04/19/upgrading-to-rails-12/ [...] [...] http://blog.spotstory.com/2007/04/19/upgrading-to-rails-12/ [...]

]]> By: Brian McNaboe http://blog.spotstory.com/2007/04/19/upgrading-to-rails-12/comment-page-1/#comment-6425 Brian McNaboe Mon, 11 Feb 2008 19:00:33 +0000 http://blog.spotstory.com/2007/04/19/upgrading-to-rails-12/#comment-6425 I'm seeing this 'User expected, got User' in Rails 2.0.2 now (and wasn't see it in 1.2.3). I also run into what appears to be the same problem when using the spec_server. Putting the fix above in my development.rb file seems to have resolved the problem in development, but not for the spec_server (even when placed in environment.rb). I'll need to dig deeper into that. Thanks for saving me a ton of time! I’m seeing this ‘User expected, got User’ in Rails 2.0.2 now (and wasn’t see it in 1.2.3). I also run into what appears to be the same problem when using the spec_server.

Putting the fix above in my development.rb file seems to have resolved the problem in development, but not for the spec_server (even when placed in environment.rb). I’ll need to dig deeper into that.

Thanks for saving me a ton of time!

]]> By: » links for 2007-07-25 | Paul Cowles http://blog.spotstory.com/2007/04/19/upgrading-to-rails-12/comment-page-1/#comment-2444 » links for 2007-07-25 | Paul Cowles Tue, 28 Aug 2007 21:58:39 +0000 http://blog.spotstory.com/2007/04/19/upgrading-to-rails-12/#comment-2444 [...] spotstory » Upgrading to Rails 1.2 gotchas for the 1.1 to 1.2 rails upgrade (tags: rails ruby) [...] [...] spotstory » Upgrading to Rails 1.2 gotchas for the 1.1 to 1.2 rails upgrade (tags: rails ruby) [...]

]]> By: User expected, got User? http://blog.spotstory.com/2007/04/19/upgrading-to-rails-12/comment-page-1/#comment-1305 User expected, got User? Sat, 07 Jul 2007 17:31:30 +0000 http://blog.spotstory.com/2007/04/19/upgrading-to-rails-12/#comment-1305 [...] Sem dúvida uma das mensagens mais irritantes que já tive o desprazer de encontrar nas andanças pelo Rails, a infame “User expected, got User” tende a aparecer, quando se utilizam plugins como o acts_as_commentable ou o acts_as_taggable, que definem Models dentro do diretório vendor/plugins. A solução, como apontado pelo blog localhost:3000 blog (belo nome para um blog, diga-se de passagem ;)), é simples (apesar de meio “xunxo”): basta mover os models do plugin para o diretório apps/models de sua aplicação. A razão por trás do problema é que as libs (e o conteúdo do diretório vendor) não são carregadas a cada request, quando utilizando o modo “development”, diferentemente de todo o conteúdo do /app . Teoricamente, definir models dentro de plugins é uma má pratica, e deve ser evitado. Vale notar que o problema não acontece em modo production, onde os models não são recarregados o tempo todo. Existe ainda uma maneira menos intrusiva de adicionar os plugins ao ‘reloadable path’, fazendo com que eles sejam recarregados junto da aplicação, conforme explicado neste link: [...] [...] Sem dúvida uma das mensagens mais irritantes que já tive o desprazer de encontrar nas andanças pelo Rails, a infame “User expected, got User” tende a aparecer, quando se utilizam plugins como o acts_as_commentable ou o acts_as_taggable, que definem Models dentro do diretório vendor/plugins. A solução, como apontado pelo blog localhost:3000 blog (belo nome para um blog, diga-se de passagem ;)), é simples (apesar de meio “xunxo”): basta mover os models do plugin para o diretório apps/models de sua aplicação. A razão por trás do problema é que as libs (e o conteúdo do diretório vendor) não são carregadas a cada request, quando utilizando o modo “development”, diferentemente de todo o conteúdo do /app . Teoricamente, definir models dentro de plugins é uma má pratica, e deve ser evitado. Vale notar que o problema não acontece em modo production, onde os models não são recarregados o tempo todo. Existe ainda uma maneira menos intrusiva de adicionar os plugins ao ‘reloadable path’, fazendo com que eles sejam recarregados junto da aplicação, conforme explicado neste link: [...]

]]> By: Robert http://blog.spotstory.com/2007/04/19/upgrading-to-rails-12/comment-page-1/#comment-1127 Robert Wed, 20 Jun 2007 00:17:14 +0000 http://blog.spotstory.com/2007/04/19/upgrading-to-rails-12/#comment-1127 Very helpful. We also got stung by a discrepancy between the way 1.1.6 and 1.2.3 handles updates to a has_one relationship. When updating the parent, 1.1.6 updates the child, while 1.2.3 does not. See example here: http://dev.rubyonrails.org/ticket/8673 Very helpful.

We also got stung by a discrepancy between the way 1.1.6 and 1.2.3 handles updates to a has_one relationship. When updating the parent, 1.1.6 updates the child, while 1.2.3 does not. See example here:

http://dev.rubyonrails.org/ticket/8673

]]> By: nick http://blog.spotstory.com/2007/04/19/upgrading-to-rails-12/comment-page-1/#comment-986 nick Thu, 07 Jun 2007 03:25:12 +0000 http://blog.spotstory.com/2007/04/19/upgrading-to-rails-12/#comment-986 Thanks for the explanation. I've run into this problem now in trying to cache database 'constants' from a file in the lib directory. This has been the most useful description of the problem I've found yet. Thanks for the explanation. I’ve run into this problem now in trying to cache database ‘constants’ from a file in the lib directory. This has been the most useful description of the problem I’ve found yet.

]]> By: ’s blog » links for 2007-06-01 http://blog.spotstory.com/2007/04/19/upgrading-to-rails-12/comment-page-1/#comment-867 ’s blog » links for 2007-06-01 Fri, 01 Jun 2007 10:18:37 +0000 http://blog.spotstory.com/2007/04/19/upgrading-to-rails-12/#comment-867 [...] spotstory » Upgrading to Rails 1.2 (tags: rails) [...] [...] spotstory » Upgrading to Rails 1.2 (tags: rails) [...]

]]> By: Googletron::new(’en’) » Blog Archive » User expected, got User? http://blog.spotstory.com/2007/04/19/upgrading-to-rails-12/comment-page-1/#comment-443 Googletron::new(’en’) » Blog Archive » User expected, got User? Tue, 08 May 2007 02:38:50 +0000 http://blog.spotstory.com/2007/04/19/upgrading-to-rails-12/#comment-443 [...] By far one of the most annoying and unhelpful messages on Rails ever. the “User expected, got User” message tends to pop up now and then when using plugins such as acts_as_commentable or acts_as_taggable, that define models on the vendor/plugins. The solution, as pointed out by the localhost:3000 blog (nice blog name, I must say ;)), is moving any models that relate to models on your application to your own /models folder. The reason behind the problem is that the libs don’t get reloaded on each server request, whereas the models are (some thoughts on things that reload here). So theoretically, plugins that define models inside them are a bad bad practice. There’s another less intrusive way to make the plugins workm though: you can add the plugins on the ‘reloadable path’, as explained on spotstory: [...] [...] By far one of the most annoying and unhelpful messages on Rails ever. the “User expected, got User” message tends to pop up now and then when using plugins such as acts_as_commentable or acts_as_taggable, that define models on the vendor/plugins. The solution, as pointed out by the localhost:3000 blog (nice blog name, I must say ;)), is moving any models that relate to models on your application to your own /models folder. The reason behind the problem is that the libs don’t get reloaded on each server request, whereas the models are (some thoughts on things that reload here). So theoretically, plugins that define models inside them are a bad bad practice. There’s another less intrusive way to make the plugins workm though: you can add the plugins on the ‘reloadable path’, as explained on spotstory: [...]

]]>