search for: ittersum

Is ActionController''s redirect_to method broken by Facebooker? When I try to invoke it and execute through apps.facebook.com, I get a blank page returned, response code 200, no redirect. When I try to connect directly to the server (not through apps.fb), I get the infinite recursion error described minutes ago. Are any of you able to use redirect_to successfully, and if so, any ideas

Here''s the fix for Facebook apps that specify a controller in their callback URLs. First, set this variable in your environment scripts: ENV[''FACEBOOKER_CALLBACK_PATH''] = ''/controller'' # where controller is the name of your Facebook controller And then patch vendor/plugins/facebooker/lib/facebooker/rails/facebook_url_rewriting.rb as shown in the

Hi, I started with rfacebook but given the recent events figure its best to move over to facebooker. I have: 1.) Installed the facebooker plugin 2.) setup my facebook app (fbml/canvas) 3.) created a method on controller & view to handle initial request 4.) added "ensure_application_is_installed_by_facebook_user" to top off application.rb I am able to get to my landing page

Facebooker URL Rewriter stuff overloads ActionController::AbstractRequest.relative_url_root, causing a conflict with the plugin file_column and possibly other utilities. file_column constructs image URLs using the server host and relative_url_root This is not related to the sandbox patch I added to the rewriter. Facebooker overloaded relative_url_root before I touched it. I''ve

I''m trying to fetch a session (and other fb user variables from the session) at the start of my controller, so that all the actions in that controller can make use of it. Here''s the code: class FacebookController < ApplicationController ensure_application_is_installed_by_facebook_user fb_session = session[:facebook_session] # ... action functions here ... end

Hey, I am wondering if anyone has run into this issue before. I can''t seem to figure out what Facebook is doing. I have an application that only requires Facebook Authentication, the user doesn''t need to "add" the app. So at the top of my main controller I have class GettingStartedController < ApplicationController ensure_authenticated_to_facebook ......

Hey everybody. I''ve been using Facebooker on several projects over the last few months and feel like it is really starting to mature. I''d like to push towards a 1.0 release within the next month. I''d really like everybody''s input on what still needs to be done, as well as some help in wrapping things up. I''ve created a list of things that still

So I have an existing app & facebook app in same rails application, for now I have decided to go the route of creating a controller for facebook stuff (called FaceController). (setup is canvas, fbml) So I have: facebook config http://myurl:myport/face/ My controllers name is face, so I dont even need a manual route, for the landing page it works like a charm. but, when I try to make

I just wanted to contribute a quick-start page with details about how to get the Facebook session (for internal apps), how to get user info, set profile FBML, post to the news feed, etc. I could even send this as text, or I can add a page using the Radiant CMS if it''s not too cumbersome. I am also working with Dave Clements to augment the configuration options to make it easier for

Figured it out. I had commented the environment lines for testing something. So if anyone has that routing error, then you''re missing your config lines in the environment. :) Shawn ----- Begin forwarded message ----- From: Shawn Van Ittersum <svicalifornia at gmail.com> Date: Tue, 15 Jan 2008 13:19:12 -0800 To: facebooker-talk at rubyforge.org Subject: strange routing problem Now when I try to use facebooker, I get routing problems on all controllers except the default route: ActionController::RoutingError (no route found to ma...

Hi, I would like to generate a facebook call on behalf of a user to create a request to another user to install the app. Is there a way to do this without being in a fb_request_form? the use case is: Fred is creating a task, he assign it to a friend Sally , if Sally has already installed & setup my app, no problem, if she hasnt, I want to send an add request from Fred along with

If you are using facebooker as a plugin, you can now have all your configuration in one place, namely config/facebooker.yml. You can create this file with rake facebooker:setup. It is also generated when you install it as a plugin. It has a similar setup to database.yml with sections for each environment. You can also configure your ssh reverse tunnels. If you are upgrading, make sure to

Hey there! I would like the discussion to continue on how facebooker handles routes, as it appears that there is an unsolved issue. Mike, I read your recent reply involving setting facebook''s callback_path to the root of the rails app, and adding a route to catch all calls to the app root where canvas => true. I just want to point out this is counterintuitive to some folks and

Hey all, Been reading through all the old posts (and the docs) to familiarize myself but I still feel a bit lost. I''m on trunk and am having a bit of a hard time knowing where to start with the particular I''m trying to solve. So far, I''ve downloaded backgroundrb, done the basic rails setup, created my worker and started it using `script/backgroundrb start`.

I was connecting directly to my server to try to debug something. I disabled the ensure_application_is_installed_by_facebook_user check, then tried to connect to my index action. Got this error: SystemStackError in FacebookController#index stack level too deep RAILS_ROOT: script/../config/.. Application Trace | Framework Trace | Full Trace

Sorry, I won''t be able to send in the right diff just yet. If you want to check in my code, just change each instance of ENV[''FACEBOOKER_CALLBACK_PATH''] to ENV[''FACEBOOKER_SANDBOX_NAMESPACE'']. Thanks, Shawn

Now when I try to use facebooker, I get routing problems on all controllers except the default route: ActionController::RoutingError (no route found to match "facebook" with {:method=>:get}) This affects all app controllers, not just the facebook one, even app controllers with no Facebooker code. When I remove the facebooker plugin, the routing problems go away and the routing