# Upgrading to 2.1 breaks my named routes

**URL:** <https://www.ruby-forum.com/t/upgrading-to-2-1-breaks-my-named-routes/140312>\
**Category:** Rails\
**Created:** [June 12, 2008, 9:26pm UTC](https://www.ruby-forum.com/t/upgrading-to-2-1-breaks-my-named-routes/140312 "2008-06-12T21:26:42Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![weyus](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/7ab992/32.png) [@weyus](https://www.ruby-forum.com/u/weyus)\
**Post date:** [June 12, 2008, 9:26pm UTC](https://www.ruby-forum.com/t/upgrading-to-2-1-breaks-my-named-routes/140312/1 "2008-06-12T21:26:42Z")

</div>

I just upgraded to 2.1 and attempted to log in to my application and  
when this line is reached in my login action:

```
  redirect_to(index_url)

```

I get the error

“wrong number of arguments (0 for 1)” [stack trace below].

Here’s my route:

```
 map.index 'index', :controller => 'e_simply', :action => 'index'

```

I found this very lengthy discussion on lighthouse about this bug:

[http://rails.lighthouseapp.com/projects/8994/tickets/22-default\_url\_options-is-being-ignored-by-named-route-optimisation](http://rails.lighthouseapp.com/projects/8994/tickets/22-default_url_options-is-being-ignored-by-named-route-optimisation)

I assume that this got fixed or no one would be able to use named  
routes.

What am I missing here?

Thanks,  
Wes

==== STACK TRACE ====

(eval):2:in `default_url_options' (eval):2:in `index\_url’  
app/controllers/application.rb:99:in `login' /Library/Ruby/Gems/1.8/gems/actionpack-2.1.0/lib/action_controller/base.rb:1162:in `send’  
/Library/Ruby/Gems/1.8/gems/actionpack-2.1.0/lib/action\_controller/base.rb:1162:in  
`perform_action_without_filters' /Library/Ruby/Gems/1.8/gems/actionpack-2.1.0/lib/action_controller/filters.rb:580:in `call\_filters’  
/Library/Ruby/Gems/1.8/gems/actionpack-2.1.0/lib/action\_controller/filters.rb:573:in  
`perform_action_without_benchmark' /Library/Ruby/Gems/1.8/gems/actionpack-2.1.0/lib/action_controller/benchmarking.rb:68:in `perform\_action\_without\_rescue’  
/Library/Ruby/Gems/1.8/gems/actionpack-2.1.0/lib/action\_controller/benchmarking.rb:68:in  
`perform_action_without_rescue' /Library/Ruby/Gems/1.8/gems/actionpack-2.1.0/lib/action_controller/rescue.rb:201:in `perform\_action\_without\_caching’  
/Library/Ruby/Gems/1.8/gems/actionpack-2.1.0/lib/action\_controller/caching/sql\_cache.rb:13:in  
`perform_action' /Library/Ruby/Gems/1.8/gems/activerecord-2.1.0/lib/active_record/connection_adapters/abstract/query_cache.rb:33:in `cache’  
/Library/Ruby/Gems/1.8/gems/activerecord-2.1.0/lib/active\_record/query\_cache.rb:8:in  
`cache' /Library/Ruby/Gems/1.8/gems/actionpack-2.1.0/lib/action_controller/caching/sql_cache.rb:12:in `perform\_action’  
/Library/Ruby/Gems/1.8/gems/actionpack-2.1.0/lib/action\_controller/base.rb:529:in  
`send' /Library/Ruby/Gems/1.8/gems/actionpack-2.1.0/lib/action_controller/base.rb:529:in `process\_without\_filters’  
/Library/Ruby/Gems/1.8/gems/actionpack-2.1.0/lib/action\_controller/filters.rb:569:in  
`process_without_session_management_support' /Library/Ruby/Gems/1.8/gems/actionpack-2.1.0/lib/action_controller/session_management.rb:130:in `process’  
/Library/Ruby/Gems/1.8/gems/actionpack-2.1.0/lib/action\_controller/base.rb:389:in  
`process' /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel/rails.rb:76:in `process’  
/Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel/rails.rb:74:in  
`synchronize' /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel/rails.rb:74:in `process’  
/Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:159:in  
`process_client' /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:158:in `each’  
/Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:158:in  
`process_client' /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:285:in `run’  
/Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:285:in  
`initialize' /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:285:in `new’  
/Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:285:in `run' /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:268:in `initialize’  
/Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:268:in `new' /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:268:in `run’  
/Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel/configurator.rb:282:in  
`run' /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel/configurator.rb:281:in `each’  
/Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel/configurator.rb:281:in  
`run' /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/bin/mongrel_rails:128:in `run’  
/Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/lib/mongrel/command.rb:212:in  
`run' /Library/Ruby/Gems/1.8/gems/mongrel-1.1.5/bin/mongrel_rails:281 /Library/Ruby/Gems/1.8/gems/activesupport-2.1.0/lib/active_support/dependencies.rb:502:in `load’  
/Library/Ruby/Gems/1.8/gems/activesupport-2.1.0/lib/active\_support/dependencies.rb:502:in  
`load' /Library/Ruby/Gems/1.8/gems/activesupport-2.1.0/lib/active_support/dependencies.rb:354:in `new\_constants\_in’  
/Library/Ruby/Gems/1.8/gems/activesupport-2.1.0/lib/active\_support/dependencies.rb:502:in  
`load' /Library/Ruby/Gems/1.8/gems/rails-2.1.0/lib/commands/servers/mongrel.rb:64 /Library/Ruby/Gems/1.8/gems/activesupport-2.1.0/lib/active_support/dependencies.rb:509:in `require’  
/Library/Ruby/Gems/1.8/gems/activesupport-2.1.0/lib/active\_support/dependencies.rb:354:in  
`new_constants_in' /Library/Ruby/Gems/1.8/gems/activesupport-2.1.0/lib/active_support/dependencies.rb:509:in `require’  
/Library/Ruby/Gems/1.8/gems/rails-2.1.0/lib/commands/server.rb:39  
-e:2:in `load’  
-e:2

---

<div class="post-metadata">

**Author:** ![weyus](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/7ab992/32.png) [@weyus](https://www.ruby-forum.com/u/weyus)\
**Post date:** [June 12, 2008, 10:06pm UTC](https://www.ruby-forum.com/t/upgrading-to-2-1-breaks-my-named-routes/140312/2 "2008-06-12T22:06:58Z")

</div>

On Thu, Jun 12, 2008 at 12:26 PM, Wes G.  
[removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> Here’s my route:  
> What am I missing here?  
> Change your default\_url\_options method to take an optional argument  
> instead of requiring one.

jeremy

---

<div class="post-metadata">

**Author:** ![weyus](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/7ab992/32.png) [@weyus](https://www.ruby-forum.com/u/weyus)\
**Post date:** [June 12, 2008, 10:18pm UTC](https://www.ruby-forum.com/t/upgrading-to-2-1-breaks-my-named-routes/140312/3 "2008-06-12T22:18:29Z")

</div>

Jeremy,

Thanks - I just got there independently by reading  
[http://dev.rubyonrails.org/ticket/10925](http://dev.rubyonrails.org/ticket/10925)

Funnily enough, I’m not even using the body of that default\_url\_options  
method. Sigh.

Thanks,  
Wes

---

<div class="post-metadata">

**Author:** ![weyus](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/7ab992/32.png) [@weyus](https://www.ruby-forum.com/u/weyus)\
**Post date:** [June 12, 2008, 10:26pm UTC](https://www.ruby-forum.com/t/upgrading-to-2-1-breaks-my-named-routes/140312/4 "2008-06-12T22:26:42Z")

</div>

Why can’t the call to default\_url\_options pass an empty hash instead of  
requiring that the developer make the options parameter optional?

Wes
