If this is the wrong place forgive me. I made the following changed to deal with SSL. Can you incorporate them in a future release?

Thank you,

ggg

xd_receiver_ssl.htm
<script src="ssl.connect.facebook.com/js/api_lib/v0.4/XdCommReceiver.js" type="text/javascript">

cb.facebookconnect.php

// TODO - Tripg added to account for SSL needs
$currenturi = JURI::getInstance();

if($currenturi->getScheme() == 'https') // TODO - Tripg if the site is using ssl use ssl for FB
{
$_CB_framework->document->addHeadScriptUrl( 'ssl.connect.facebook.com/js/api_lib/v0.4/FeatureLoader.js.php' );
}
else
{
$_CB_framework->document->addHeadScriptUrl( 'static.ak.connect.facebook.com/js/api_lib/v0.4/FeatureLoader.js.php' );
}


if($currenturi->getScheme() == 'https') // TODO - Tripg if the site is using ssl use ssl for FB
{
$xd_reciever = $_CB_framework->getCfg( 'live_site' ) . '/components/com_comprofiler/plugin/user/plug_cbfacebookconnect/xd_receiver_ssl.htm';
}
else
{
$xd_reciever = $_CB_framework->getCfg( 'live_site' ) . '/components/com_comprofiler/plugin/user/plug_cbfacebookconnect/xd_receiver.htm';
}

Post edited by: krileon, at: 2010/03/21 17:15

This didn't make RC3? What is the priority of this? Is anyone else using SSL on their sites?

Thought that the logic to check for https in the uri prior to switch to https on the FBC call would handle that. Ok we'll keep hacking the code. Please note for others it is not as simple as switch to HTTPS and does require all the steps outlined in my original post.

Thank you,

ggg