hey Sabih,

I've checked in yous site, it seems like some of the image corrupted or damaged, can you provide us with your Amazon S3 access so I can investigate this issue?

it seems like some of the image corrupted or damaged

These images were there, I could see them and then I started the cronjob manually and afterwards the images were corrupted.
So the corrupted ones are the images that were recently uploaded to S3.

S3 access updated in first post.

Hey Sabih,

I am sorry for the delay of this reply,

I've tried to login in Amazon S3 but it seems like it always redirect me to login this page first, you can refer on my attached screenshot below.

Is it I login wrong page? Please advise.

Hm, never seen that page before. I always enter through this url: https://console.aws.amazon.com/s3/home?region=us-west-2 and then enter my login stuff and it works.

hey Sabih,

I can access your Amazon S3 now, for some reason my chrome browser always get redirection to another login page.

Can you open this file JoomlaFolder\administrator\components\com_easysocial\includes\cron\hooks\storage.php from your live site and temporary comment out these few line of the code? So that it can prevent all of your site photo stop upload to amazon. Because I just logged in as another register user in your site and I can replicate this issue when upload to Amazon, the image already broken.

Also can I have the permission to setup Amazon S3 from your dev site for investigate this issue?

Can you open this file JoomlaFolder\administrator\components\com_easysocial\includes\cron\hooks\storage.php from your live site and temporary comment out these few line of the code?

Done.

Also can I have the permission to setup Amazon S3 from your dev site for investigate this issue?

Sure, just go on. Only important thing to know is, that I do not have any backup of the images on S3 from my live site.


It would be great if you could delete your stream entries the moment you do not need them any longer. Because I do not want to delete these things while you are still testing and perhaps still in need for these testposts.

Is it safe to execute a cronjob at the moment or are the latest photos gone afterwards?

Hey Sabih,

I am really sorry for the delay of this reply, because I still investigate this issue why the image get corrupted after push to Amazon S3.

Is it safe to execute a cronjob at the moment or are the latest photos gone afterwards?

Do you mean your live site? If yes, you can execute the cronjob on your live site, because you already commented out these code from this file -> JoomlaFolder\administrator\components\com_easysocial\includes\cron\hooks\storage.php so it will not push your site new photo in Amazon S3 at this moment.

By the way, I have setup a new bucket in your AmazonS3 to testing this issue on your dev site, and may i know this dev site also running cronjob as well?

may i know this dev site also running cronjob as well?

Hm, I am not sure if I understand this question. There are no planned cronjobs on the dev site and I have never used cronjobs there.

hey Sabih,

Hm, I am not sure if I understand this question. There are no planned cronjobs on the dev site and I have never used cronjobs there.

Oh, what i mean is I afraid that if you have setup cronjob in your dev site, it will automatically update the image into your amazon S3. By the way, I still troubleshot this issue and I will keep you update.

Thank you very much Arlex and I feel sorry about having such a big problem.

Just to make it clear, there is no cronjob activated on the dev site.

Hey Sabih,

You're welcome.

I have a question :
Can you recall again did you change any permission setting from your Amazon S3 account? Because I remember your site is work fine before. I also tried in my locally regarding this, it did pushed in Amazon S3 server and show the image correctly (screenshot : http://take.ms/2RoYhT ). Mean the Amazon S3 API didn't have update.

By the way, I've tried to login in your AmazonS3 but it shown me `Your password is incorrect`, perhaps you can update again with your new password in this thread first post so that I can login and see what is your current setting from AmazonS3 server?

Can you recall again did you change any permission setting from your Amazon S3 account? Because I remember your site is work fine before.

I did not made any changes regarding the S3 account. I know that the cronjob was working then I suddenly got a mail from my provider that tells that the cronjob is causing a timeout and was shutdown. After that I updated to EasySocial 1.4.11 and it was working but the images were gone.

Maybe you remember you sent me an updated amazon.php file that I replaced the original one with. I saved this file and put it back on after the update. Is that causing the mistake? I am confused about the former changes because I remember that there were several problems with the cronjob before on my site.

Here are the threads of the problems some time ago:
http://stackideas.com/forums/uploaded-s3-images-not-shown-after-cronjob
http://stackideas.com/forums/cronjob-leads-to-404

I have updated the login passwort for S3, maybe this will work for me? I have no idea why you got a login incorrect, I just tested it and it worked but I updated it now.

Hm, I am sorry for previously what I provided that fix code is not a proper fix.

And I also re-check again, last time you hitting that 404 error when the cronjob process, now no longer hit this.

I already revert back to original code regarding this file. JoomlaFolder\administrator\components\com_easysocial\includes\storage\amazon\amazon.php

Can you try upload some photo from your dev site and see is it work fine now?

And manually run this cron URL -> http://sicherung.zazeni.de.vm107.fc-server.de/index.php?option=com_easysocial&cron=true

Thank you very much Arlex,

on the dev site it is working but live site is giving 404. >.<

I have replaced the amazon.php with the one you provided and withdrew the changes in the storage.php made some posts ago.

I already help you updated that record from your database, it should work prefect fine now.

Awesome. Thank you very much Arlex. I am really sorry that this small problem caused such a long time work for you and I really appreciate your effort to solve this in the end. Thank you so much.

Hi there,

You are most welcome. Glad to hear that your issue has been resolved now.

As a gentle reminder, kindly start a new thread if you have any other issue in the future so it will be easier for us to manage your inquiry. I will lock and mark this thread as resolved.