This repository is private.
All pages are served over SSL and all pushing and pulling is done over SSH.
No one may fork, clone, or view it unless they are added as a member.
Every repository with this icon (
) is private.
Every repository with this icon (
This repository is public.
Anyone may fork, clone, or view it.
Every repository with this icon (
) is public.
Every repository with this icon (
rick (committer)
Mon May 05 23:41:33 -0700 2008
commit ee1d508a6bbdbfafb20516ebb4b452f1596f9ebe
tree 4bc2991c6819f50de9b44201033751baf9e27434
parent 04d85548608eb42f2d7071daa4661c5eac3a552a
tree 4bc2991c6819f50de9b44201033751baf9e27434
parent 04d85548608eb42f2d7071daa4661c5eac3a552a
... |
... |
|
... |
... |
|
... |
... |
|












Hi,
This change has caused me a bit of a headache to try and figure why some of my redirects to named routes had stopped working after an upgrade to Rails 2.1. I’m probably not the only one to be affected by this either, as changing the definition of a method which is frequently “duck-typed” is really not a good idea, especially when the error message is so cryptic.
For the record the error I received was this:
(eval):2:in `default_url_options’ (eval):2:in `admin_pages_url’Where admin_pages_url is my named route. The code in question in the controller was:
redirect_to admin_pages_urlEnsuring all definitions of default_url_options contain the options = nil part fixes this problem, but I really do not think this change was necessary.
Perhaps this can be reverted to the first version of this change here:
http://github.com/rails/rails/commit/6a6b4392c16c665eb713705f2b38e959a658eeef
Thanks, Sam Lown
Hi,
This change has caused me a bit of a headache to try and figure why some of my redirects to named routes had stopped working after an upgrade to Rails 2.1. I’m probably not the only one to be affected by this either, as changing the definition of a method which is frequently “duck-typed” is really not a good idea, especially when the error message is so cryptic.
For the record the error I received was this:
(eval):2:in `default_url_options’ (eval):2:in `admin_pages_url’Where admin_pages_url is my named route. The code in question in the controller was:
redirect_to admin_pages_urlEnsuring all definitions of default_url_options contain the options = nil part fixes this problem, but I really do not think this change was necessary.
Perhaps this can be reverted to the first version of this change here:
http://github.com/rails/rails/commit/6a6b4392c16c665eb713705f2b38e959a658eeef
Thanks, Sam Lown
Hi,
This change has caused me a bit of a headache to try and figure why some of my redirects to named routes had stopped working after an upgrade to Rails 2.1. I’m probably not the only one to be affected by this either, as changing the definition of a method which is frequently “duck-typed” is really not a good idea, especially when the error message is so cryptic.
For the record the error I received was this:
(eval):2:in `default_url_options’ (eval):2:in `admin_pages_url’Where admin_pages_url is my named route. The code in question in the controller was:
redirect_to admin_pages_urlEnsuring all definitions of default_url_options contain the options = nil part fixes this problem, but I really do not think this change was necessary.
Perhaps this can be reverted to the first version of this change here:
http://github.com/rails/rails/commit/6a6b4392c16c665eb713705f2b38e959a658eeef
Thanks, Sam Lown