On the topic of bugfixes - care to comment on http://rubyforge.org/tracker/index.php?func=detail&aid=15869&group_id=3607&atid=13796 ?

And thanks for your great work! It’s been nice to have a rails plugin for the stuff as well…

Yea, these are definitely things on my list to get done…things have been super busy for me lately. I plan on getting some serious feature addition and bugfixes in the next few weeks.

“On the feature-request end, it would be nice to be able to authenticated a user who both isn’t in an iframe AND isn’t in the canvas. Again, I had to upload a file, and was hoping to maintain facebook sessions, as all the necessary information is posted back, but your first check is to see if they’re in an iframe first… and if not, ignore auth information. If there was a nice way of overriding this… I’d hug you.”

I have also spent the past few weeks toying around with a facebook application. The major problem I have run into is when I try to upload a photo to facebook. Primarily I am directing all requests/form submissions to “apps.facebook.com/myapp/foo.” With this approach, there are no issues with the session. However, when attempting to upload an image, I must submit the “multipart/form-data” form directly back to my server and the session is lost! This is a royal pain in the ass and I am wondering if you have a workaround!

Basically, I am trying to take a user image posted by a multipart form and upload it directly to facebook in my controller. Maybe I’m going about this all wrong, but one more headbutt and this monitor will be fresh out of pixels. Any help would be much appreciated.

Cheers,
Brian

Glad to hear that RFacebook is mostly working in Rails 2.0. Things have been pretty busy for me so I haven’t had a lot of time to stay on top of that stuff, so any fixes you can make to the URL code is much appreciated

I’ve been hearing more reports of problems with the Jypsie forums. I’m planning on revamping my personal site end of December, so at that time I’ll look into forum alternatives (or perhaps contact JDG to see whats up with Jypsie these days).

First off, the Jypsie site is fux0red… for the last few days, it seems I’ve been inadvertently crashing the site; I would attempt to post a forum topic only to be served with a 500 error. But it doesn’t stop there, because after this first 500 error, the entire site of Jypsie.com just serves 500s! Happened yesterday and happened today. In fact, the site is still down from when I tried to post a topic about half an hour ago. Also, the forum lacks a search feature. May I suggest linking up to a more reliable and usable forum?

Second, yesterday I installed Rails 2.0 RC1 and started a new Facebook app with RFacebook. Congratulations, just about everything seems to be in working order! The only thing I’ve found that doesn’t work anymore is the URL code; so far, attempting to use a named route gives me an absolute URL to the app’s hosted server rather than its respective canvas URL. Such a break isn’t unexpected, since Rails 2.0 has changed the way it handles named routes, but I suspect it should be an easy fix. I’ll probably try and work it out myself rather than wait for an update, and I’ll be sure to send you the code if I’m successful in the endeavor.

Thanks again, I’m sure this project keeps you plenty busy, just know we developers are very grateful for your work!

Yea, sorry abou tht mock_ajax deprecation + behavior change - I had forgotten that I hadn’t actually released a version with just the notice.

If you could submit your feature request on Rubyforge, that would be great. Things have been very busy these days and it makes it a lot easier to go to one place than to dig through blog comments + jypsie forums + rubyforge.

Glad to hear things are working out so well!

First, thanks for such an awesome plugin. I was doing Facebook work with CodeIgniter before… not so much fun.

One lil’ bit: When you upgraded to 0.9.7, you changed :mock_ajax to :full_callback. While I appreciate this behavior (as I was using it for uploading a file to my server, since FB doesn’t proxy FILE info), when you deprecate something, you typically don’t remove the behavior in the same release. When I went to deploy this morning, :mock_ajax was no longer working, and I freaked out for about ten seconds before I saw your deprecation warning in my logs. Working beautifully now, however.

On the feature-request end, it would be nice to be able to authenticated a user who both isn’t in an iframe AND isn’t in the canvas. Again, I had to upload a file, and was hoping to maintain facebook sessions, as all the necessary information is posted back, but your first check is to see if they’re in an iframe first… and if not, ignore auth information. If there was a nice way of overriding this… I’d hug you.

Anyhow… thanks again. S’been a joy.