Import af avatar to kunea

We just had our 2nd report of this same problem yesterday. Its very uncommon, but have an idea for a workaround for saving the image to your server. We'll be testing this shortly, and hope to have it in the next release (later this week). The other thread is below, if you'd like to see the discussion that's gone on there.
www.sourcecoast.com/forums/topic?id=1243&p=1#p4658

Sorry for the inconvenience, we'll get something going soon.

Howdy!
Sorry for the delays, but we think we have a solution that worked for the 1 other person with this problem. I just tried to log into your site with the admin account you had sent earlier, but it doesn't seem to work anymore.

If you could re-enable that account, I could try my fix. Alternatively, if you'd prefer to do it, could you please update the same line as above, just differently? We realized that the line of code was checking for some settings on the server, and it could possibly be reported differently than we expected. Either way, would love to hear your feedback as we're planning to implement this minor change in the 3.0 Stable release due late tonight or tomorrow.

In the /components/com_jfbconnect/libraries/profile.php file, ~line 124, change the following line:
if (function_exists('curl_init') && ini_get('open_basedir') == '' && ini_get('safe_mode') == '') {
to
if (function_exists('curl_init') && !ini_get('open_basedir') && !ini_get('safe_mode')) {

If that still fails, please additionally try adding the following bold line to the commands underneath:
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);
curl_setopt($ch, CURLOPT_TIMEOUT, 50);
curl_setopt($ch, CURLOPT_FILE, $fp);

Thanks for your patience, and good luck!

3.0.0 was just released. Unfortunately, there were 2 bugs that we were unable to determine a cause for, and ultimately fix in this release. One of them is yours.

Now that its out, we'll be focusing even more on solving this problem. We'll be using the credentials you re-sent (thanks) to determine the avatar import issue and will get something temporary setup before we can bake something into the next release. If you could, please upgrade to 3.0.0. This involves unintalling and reinstalling the component along with any of the social modules/plugins you may be using. We'll be improving the upgrade process in an upcoming release. Having 3.0.0 on your site will help us narrow down the issue as there are many other minor bugs fixed in this release.

Just wanted to let you know the status, and thanks again for your patience.

Alright, we'll be on your site very shortly to figure this out. We've had no other posts about this, so it seems your server just doesn't like us.

The good news is that we did add a feature to auto-link accounts by email.. so even with blowing away your usermap table, when we fix the issue, any returning users should automatically link back up.

We'll let you know what we find.

Yowzer! That took much longer than we ever anticipated, but good news! You should be up and running.

The usermapping issues seemed to only be that the authentication plugin was not enabled. The profile issue was much trickier. Basically, your server has a lot of security setup on it.. which, while good, some of it's overkill since you're the only one that's ever had this problem The security was preventing external images from being automatically downloaded to your page.

We implemented a new approach, which gets around these methods (don't worry, it's not insecure). My avatar was successfully imported into both Kunena and Community Builder after doing this. We'll be investigating if this is the approach we want to use going forward, or, if not, figure out how to set an 'alternate image grab' setting or something along those lines. You should be good one way or another in future releases.

What you need to do:
* Delete my accounts. The super admin account you created along with "sourcecoast" - registered user I was testing with. Left so you can see my avatar, just in case.
* Enable the JFBCLogin module - I left disabled because it's your site. Test first or do whatever you want.

I reaaally hope you don't find other issues, but if you do, you know where to find us

Thanks, once again, for your patience while we resolved this problem for you.

You don't need to talk to the hoster. Again, we found a way around it, and are likely going to use that in the upcoming release to prevent this problem for any other users. Extra security isn't a bad thing

We have a goal for 3.1 to re-scrub the translations in the modules and component. A lot of the strings in the language files (unfortunately) have been moved or are no longer used since we shifted functionality from the Login Module to the component. Sorry about that. You'll loose them again with the next release, but after that, you should be able to use the language files to store them in. Additionally, you can do a template override of the module to prevent the change from being lost when you upgrade next. For more information:
www.sourcecoast.com/extensions/troublesh...s#template_overrides