I just upgraded to 0.9.8, and now if our app throws an error the debug panel is displayed, despite the fact that we're
not calling render_with_facebook_debug_panel anywhere.  This is happening in production, as well as development, so
users are seeing our whole stack trace.  What's worse, our standard error handling (Exception Notification plugin) is
not notifying us of the errors so that we can fix.  How can prevent this behavior?

I'm trying to go through the latest release and see what changed, but haven't had much luck yet.  

Thanks!

P.S. I tried to submit this to the RFacebook forums as well, but the server is throwing 500 errors (again!).  This seems
to happen a lot.  Might consider moving the forum over to google groups.  Just a suggestion.

Date: 2008-08-09 18:26
Sender: Gerald Bauer

FYI: The official RFacebook forum/mailing list (including
the core RFacebook developers) is @
http://groups.google.com/group/rfacebook

If you want to get the issue resolved that's the best place
to start. Cheers.

Date: 2008-02-15 20:02
Sender: John Weathers

Hi,

I ran into the problem myself and developed a fix for it.
If you look at the RFacebook plugin code under the
lib/controller_extensions.rb you will find the culprit is the
method "rescue_action_with_rfacebook". Towards the
bottom of the file, an alias is set up that replaces the Rails
"rescue_action" method with this customized version
for RFacebook.

The only problem is that it doesn't care whether you are in production
or development mode - it always sends you to the debug panel
if you are in a canvas and an exception is caught.

I got around the problem by changing its check on line 403 from:
if in_facebook_canvas?

to:
if in_facebook_canvas? and ENV['RAILS_ENV'] == 'development'