Joomblog and Open Graph

You should be able to do some integration, like posting to a user's timeline when they read an article. We don't have an Open Graph plugin for Joomblog which would allow more advanced things, like posting when a user creates a new blog post, votes for post, comments on one, or other features that Joomblog may offer.

If you need help setting up reads, let me know, and we'll help how we can.

Thanks,
Alex

Pieter,
Again, I don't know Joomblog, so the below may not be 100% accurate, but I think it should get you there. To setup the read action for blog posts in an extension we don't support, you'd mainly want to follow all the instructions in our Open Graph for Joomla configuration guide.

The only difference would be in the steps for setting up the Object within JFBConnect. Instead of creating an "Article" object, you'll want to install and enable the Open Graph - Custom plugin. Create a new "Custom Object Type". For the "Type" on the left side, it'd be "news.reads", just like the configuration guide. The "URL Query Parameters" is what you'd need to set so that the Object is properly set for your blog view pages.

Here's where I get a little inaccurate... disable SEF URLs (if enabled) and go to one of your blog posts. The URL will look something like the below (I'm guessing here):
index.php?option=com_joomblog&view=post&id=12
The id will change for each post, so we'll disregard that. The option=com_joomblog and view=post is what we want to apply our Object Type to anytime those types of URLs are loaded.. so, in the "URL Query Parameters", you'd want to put:Again, you'll need to update that based on the actual URL for your posts.

After that, setup your actions just like the configuration guide shows.

Hope that helps, but let me know if you have any questions!
Alex

Definitely let us know how it goes. The "Custom Object Type" allows the creation of Open Graph Actions for any extension, but it's just a little more tedious than point and click.. hopefully still easy, and worth it, though!

Best of luck,
Alex

Pieter,
Doing a search, I found that the error message is generated by mod_security, part of Apache, when it's configured very strictly. You'll need to either have your host disable that module or send us a report as to what is wrong with the request we're making to save that is causing it mod_security to be triggered. For more information, see:
www.werockyourweb.com/406-error-not-acce...found-on-this-server

Hope that helps explain, but let us know if you run into any issues with the above.

Thanks,
Alex

Definitely let us know how that goes. Hopefully, that will get you fixed up. If they can provide a log of the exception that our saving was causing, we'd gladly look into how to change our data so as not to trigger the issue as well.

Either way, hope that gets you going, and best of luck,
Alex