Import of avatar is fine, but cover is not being imported

From a message you made a few posts ago, it *was* working, correct? We are planning on implementing the changes we noted above, as there definitely was an issue with saving cover photos that would have affected sites not using the default tmp directory. From your post above, it sounded like you had things going though, and we weren't planning a lot more testing with Amazon S3 storage for those avatars.

In general, EasySocial and JomSocial handle S3 avatars the same way.. they are first uploaded locally and then (via the cron job) are pushed to S3 when possible. JFBConnect normally doesn't need to care about where the images are stored since we take care of getting them local, and those extensions 'push' them to S3 on their own without our intervention.

So, keep me posted if you were incorrect before, as that will help us narrow down where something may be going wrong. v5.2.2 is scheduled for release later this week (likely on Friday). We may be able to try some S3 testing before then, but not sure if it will be part of this release.

Thanks,
Alex

That's definitely an interesting piece of information. Our code for fetching a user's cover photo is the same whether its on a new user registration or login. It's strange that it's just the cover photo as well.

Do you have anything else (another plugin, addon, special code, etc) that may be also trying to alter the cover photo during registration? All I can guess, from the above, is that our cover photo is being imported, but then something else is reverting that back to default during registration. It's a guess, but that's all I really have right now.

From here, I'll try to FTP into your site tomorrow to check if the cover photo is being imported in code and narrow down where issues are occurring during the reg process. Let me know if you have any issues with that.. if not, I'll let you know what we find and hopefully get this cleared out soon.

Thanks,
Alex