JFTP write bad response

I don't have a copy of your site. If you're willing to let us try, we gladly will.

As for switching to JomSocial, we had to lose a customer, but we definitely understand your frustration. We have a 30-day money back guarantee. If you do switch, let us know. You're slightly past the 30 day window, but we'd waive that in your case for your troubles. PayPal does only allow refunds for up to 60 days though.

Please let us know how you'd like us to proceed.

Thanks,
Alex

Yes, we could definitely do a lot of testing on a backup. If we could get one (with your permission), I think it would help us narrow down the activiation issue very quickly (and would be our focus this weekend). The JFTP issue, I think, may be a more server related issue, but we really can't tackle that until we're able to create an account easily.

Let us know if we can install (if it's not already there) Akeeba Backup and make a backup of your site for our testing purposes.

Thank you

Evil,
Good news. We've found the cause of the non-activation issue for Community Builder. The cause is because you have 2 required fields in the CB profiles which are not automatically being populated by Facebook. Since they are required, but not filled in, Community Builder will not allow the user to be saved.

The 2 fields are: Birthday and Gender. We have some logic to pre-populate these fields in JFBConnect with what whatevever 'default' values you've set in Community Builder. However, you don't have any defaults set. On our system, we set those 2 fields to not-required and our profile immediately imported correctly. Our avatar also successfully imported, but we are not using FTP.

If you mark those fields as not required, the same should work for you. Please test, and let us know how it goes. We don't want to mess with profiles on your site though.

Finally, a few notes:
* We are working on methods to import dates and gender for the 3.1 release. The gender will be more difficult, but we're hopeful we'll get it in there.
* You have a system plugin called Javascript SDK. This is adding the Facebook javascript twice on your page. I don't think this is causing problems currently, but it's possible it may.

Good luck, and please let us know how it goes!

Wow, you're running into all the issues. I'm not sure if you have database access to run a query, but if so, the following query will clear up this issue:

ALTER TABLE `jos_jfbconnect_user_map` MODIFY COLUMN `fb_user_id` BIGINT;

The problem is that, a long time ago, Facebook increased the size of their user Ids. The old size we were using in the table wasn't long enough. In the 2.5 release (more than a year ago) we updated the database. If you were using a previous version and never upgraded to 2.5 or 2.6 and went straight to 3.x, your table wouldn't have been updated. So, if users who have 'newer' Facebook accounts try to log in, their Facebook ID is not being properly stored in the table, which is causing your issue.

If you don't have database access, please let us know, and we can fix it in another way.

For legacy reasons, we don't delete the images. We've contemplated it in the past, and will likely change the logic to delete the photos we download (and aren't used) in the 3.1 release.

As for your troubles, we do appreciate your patience, and are glad we got you going. We upgraded your subscription to a JFBConnect12. We don't normally extend subscriptions due to a support request, but yours have been extra irksome.

Thanks again, and good luck!