Topic-icon Problem with Open Graph Plugin for Easy Blog

Active Subscriptions:

None
Dear Alex,

I continue to really enjoy the functionality your products deliver.

I ran the update function on my Joomla 2.5 site and all went well but then my Easy Blog blogs wouldn't show up. All of the menus would work but as I drilled down to the actual blog nothing would display. When I disabled the JFBC Open Graph Plugin for Easy Blog, the blog now displays. I installed the plug in from my distribution labeled jfbconnect-5.0.1-joomla25_20130703_unzip_first.

On a side note, I'm curious why I would want to continue to use the default Joomla article content manager any more. I really like the ease of Easy Blog. I like your products and how they display in a Joomla article. What are your thoughts?

Spike
The topic has been locked.
Support Specialist
12 years 9 months ago #35377 by alzander
Spike,
Glad to hear you're still enjoying things. We're getting very, very excited for our v5.1 release (which should be out next week). That release adds Google authentication, and a whole bunch more. It's going to be big.

As for your question, I'm sorry you ran into some issues with the EasyBlog integration. My guess is that you're running into a problem we've heard of, but haven't fully diagnosed. To fix, you can either disable the Open Graph - EasyBlog plugin, or you can edit the /plugins/opengraph/easyblog/easyblog.php file. Around line 121, you'll see:
if ($image_type == 'custom_image_category' || $image == '') 
            { 
                $tmpImage = SCArticleContent::getEasyBlogCategoryImage($item->category_id); 
                if($tmpImage != '') 
                    $image = $tmpImage; 
            }
Comment (or delete) that whole block out and that should prevent the error. We'd love to know if that helps.. and if so, could you let us know what version of EasyBlog you are using, which may help us narrow things down further.

As for EasyBlog, no arguments there, it's a great extension. We use a mix of Joomla articles and EasyBlog (for our blog) on this site, actually. Joomla articles are easier for documentation and 'static' content, in my opinion. It's usually simpler by default so there's less to actually disable than if we were to use EasyBlog. Plus, many extensions work directly with Joomla content, which is a benefit.

In general though, using EasyBlog exclusively for content isn't a bad thing. We're working on even more integration with EasyBlog in addition to our existing features, like posting when an Open Graph Action whenever a user leaves a comment to their Timeline.

I hope that helps answer your questions, but if you have any others, just let us know.

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

None
12 years 9 months ago #35382 by spikesantee
Dear Alex,

I am using EasyBlog 3.8.14576. My control panel says that it is the latest version. I have already disabled the EasyBlog Open Graph plug in so my blogs are working okay without it. When I turn it on, the browser attempts to navigate to the actual blog but it just stops with a blank page. All of the menus and categories and editing work, just the blog in finished form doesn't show up. When I disable the plug in it works okay. I don't know what functionality I'm missing without the plug in but I'll sit tight and look forward to your new release.

I was on the same page with you about which content editor to use. My major papers are in Joomla and my quick posts are in EasyBlog. I think I will continue to do it that way for the very same reasons you stated about your own content.

Keep up the good work.

Spike
The topic has been locked.
Support Specialist
12 years 9 months ago #35422 by alzander
Spike,
We're investigating this issue a little more as we'd love to get to the bottom of it before the next release.

Can you help us out by doing the following:
* Go to the Joomla Global Configuration area and set Error Reporting to "Maximum"
* Enable the Open Graph - Easy Blog plugin
* Navigate to the page and look for a PHP Error message that may be there.

If it exists, let us know what it is.. then undo the changes above. This issue has only been reported by one other user and we can't recreate it.. so getting any more information about what the actual error is will help us ensure our planned fix will work (since we can't test directly).

Glad we could help explain our process and help you decide on what would work best for you.

Thanks,
Alex
The topic has been locked.