Where to change codepage

Peter,
Sorry for the delayed response. I can't find the article you're posting about above. Can you link directly to that article so we can look into it further?

JFBConnect should be able to use the proper encoding of text from your article when posting to Facebook, but it doesn't seem to be doing so. We'll gladly look into why it's not, and possible solutions. Just need to see the page content first to test a little more.

Thanks,
Alex

Peter,
We've been testing and it turned out to be a very hard issue to understand and recreate. The issue only affects K2, which was hard to discover at first. Normal Joomla articles aren't affected. We think we finally found a good solution, and hopefully you can test it out and let us know if it helps.

Can you please edit the /plugins/content/jfbccontent/jfbccontent.php file. Around line 170, you'll see the following line of code:Change that "1" at the end to "2", so it looks like:There's another line around 185 that looks almost the same that requires the same change.

After you make the change, you'll need to use the Facebook URL Debug Tool to re-scan the page(s) from your site with the issue. Using the Debug Tool will show you what Facebook sees and also update their cache to make sure the old, wrong values, aren't used.

Please let us know if that helps fix your situation. We'll be putting this change into the next release of JFBConnect as it helps correct a separate issue as well, but would love to hear your feedback to know if it fixes this as well!

Thanks,
Alex

Peter,
Awesome! Very glad to hear that seems to be helping the situation. For all new articles/K2 items, the change should work immediately; for old K2 items, you'd need to wait for the Facebook cache to update or run the URL Debug Tool you've been using.

If you do run into other issues, just let us know. As mentioned above though, this fix will be included in the next release as well so hopefully you won't have to worry about it going forward.

Thanks,
Alex

Peter,
That's actually normal behavior for brand new content. Facebook will automatically scan the page by itself after it's view by a user, but it can take about 30 minutes to an hour or so for that to happen sometimes. Once Facebook's seen a lot of your content though, it will make the Facebook button work immediately. Basically, they don't want the Like button to work until they are sure the page isn't spam, malicious, etc. That happens by them automatically scanning the page, or knowing enough about your site's content to automatically 'know' any new pages should be good too.

Scanning it manually just speeds the process up, as you've found.

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

Thanks,
Alex