# AJAX not Working in Production

**URL:** <https://www.ruby-forum.com/t/ajax-not-working-in-production/150054>\
**Category:** Rails\
**Created:** [October 2, 2008, 10:52pm UTC](https://www.ruby-forum.com/t/ajax-not-working-in-production/150054 "2008-10-02T22:52:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![amin1426](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/4da419/32.png) [@amin1426](https://www.ruby-forum.com/u/amin1426)\
**Post date:** [October 2, 2008, 10:52pm UTC](https://www.ruby-forum.com/t/ajax-not-working-in-production/150054/1 "2008-10-02T22:52:36Z")

</div>

I’m having an issue in my Prod environment where some sets of Ajax code  
are not working correctly

Going to [HugeDomains.com](http://www.jbcmanagement.com/test_case/new#) and clicking Add a  
Step executes the following code:

\<%= link\_to\_function "Add a Step" do |page| page.insert\_html :bottom, :chaka, :partial =\> 'test\_script', :object =\> TestScript.new end%\>

In my development environment, this code works correctly, it adds an  
additional data entry line for an additional test step on the page.  
In production I am not getting any action.

The only indication I see of an error is in my production.log :

ActionController::RoutingError (No route matches  
“/javascripts/effects.js” with {:method=\>:get}):

effects.js exists in my Project/public/javascripts folder.

Here is my routes.rb

map.connect ‘:controller/:action/:id’  
map.connect ‘:controller/:action/:id.:format’

---

<div class="post-metadata">

**Author:** ![amin1426](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/4da419/32.png) [@amin1426](https://www.ruby-forum.com/u/amin1426)\
**Post date:** [October 3, 2008, 4:30pm UTC](https://www.ruby-forum.com/t/ajax-not-working-in-production/150054/2 "2008-10-03T16:30:25Z")

</div>

That’s weird because if you debug it with Firebug you can see how  
effects.js is loaded.

On Oct 2, 10:56 pm, Frederick C. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)