Joy jili casino login register mobile philippines.Claim Your Free 999 Pesos Bonus Today

Resolved ajayrds
(@ajayrds)

11 years, 4 months ago

Hi,

Thanks for the amazing plugin, it definitely helps speed up the website.
I had a lot of photos from 2012 onwards which are now on s3 because of this plugin.
However, I noticed that photos in two folder (2012/05, 2012/10) were missed somehow and they still are on my server. Please check here – https://www.gounesco.com/proof/22768032288-ankitha-prashanth-shravya-airavateswaram-temple-darasuram/
The pictures on this post are still referring to the files on the server whereas the pictures in this post from march are referring to the s3 files – https://www.gounesco.com/proof/19355818608-khajuraho-the-symbol-of-the-chandela-kings/.

I have now uploaded all the files in these two folder to S3 by using dragondisk on ubuntu, how can I make sure that the photos now are directed to the S3 versions?
Also, I noticed that the urls in the posts remain same, does this mean that the request first comes to my server and then gets redirected through the htaccess in the uploads folder? Would the website get faster if the request was directed initially itself to s3?

Ajay

https://www.ads-software.com/extend/plugins/amazon-s3-uploads/

Viewing 5 replies - 1 through 5 (of 5 total)

Plugin Author atvdev
(@atvdev)

11 years, 4 months ago

Hello,
the images are uploaded via wp cron job, 50 files, every 30 minutes. That means that you blog must be visited by someone to get some files uploaded to s3 (that’s how wp cron job works). Probably if you had waited some more time, files would have eventually uploaded.

Now that you have uploaded the files manually, the plugin sees that there is already a file with that name on s3 and leaves the local file as is. Currently the serving of s3 content is done by a redirect with htaccess, only if the requested file does not exist on local server. And that’s why you continue to see your local images although you have copied them to s3. To make the redirect work you have to delete the local files that you uploaded to s3. That’s also how the plugin works, after a successful upload to s3, the local file is deleted.

If the request was directed initially to s3, you would win some milliseconds before the webpage is cached, and maybe more if your wp shows a lot of images. But to make that I must make the plugin to work without cron jobs and upload files directly to s3, which slows media uploads a lot and can not be done until patch for this bug is released. So when the patch is released, I will review if it is worth it. Maybe I will leave both options for the user to choose, I don’t know yet.

Thread Starter ajayrds
(@ajayrds)

11 years, 4 months ago

Thanks a bunch for the quick reply!
I have deleted the files on my server now, and it works just like you said. About avoiding the redirects, I was thinking about the advantage of downloading files from separate domains. But i do understand, other functions will get slow.
Thanks again for the excellent plugin!

Ajay

myhero
(@myhero)

11 years, 3 months ago

Hi,

Thanks for the contribution

Does this plugin work all file uploaded to WP or only files uploaded through the WP media library?

James
(@jameshilliard)

11 years, 2 months ago

There seem to have been 50 files transfered but the cron has not run again since? It has been 24 hours.
Ty

trickleup
(@trickleup)

11 years, 2 months ago

I have the exact same issue as JamesHillard. I’ve pinged the website plenty, and even accessed wp-cron.php directly, but no more files are uploaded beyond the inital batch.