× Joomla Facebook Connect support forum

Topic-icon wrong facebook status import

Active Subscriptions:

None
15 years 4 weeks ago #9853 by remington
hi,
when enabling the facebook status import after login it is importing the newest facebook stream entry but not the own/personal status message.
The topic has been locked.
Support Specialist
15 years 4 weeks ago #9890 by alzander
When we import the status, we're getting the latest message from a users stream. Depending on how the user's profile is configured for privacy, we may not be able to see their personal status message, only their public stream.

If your status is public, and isn't being pulled in, let us know. I think we can find an additional data permission you can add to the additional permissions request box, in JFBConnect, and when granted, you can get the private user stream. Of course, be careful with this as your site may make their private stream public, which may annoy some users.

If the above doesn't make sense, or you don't think I'm right, just let me know! The API call we use is:
developers.facebook.com/docs/reference/api/status/

Thanks!
The topic has been locked.
Active Subscriptions:

None
15 years 4 weeks ago #9891 by remington
hi alex,
first of all I don't use it but perhaps it's interesting for others.
Think about the status import:
right now you import the latest message from the stream and not a status - so if the last message is from one of your friends you're importing that. but now at jomsocial the imported message is shown as YOUR message - so this doesn't make sense ^^
facebook has different types (status message, usual message, link, video and so on..) - the jomsocial fb connect is importing the last status message from a user, so I know that it is possible and I think makes more sense - otherwise, with the actual way of jfbc, when your mom posts you happy birthday to the stream (last message) after importing this you wish it to yourself at jomsocial :D
The topic has been locked.
Support Specialist
15 years 4 weeks ago #9893 by alzander
Ahh.. I see what you're saying. We'll look into this and see what we're doing wrong. Thanks for the explanation of the issue, that will help us track it down.
The topic has been locked.
Active Subscriptions:

None
15 years 2 weeks ago #10323 by jfbillups
Hey Alex,
have you guys figured anything out with this yet... I was just going to post the same question. It does look a bit silly the way it stands at the moment.

kindest regards
The topic has been locked.
Active Subscriptions:

None
15 years 2 weeks ago #10326 by jfbillups
never mind, saw in another post that you are working on this ;)
The topic has been locked.
Support Specialist
15 years 2 weeks ago #10328 by alzander
Yes, we have a fix in development that we're testing. We'd love some feedback from you on the possible implementations though as there are some caveats and privacy things to take note of with this update.

Currently, we get the last entry in the user's feed. We'll all agree this is incorrect, but can be fixed/improved in a few ways.

* Updating to use Facebook's get status command:
This is a specific request to just get the user's last few status posts. This is easy from our standpoint as it's a few line code-fix (see below for the exact code if you want to implement it now). However, the following are 'problems' with it:
1) A new permission must be requested: user_status
We're very conservative with what we request, so we don't like adding new permissions to the approve application dialog. Obviously, this would only be requested if the "Pull FB status" setting is enabled, so it's (as with all of our permissions) a choice.
2) Once granted, the "user_status" will fetch all status messages, private or not. There is -no- way for us to tell if the status message is private. This is kinda annoying, and possibly really bad, depending on how you feel about that.
Bottom line: An extra permissions request and possibly private messages pulled in.
P.S. From what we can tell, this is what JomSocial is doing right now, so, for better or worse, it's actively being used. Confirmation of this behavior would be welcome.

* Update our current method to weed out 'non-status' items
This is the same as what we're doing right now, and would not require an extra permission request. Basically, Facebook returns the last 25 feed messages (probably configurable). We can parse these out the last status message posted and use it (instead of just the first, which is what we're doing now).
Pros: No private messages, no extra permissions request
Cons: May take 'slightly' longer (milli-seconds'ish) to get the extra feeds and sort through them, may not find a status post in the last 25 and therefore import nothing

Since you guys are the ones who noticed this, you're feedback will be structuring our choice, so let us know which of the poison above sounds better :)

To do the first one above, it's pretty simple right now. In /plugins/jfbcprofiles/jomsocial.php, at line ~200, change the line to:
$response = $this->jfbcLibrary->api('/me/statuses');
Then, in the Permissions tab in the JFBConnect Configuration, add the "user_status" to the extra permissions to request.

Hope this helps get you started, and sorry for the delay. We're working on a few updates to JFBConnect right now regarding JomSocial (in addition to a new VirtueMart plugin). Hoping to get a release out with this update and others by the end of this week or early in June.

Thanks,
Alex
The topic has been locked.
Support Specialist
15 years 2 weeks ago #10329 by alzander
2 more notes:
1) For parsing the feed, this may not be possible, just a thought though. The main problem we can see is that it's possible comments to other user's statuses would be pulled in, and we wouldn't be able to know the difference.. which would pull in 'random' statuses again.
2) We don't want to implement both, so saying "Do both with an option" isn't a great option :)
The topic has been locked.
Active Subscriptions:

None
15 years 2 weeks ago #10374 by SOJIVE
Replied by SOJIVE on topic wrong facebook status import
Thanks for all of your hard work Alex... :) looking forward to the new features.
cheers,
chris
The topic has been locked.
Active Subscriptions:

None
15 years 2 weeks ago #10376 by jfbillups
Alex, I think option 1 would be a good direction to go, I will try adding that code and give it try. Thanks again for your time.
The topic has been locked.