Hey Phivos,

I am sorry for the delay of this reply,

Can I have the permission to help you update to Easysocial 1.4.8 version in your site?

Dear Arlex,

I updated to 1.4.8. Please have a look at the issue.

Regards,

it seems like that avatar image already uploaded to your Amazon S3, you can check my attached screenshot below.

May i know the cronjob where you setup before? Is it possible provide us that access so we can better have a look?

Dear support,

It seems that the problem for those users has been resolved itself. We have not changed anything with regards to the cron.

We updated to EasySocial 1.4.8, then waited for about half an hour and then contacted you to proceed. It seems that it has been resolved the same weird way that it appeared, but for those two users only.

Please check this user as well. We just updated his profile picture before half an hour. The avatar is not saved to Amazon S3:
https://penaltara.com/community/%CE%A0%CF%81%CE%BF%CF%86%CE%AF%CE%BB/471-andreas

Please let me know which access do you need? The host provider to check the cron? If yes, I included just now the credentials to my frist post above.

Regards,

Hey Phivos,

It seems like recently you change your site to SSL certificate right?

Because I noticed your cronjob is not working in Easysocial.

So I have update to use this cron file -> JoomlaFolder/components/com_easysocial/escron.php

it should work fine now, can you give it a try upload a new avatar photo again and see how it goes?

Dear support,

Thank you for the valuable input. Yes, we updated the cron file in the past but it seems that:
1. The issue as reported above has been solved upon EasySocial update but
2. The cron.php file was replaced on the update so the modification done for the SSL site has been lost and so this new problem was still causing the same issue.

Question:
You renamed the cron.php to the new escron.php. What will happen upon a future EasySocial update? Will we have to update escron.php form now on?

Regards,

Hey there,

I am really sorry for the delay of this reply as it is a weekend for us here.

I found out that cron.php file is always get overridden for every update, I will fix this in future release version.

So I have temporary duplicate another cron.php file to use escron.php. At the same time, it will not get overridden every time you update your Easysocial.

In your Cloudaccess.net cron service configuration, I already changed that command to execute this escron.php file instead of cron.php.

Overall, everything will within the same and work fine.

Dear Arlex,

Thank you for the valuable input.

It seems that we will have the same problem with the cron.php of EasyBlog as we are going to update it. Shall we copy and rename the cron.php to ebcron.php for example and update the cron command in our host, in order to avoid the replacement of the cron.php during the update?

There is no need to reply during the weekend. This is not urgent. Thank you.

Regards,

Dear Arlex,

We have updated EasyBlog. We had in mind to update the cron.php with the site name and socket port so everything works normally now.

If you find a way the cron.php not to be replaced on every update this will be helpful. Thank you.

Regards,

Hey Phivos,

The "cron.php" is just a sample file which we provide so user's could easily use it. What you could do is to copy the file out to your Joomla root directory, and modify your host's cronjob to point to this new path

Dear Mark,

Thanks for the valuable input.

In the beginning, we just left it like that as we did not know if there might have been any change to the file, upon a future update.

Regards,

No problem Phivos, just copy the file out of your EasyBlog directory and you are good to go

Dear Mark,

Ok thank you for the valuable input.

Regards,

You are most welcome