why no reply for private message AGAIN?

I think you're link above was wrong. Could you explain more about what you mean is wrong when you changed that setting:
* Is the post going to the correct Facebook Page?
* Is the link incorrect?

Any information you can provide will really help.

Thanks,
Alex

Thanks for the details in your post.

The relative path of the URL is correct, but the domain is missing. That's not an issue we've heard of before. I see you're using JFBConnect v7.2.1. Can you try upgrading to JFBConnect v7.2.2 and see if that fixes things? There were some minor EasyBlog updates in the latest release that could affect this, but if not, we'll gladly dig into what's going on there further.

Thanks,
Alex

I just investigated further as to what's happening.

When JFBConnect tries to autopost content, we make a call to the front-end of the site to get the SEF version of the URL to be posted. However, that call is failing when being made from the admin area of your site.

When that call is made, it makes a request like:
index.php?option=com_jfbconnect&task=ajax.sef&url=aW5kZXgucGhwP29wdGlvbj1jb21fZWFzeWJsb2cmdmlldz1lbnRyeSZpZD05ODU=

If I go to that URL directly, it works. From the admin area making the call, it fails with the following error:

Forbidden

You don't have permission to access /dev/index.php on this server.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.

I'm not sure what's causing that as it seems like it may be a firewall or other server configuration issue not allowing the admin area to call the front-end of your site. Because that call is failing, the URL was just being the relative link.

I've made a change on your site which should generate a working URL including the domain. Please test and let me know if that works for you.

Thanks,
Alex

The code change I made on your site will work if the Forbidden issue is fixed automatically. The change I made simply uses the non-SEF link if the SEF link couldn't be generated. So you are free to test and try disabling AdminTools or whatever else you think may be preventing the front-end page load to be working. If it still fails, you'll get a non-SEF URL which at least works.

I plan to have this code fix implemented in the next release as well.

I hope that helps explain,
Alex

The code change we put on your site is checked in, but we haven't released an updated version with it included yet. Your site was the only issue with this problem so far, and your site should be fixed for now. We are working on a new release which has this, along with other fixes for other users and various improvements, that should be out over the next few weeks.

Thanks,
Alex