Hello James,

I am really sorry for the delay of this reply as it is a weekend for us here. Hm, not really sure if I understand you here. Do you mean the link is being redirected to the home page when clicked on Facebook? Were you able to view the group pages as a guest on the site? The only way for this to actually work is when the page is accessible publicly. If it's not accessible by guests, you will face issues such as this.

I think that its silly to have a feature like this that only works if the website is set to public. It should still (in my opinion) use the groups avatar, group description, etc when sharing the group itself. Same for Events. For Streams it should possibly share the "sharers" avatar and the content of the stream regardless of if the link is set to public or registered.

The problem is none of the above happens when the menu id of the shared item is set to registered. It should still share all of the correct elements and linking. Not default to the website meta data and link to the homepage of the website.

Right now, if I visit a page that is set to registered and I am NOT logged in it re-directs me to login or register. Once I do either it takes me to the page I was initially trying to access. It should still follow this pattern but use correct content and linking.

James

This is not our requirements James, it's Facebook's and there is nothing really can be done. If you try to share a link that is not public to Facebook, you will hit the same issue.

When you share a link on Facebook, it uses it's own crawlers to crawl the contents of the site and this is why they introduced the debugger tool at http://developers.facebook.com/tools/debug

Ok, understood.

Basically the linking in Easysocial MUST be set to public for this to work properly. Can you tell me if that is ALL linking or only item specific?

James

Hello James,

Yep, you are absolutely right unfortunately Not something that we could control. I do wish and hope every day that Facebook would remove such limitations and trust 3rd party sites that the data which we send to them is legitimate but I believe their main concerns are over spams. Considering if they trust the data that is being sent to them, it might eventually lead to tons of spams.

Basically, any links shared on Facebook has to be public. If it isn't public, Facebook's crawler will try to follow the link and get the appropriate page when their crawler access your site. Also, you wouldn't be able to share the link at all if their crawler can't access your link.

Gotcha, thanks again.

I need to reconsider my linking. Do you have a best practice solution for this? Also, it would be good to include this data in the EasySocial documentation. I don't recall seeing it there.

Thanks,
James

Hello James,

If social sharing is a huge concern, I would strongly suggest you to have the menu's set to "public".

Last night, I changed all EasySocial menus I have to public, made sure the EasySocial Opengraph was enabled and give it another shot but no success. It pulled my profile photo while sharing a group and the main site meta data again. It's not detrimental at the moment as the site is in development but would like to look further into it and see if we can't determine the problem.

Any possibility it could be caused by JFBConnect's opengraph system?

James

Hello James,

Hm, that's odd. Can I have the URL that you are trying to share? Also, Is it possible for you to provide us with the back end and FTP access to your site to check on this issue?