search for: facebook_url_rewrit

...s running in or outside a canvas, and fb_sig_in_canvas is not sent for ajax requests. My hacked together patch diff is below, sorry I didn''t have a chance to write tests or closely verify that my changes won''t break anything else. a/vendor/plugins/facebooker/lib/facebooker/rails/facebook_url_rewriting.rb b/vendor/plugins/facebooker/lib/facebooker/rails/facebook_url_rewriting.rb index 00b1e1d..e81a316 100644 --- a/vendor/plugins/facebooker/lib/facebooker/rails/facebook_url_rewriting.rb +++ b/vendor/plugins/facebooker/lib/facebooker/rails/facebook_url_rewriting.rb @@ -11,7 +11,7 @@ module ::Act...

As per my last email, I''m generating links to our app outside of Facebook. Sorry for the onslaught of emails on this. I do link generation in Publisher based code as well. What I''m finding is that the Facebooker UrlRewriter doesn''t get used in Publisher. This makes sense if we assume that Publisher can be used outside of an HTTP request, and things like the

...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 attached diff. Please let me know if you encounter any issues with this patch. Thanks, Shawn -------------- next part -------------- A non-text attachment was scrubbed... Name: diff.out Type: application/octet-stream Size: 750 bytes Desc: not available Url : http://rubyforge...

Running Rails 2.0.2, I get this error: ./script/../config/../vendor/plugins/facebooker/lib/facebooker/rails/facebook_url_rewriting.rb:29: undefined method `alias_method_chain'' for ActionController::UrlRewriter:Class (NoMethodError) from /usr/local/rubygems/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require'' from /usr/local/rubygems/lib/ruby/site_ruby/1.8/rubygems/custom_require...

...into account). I''m wondering if someone can comment on this more? I have a fix, but I''m not sure if it''s actually a fix, or just solving the symptom or improper use on my part, etc. What I did to fix it was change Facebooker''s UrlRewriter#link_to_canvas? (in facebook_url_rewriting.rb) to look like this: def link_to_canvas?(params, options) option_override = options[:canvas] if option_override == false # important to check for false. nil should use default behavior options[:only_path] = false RAILS_DEFAULT_LOGGER.debug "set options[:o...

...d > constant ActionController::AbstractRequest (NameError) > from /Users/user/Sites/iwr2/vendor/rails/activesupport/lib/ > active_support/dependencies.rb:80:in `const_missing'' > from /Users/user/Sites/iwr2/vendor/plugins/facebooker/lib/ > facebooker/rails/facebook_url_rewriting.rb:2 > from /opt/local/lib/ruby/site_ruby/1.8/rubygems/ > custom_require.rb:31:in `gem_original_require'' > from /opt/local/lib/ruby/site_ruby/1.8/rubygems/ > custom_require.rb:31:in `require'' > from /Users/user/Sites/iwr2/vendor/rails/ac...

The URLs for CSS/JS files are being rewritten to the address specified in the tunnel even when outside of the facebook canvas. Is anyone else having this problem?

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

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 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