Hey Matt,

Is it possible for you to provide us with the back end and FTP access to your site to check on this issue?

To add your access, simply edit your first post above or head on to http://stackideas.com/dashboard/site to insert your site access once only.

Hi there, sorry, should be able to login now (c:

Hi Matt,

I am really sorry for the delay of this reply.

Can you provide us with your amazon s3 access and your database access so we can check on this issue further?

Should have access now with the additional details in the site details for this account?

Let me know if you need to the S3 details as I will have to get permission to give you these.

Hmm I have also added the S3 details. It seems that the images are not either local or on the S3 servers - meaning they are lost? They where all there before the upgrade....

Hey Matt,

Hm, I have just checked your site and Amazon S3. It looks like those photos are actually not on the site and neither is it on Amazon S3.

I am not too sure how this was configured earlier, did you switch between "local storage" and "amazon s3" multiple times?

I am suspecting that there was some errors with your S3 configuration and the photos was deleted on your local instance but Amazon was actually "rejecting" the uploads because of the incorrect settings.

I have tested this on your site by creating a new album at http://gamersnaps.com/browse/item/160-testing-remote-storage/user/634-extfix , and upon running the cron, the images does get pushed to Amazon correctly.

Do you have a backup of the files on the server? I would suggest that you restore them into /media/com_easysocial/photos

Hi There,

I haven't made any changes to the storage setup, it was working fine, I upgraded following the method in the documentation, and now this has happened?

I guess I will just have to delete all the empty albums )c: I am not sure I have a backup.

Hey Matt,

Hm, to be honest, I am not too sure what actually happened and this is actually the second time I have seen this issue but the other issue was because the user configured S3 incorrectly and it was already fixed in 1.4.8.