EasyBlog Open Graph Plugin: incorrect Path for Post Image

As I mentioned in your other post, it would be easiest to get FTP and superadmin credentials to look at this issue. The code has many cases on how it builds up that image link based on which EasyBlog version, whether you're using category or main blog image, etc that we will most likely need to step through the code.

In order to investigate this further we tried to turn off SEF URLs but were unable to. Even if I disabled SEF URLs in both the sh404SEF configuration area and the Joomla Global Configuration area, the URLs remained as SEF and worked normally. That's not normal behavior when SEF is turned off.

Can you help us determine how we can change the URLs to their non-SEF versions (index.php?option=com_easyblog&... ) ? I'm assuming those settings are important, but if you have additional caching or something else that may be making the old SEF URLs still work, let us know.

Once we can do that, it will help us narrow down where the issue is.

Thanks,
Alex

I'm not sure what happened when we tried either. I see the non-SEF URLs now and the Open Graph Object works. I updated the "type" in the object settings to "article123" and in the source HTML of the page, the og:type is properly set to "article123".

After that, I went to the Joomla Global Configuration area and enabled SEF there. The og:type was still properly set to article123.

Then, I went into sh404SEF and enabled SEF URLs there, but the URLs didn't change. They still had index.php/ in the URL and didn't seem to update. So, with sh404SEF enabled, the URL looks like below, but the Open Graph tags are set properly:
www.dev2.altitudes.asso.fr/index.php/blo...omme-si-vous-y-etiez

Let us know if you can understand why sh404SEF isn't setting URLs. It seems like there's some conflict there we haven't heard of those if enabling it breaks our object plugins. For note, many sites, including this one, use sh404SEF with JFBConnect though. Have you made any modifications to sh404SEF or JFBConnect code we should know about?

Thanks,
Alex

Alright.. sorry for all the confusion. There's a few different posts that I got confused regarding issues you were having and sites that were related. I just FTP'd into your site and fixed the problem. There was a small bug with JFBConnect where we weren't properly detecting the type of formatting that EasyBlog is using for their images and, because of that, were re-inserting the full domain. It should be fixed now and the update will be in the next release of JFBConnect as well.

Thanks,
Alex

Alright.. think we're there now

- image URL (in og:image and twitter:image) starts with // instead of http:// (maybe it's not so important...)

Fixed. I made one more minor change to our code on your site. If you'd like to implement it on your live site, just copy your /libraries/sourcecoast/opengraphPlugin.php file from the dev site there. Again, this will be in the next release.

- the image URL is the URL of my production site, whereas we are on my dev site. The database is a copy of the production database, but usually that's not a problem. I can't say weither the issue is on JFBConnect side or EasyBlog side.

That's how the image is set in the article. The image tag looks like:The // at the beginning is what was the original issue as it was a case we didn't support (but now do). The image path itself is to your live site, and that's just how the blog post was saved.

I hope that helps,
Alex