Topic-icon {actor} Showing up in JomSocial Stream from FB Wall Post

Active Subscriptions:

None
Hi Guys,

First, AWESOME job!! This in combination with JomSocial works great overall!!

I do have one issue. On the imported wall posts from FaceBook the tag {actor} is showing up in front. I searched through the forums for assistance and could find nothing that solved it.

Also, is there a way that the FB Stream automatically updates on my site without the user having to log off and then back on again?

Thanks in advance,
Joe
907CrossFit.com
The topic has been locked.
Support Specialist
Joe,
The {actor} tag is an issue with JomSocial itself. My understanding is that JomSocial 2.8.3 fixed it, whereas JomSocial 2.8.0-2.8.2 had the problem. Let me know what version of JomSocial you're using and we can investigate more if necessary.

As for updating the stream automatically, no, we can't currently do that. It is possible for Facebook to notify JFBConnect when a user's status updates, but we don't have support for fetching that outside of the login.. yet. It's something we have plans to implement over the next few releases.

Hope that all helps, but if you need anything else, just let us know.

Thanks,
Alex
The topic has been locked.
Active Subscriptions:

None
I just updated from JomSocial 2.6 to 2.8.3 and the {actor} tag is still showing up:
miraargentina.com/comunidad
The topic has been locked.
Support Specialist
Ludwig,
Thanks for pointing that out. JomSocial's docs for the new Stream API aren't complete yet, so it's difficult to see what we should be doing now that things have changed in 2.8, as you can see:
documentation.jomsocial.com/wiki/Stream_API_v2

From what we can tell, in 2.8.3, the 'fix' they had for the {actor} issue was to simply change their language string for the case where that tag was being used. That's my only suggestion as well for now. To do so, edit the /plugins/socialprofiles/jomsocial/jomsocial.php file. Around line 67, you'll see:
$act->title = "{actor} " . $socialStatus;
Change that to:
$act->title = " " . $socialStatus;
That will definitely get rid of the {actor} tag and should hopefully make the problem go away without any other bad effects.

We'll likely have to release an updated profile plugin to detect JomSocial 2.8 vs 2.6 and lower and remove that tag when it's there.

Please let us know how it goes, and thanks for the feedback,
Alex
The topic has been locked.
Active Subscriptions:

None
Thanks, Alex. I tried with a test post and that fixed it. Typical JomSocial releasing unfinished software. At least I was able to delete my test post. During the whole life of JS 2.6 the delete activity bug was never fixed! LOL
The topic has been locked.
Support Specialist
Glad to hear that got you going. JomSocial is definitely a complex extension. We get ahead of ourselves with features that aren't fully documented as well, so I can't fault them for that.. it's tough being at the bleeding edge and keeping everything up to date. It does make things a little more difficult for us right now though to make sure we integrate well.

Again though, glad that worked, and we'll be looking into an update of the JomSocial Profile Plugin to remove that {actor} tag when in JomSocial 2.8+

Alex
The topic has been locked.
Alex, even in JS v2.8.4 this is not resolved except within Jomsocial. I find that if new stream activity is created inside Jomsocial, there is no problem. However, if I login via JFBC, even in JS v2.8.4 that tag appears with my imported status.

There is a thread here describing the current perspective of JS:
www.jomsocial.com/forum/installation/396...-in-activity-streams

They essentially feel it's the result of 3rd party add-ons. My informal testing seems to support that based on the fact I only get them when using JFBC.

There is a query from another thread that describes a query to run that removes existing tags:
www.jomsocial.com/forum/jomsocial-2-8-be...or-tag-in-activities

I will try your below patch, but I think a more permanent solution is in order.

Thanks for the great extensions!
The topic has been locked.
Support Specialist
Steve,
We agree that the patch above isn't something everyone should have to do. We commented that "We'll likely have to release an updated profile plugin to detect JomSocial 2.8 vs 2.6 and lower and remove that tag when it's there. ". We just haven't made that release yet which will detect the version of JomSocial being used and remove the {actor} tag when in JS 2.8+. Until then, we'd recommend removing the {actor} from the file we mentioned above. The next release of the JomSocial plugin will definitely have this built in, and it should be out later this month.

Hope that helps explain, and thanks for the feedback,
Alex
The topic has been locked.

alzander wrote: Steve,
We agree that the patch above isn't something everyone should have to do. We commented that "We'll likely have to release an updated profile plugin to detect JomSocial 2.8 vs 2.6 and lower and remove that tag when it's there. ". We just haven't made that release yet which will detect the version of JomSocial being used and remove the {actor} tag when in JS 2.8+. Until then, we'd recommend removing the {actor} from the file we mentioned above. The next release of the JomSocial plugin will definitely have this built in, and it should be out later this month.

Hope that helps explain, and thanks for the feedback,
Alex

Yessir! I didn't mean to sound obnoxious. I just had the impression it was kind of a "we're not quite sure it's a problem" from reading the thread so I wanted to add my experience.

Thanks for the great work!
The topic has been locked.
Support Specialist
Wasn't obnoxious at all. It is a partial not sure of the solution. The fix above does work, but JomSocial's docs recommend using the new Stream V2 API.. but there's no documentation for that API.

So, in the near future, we'll be putting out a minor release that simply checks for JS 2.8+ and doesn't use the {actor} tag in that case. In the longer term, we'll need to investigate and understand the new Stream V2 API and decide if we need to be using that or not.

Hope that's a lot more clear and concise. Your experience and feedback is always welcome!

Thanks,
Alex
The topic has been locked.