Tuneup bar is not getting displayed -

11 Nov, 2008 12:14 PM

Karthik 1 post(s)

We are using the following configurations:
1. latest version of Fiveruns Tuneup gem
2. Rails 2.1
3. OS: Fedora 8
4. Browser: Firefox latest version
We are not able to see the Fiveruns Tuneup bar in our application pages. When we checked the ‘View Source’ of the page in firefox, we are able to see the tuneup javascripts loaded. Also there is no error in the ‘tuneup.log’.
We see the following error in the development log.
ActionController::RoutingError (No route matches ”/tuneup/sandbox” with {:method=>:get}):
/vendor/rails/actionpack/lib/action_controller/routing/recognition_optimisation.rb:67:in `recognize_path’
Please help me in fixing this.
Thanks in advance…

12 Nov, 2008 03:51 PM

Doug 1 post(s)

I’m getting the same problem on Mac OS X using Rails 2.1.1 and 2.1.2.

14 Nov, 2008 06:01 PM

Rachel G Administator 50 post(s)

We are looking into this issue now. I will post here when we have this resolved.
Thanks,
Rachel

14 Nov, 2008 08:47 PM

Rachel G Administator 50 post(s)

Hi Karthik and Doug,
We do have a work around for the routing problem. If you can rename the fiveruns_tuneup plugin in your /vendor/plugins directory to zfiveruns_tuneup the TuneUp bar should show up.
We use alias_method_chain for the routing, but it looks like there is another plugin that is monkey-patched, so our plugin will need to load last.
Thanks,
Rachel

17 Nov, 2008 07:08 AM

Ayyanar 3 post(s)

Hi Rachel,
We configure config.gem in the environment.rb. We don’t install as plugin. We use rails 2.1.0.
Kindly let me know how to install the fiveruns as plugin to fix the sandbox error

18 Nov, 2008 10:24 PM

Joe C 2 post(s)

Hi,
I’m having this same problem under:
- rails 2.1.1
- leopard 10.5
I followed the setup instructions verbatim, and nothing happened. I also don’t use the plugin but per the rails 2.1 setup instruction use the config.gem method

19 Nov, 2008 02:49 PM

Joe C 2 post(s)

Got it working, the doctype tag had a carriage return in the middle.
Changed:
<!DOCTYPE html PUBLIC ”-//W3C//DTD XHTML 1.0 Transitional//EN”
“http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd”>
To:
<!DOCTYPE html PUBLIC ”-//W3C//DTD XHTML 1.0 Transitional//EN” “http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd”>
And everything started working.

12 Dec, 2008 11:53 PM

aarontav 2 post(s)

Not sure how the doctype tag could have anything to do with the routes, but that doesn’t fix this problem for me. Still getting
ActionController::RoutingError (No route matches ”/tuneup/sandbox” with {:method=>:get})
Another user running Rails 2.1 and this gem deployment doesn’t work.

12 Dec, 2008 11:57 PM

aarontav 2 post(s)

As a quick two cent solution, in my case it is newrelic conflicting with fiveruns. Removing newrelic_rpm allows fiveruns to work. My guess is they each use the same kind of hooking, and newrelic got loaded last.

16 Dec, 2008 10:43 PM

Rachel G Administator 50 post(s)

Hi All,
NewRelic has released a new gem and so now, both TuneUp and NewRelic can run in the same environment. If you update your NewRelic gem, you should not see this problem any more.
Thanks,
Rachel

11 Nov, 2008 12:14 PM Karthik 1 post(s)	We are using the following configurations: 1. latest version of Fiveruns Tuneup gem 2. Rails 2.1 3. OS: Fedora 8 4. Browser: Firefox latest version We are not able to see the Fiveruns Tuneup bar in our application pages. When we checked the ‘View Source’ of the page in firefox, we are able to see the tuneup javascripts loaded. Also there is no error in the ‘tuneup.log’. We see the following error in the development log. ActionController::RoutingError (No route matches ”/tuneup/sandbox” with {:method=>:get}): /vendor/rails/actionpack/lib/action_controller/routing/recognition_optimisation.rb:67:in `recognize_path’ Please help me in fixing this. Thanks in advance…

12 Nov, 2008 03:51 PM Doug 1 post(s)	I’m getting the same problem on Mac OS X using Rails 2.1.1 and 2.1.2.

14 Nov, 2008 06:01 PM Rachel G Administator 50 post(s)	We are looking into this issue now. I will post here when we have this resolved. Thanks, Rachel

14 Nov, 2008 08:47 PM Rachel G Administator 50 post(s)	Hi Karthik and Doug, We do have a work around for the routing problem. If you can rename the fiveruns_tuneup plugin in your /vendor/plugins directory to zfiveruns_tuneup the TuneUp bar should show up. We use alias_method_chain for the routing, but it looks like there is another plugin that is monkey-patched, so our plugin will need to load last. Thanks, Rachel

17 Nov, 2008 07:08 AM Ayyanar 3 post(s)	Hi Rachel, We configure config.gem in the environment.rb. We don’t install as plugin. We use rails 2.1.0. Kindly let me know how to install the fiveruns as plugin to fix the sandbox error

18 Nov, 2008 10:24 PM Joe C 2 post(s)	Hi, I’m having this same problem under: - rails 2.1.1 - leopard 10.5 I followed the setup instructions verbatim, and nothing happened. I also don’t use the plugin but per the rails 2.1 setup instruction use the config.gem method

19 Nov, 2008 02:49 PM Joe C 2 post(s)	Got it working, the doctype tag had a carriage return in the middle. Changed: <!DOCTYPE html PUBLIC ”-//W3C//DTD XHTML 1.0 Transitional//EN” “http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd”> To: <!DOCTYPE html PUBLIC ”-//W3C//DTD XHTML 1.0 Transitional//EN” “http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd”> And everything started working.

12 Dec, 2008 11:53 PM aarontav 2 post(s)	Not sure how the doctype tag could have anything to do with the routes, but that doesn’t fix this problem for me. Still getting ActionController::RoutingError (No route matches ”/tuneup/sandbox” with {:method=>:get}) Another user running Rails 2.1 and this gem deployment doesn’t work.

12 Dec, 2008 11:57 PM aarontav 2 post(s)	As a quick two cent solution, in my case it is newrelic conflicting with fiveruns. Removing newrelic_rpm allows fiveruns to work. My guess is they each use the same kind of hooking, and newrelic got loaded last.

16 Dec, 2008 10:43 PM Rachel G Administator 50 post(s)	Hi All, NewRelic has released a new gem and so now, both TuneUp and NewRelic can run in the same environment. If you update your NewRelic gem, you should not see this problem any more. Thanks, Rachel

Tuneup bar is not getting displayed

Voices