TuneUp bar is Empty
|
|
I’ve installed TuneUp for a Rails 2.1 app. Upon restart of the app I see the black TuneUp bar across the top of the page. However, it only contains the FiveRuns logo and the words FiveRuns TuneUp on the left. I have seen a demo of TuneUp and expected to see an area on the right which details how much time was spent in M/V/C, but this data is missing. There’s no text or anything on the right. I’ve looked in tuneup.log and see no errors—I do see a bunch of hits to TuneupController actions, but still no errors. I’m using Firefox 3.0.1 and MacOS X Leopard. The only thing non standard about my Rails app is that it does not use Prototype. I only use jQuery and do not have a noConflict() statement present. |
|
|
Hi Justin, |
|
|
I’m having the same problem, though my application does use prototype. The progress indicator on the right seems to work, but nothing displays thereafter. I have a ton of different javascript and css going on, but even after removing all of it except for the standard default rails stuff (proto + scriptaculous), I have the same issue. |
|
|
anyone? |
|
|
senihele and jbritten, |
|
|
Hey Eric, |
|
|
Look at your server log for your rails app, any exceptions may be logged there. I have this same issue, and my rails app log showed exceptions when it tried to get the tuneup data for display. My issue is that I am using jruby and there are current issues with jruby and tuneup. I do have it working after modifications which I will try to get up on GitHub. |
|
|
No exceptions logged. I’m not using jRuby. I just updated to TuneUp v. 0.8.13 and still no luck. |
|
|
I initially had this problem – i had to do 2 things |
|
|
I am also getting an empty bar, however, it is system-wide. I have tried it on many applications including some that don’t use any plugins or other gems. Also, I have tried using both the plugin and the gem with the same results. |
|
|
I’ve got the same thing going on with a recent install as zef. Tried it out with a blank app only using a single welcome controller and my error message is identical to zef’s above. |
|
|
I got a similar error: |
|
|
smeade, that worked for me too (thanks so much!) – I edited the file in the gem directory and all seems to be working just fine. Perhaps an update to the gem is in order guys? |
|
|
Yep, smeade’s fix worked for me as well. I running on ruby v1.8.7 and Rails 2.1 |
|
|
I can’t believe this hasn’t been patched yet… |
