Hey there,

Do you mean this "instance image folder" is your local server directory folder right?

Perhaps you can provide us with your following details at http://stackideas.com/dashboard/site so we can better have a look on your site?

1. Joomla backend access
2. FTP access
3. Provide us one of the blog URL which show the image correctly if you didn't remove that image file from your local server
4. Provide us one of the blog URL which show broken image if you already remove that image file from your local server

Because currently we never use JA Amazon S3 component before so I am not really sure how it work currently.

Do you mean this "instance image folder" is your local server directory folder right?

Yes.

At the moment all images working because I did create one script to copy "images folder" (that was previously backup) when code is deployed. But that it is not solution because when we create new post I have turn off all instances make the post, zip the images put on S3 bucket and run the script to copy that "images folder" on all instances.

Best solution for me will be easyblog to skip file (image) checking.

Thanks.

I am sorry for the delay of this reply,

I've checked the code, we actually just render out the blog content without do any image checking.

For example this blog HTML content :

<p>test</p>

<p><img src="images/easyblog_articles/34/b2ap3_large_6760135001_58b1c5c5f0_b.jpg" width="1024" height="1024" align="center" data-style="clear" /></p>

So browser will trying to load this image on the page, if the site server no longer have this image, it will show broken image in this case.

To be frank with you, currently i have no ideas how this JA Amazon S3 component work, so that is difficult for us to know which part went wrong.

In Easysocial extension, we do have implement this feature, when the media item pushed to Amazon S3, in PHP part, we will replace the site domain name to Amazon region-specific endpoint e.g. http://s3-ap-southeast-1.amazonaws.com/bucketName/media/com_easysocial/files/users/466/file.pdf , so even i remove this file from my local server, the webpage still can able to render this correctly because now it referring to this Amazon S3 region-specific endpoint path instead of local server path.

If this JA Amazon S3 component can work well in Joomla article, perhaps you can setup one of the staging site which installed this JA Amazon S3 component so we can better have a look why it work fine in Joomla article but that is not Easyblog.

And if it possible for you that provide us with your following site details so it will help us troubleshoot this quickly.

1. Staging site Joomla backend access
2. FTP access

Sorry at the moment I cant provide ftp access.

In Easysocial extension, we do have implement this feature, when the media item pushed to Amazon S3, in PHP part, we will replace the site domain name to Amazon region-specific endpoint e.g. http://s3-ap-southeast-1.amazonaws.com/bucketName/media/com_easysocial/files/users/466/file.pdf , so even i remove this file from my local server, the webpage still can able to render this correctly because now it referring to this Amazon S3 region-specific endpoint path instead of local server path.

can you share you changes ?

Actually you do not need to change anything into the Easysocial core file, because Easysocial already have this feature, you can follow our documentation how to setup this in Easysocial.

https://stackideas.com/docs/easysocial/administrators/remote-storage/setup-amazon

But unfortunately Easyblog do not have this feature yet at this point of time.