Duplicate Status Updates

First, I just updated your subscriptions on our site by extending your JFBConnect subscription and closing your older JLinked subscription. That should have happened automatically before, but for some reason it didn't. I just wanted to let you know in case you got some update emals about your subscription.

As to your status import issue, JFBConnect should check to make sure that the status import being pulled in isn't the same update as the user's last update. It's possible it may match an older update though if newer ones have been made on site. Is that what's happening in your case? If so, can you tell me what extension you're integrating with (JomSocial or EasySocial) and we can investigate a better solution.

Thanks,
Alex

I'm sorry for the delay. We're looking into this, but don't have a cause as to why the issue is occurring right now. Looking at your image above, some of what I see is correct and some is not. Starting from the bottom:
* The bottom most post is the original one (at least as far as I can tell). This should obviously be imported.
* The middle post likely would be imported by JFBConnect normally because there's a different status update in between the bottom post and it.
* The top post is definitely incorrect because, for that user, their last status update looks to be identical to the one being imported.

The question I don't understand is why it's behaving like this. There is a check in our /plugins/socialprofiles/jomsocial/jomsocial.php file (in the setStatus function) to get the last status for a user and compare it to the status being imported. If they are the same, the new import should be skipped.

In our testing, we can't recreate this problem. Repeated logout and login attempts result in only 1 status update. The rest are ignored.

With that said, there's one other report of this problem . That user is using JomSocial 3.2.0.5, which is what we're testing with as well. Can you tell me what version of JomSocial you are using?

Again, sorry for the delays. We are investigating this and hope to have a solution soon.

Thanks,
Alex