This plugin creates folders in /tmp directory and uses up disk space. The issue has been reported on github, but there is no response from developer.
Fortunately, the reporter created a patch for this issue. If you have same trouble, see the issue tracker page for more detail and getting the patch. But I hope the developer merge the pull request and fix the issue.
/tmp/ folder with insane amount of empty folders · Issue #21 · alfreddatakillen/wpro
]]>I’m not sure if this is a feature request or there is something wrong with my installation, but when i delete an image from within the wordpress admin, it says that the media attachment is permanently delete, but when i check the S3 bucket, all the “deleted” images are still there.
Shouldn’t the plugin be able to manage those files inside the S3 bucket?
Otherwise, after a long time, the bucket contents and the media library of a wordpress installation would be completely out of sync, not knowing which images are being used by the site and which not. (plus the added costs of having not actively used images)
Thanks for a great plugin it works really well.
One question though:
I changed the S3 bucket AWS region to EU (Ireland) region, but the endpoint is still s3.amazonaws.com, is this supposed to happen?
I noticed that on line 431 it is hardcoded to this url.
]]>I try to upload images through the latest iOS app. It worked before I switched to the Read Only Plugin. I would suspect this should work since it claims XMLRPC is functional with this plugin. The WordPress iOS app is configured to use XMLRPC and it still doesn’t upload. The image doesn’t get placed in my S3 bucket even. Anyone have experience with this? It looks like some response is being returned to the app that it isn’t expecting.
]]>When I try to add media, the only option available for size is “Full Size”. In the other WP sites I’ve built (which don’t use WPRO) this doesn’t occur, so I assume the problem lies with WPRO or the S3 model of hosting media.
Can I get “Thumbnail”, “Medium” and “Large” to show up again?
]]>Hey,
I could be off on this but I noticed that the assumed URL in the plugin is BUCKET. s3.amazonaws.com and it’s now actually reversed. Also, it’s https. Here’s the updated line:
$data[‘baseurl’] = ‘https://s3.amazonaws.com/’ . trim(str_replace(‘//’, ‘/’, get_option(‘wpro-aws-bucket’) . trim(get_option(‘wpro-folder’))), ‘/’);
Just tested it out and works for me. Again, I’m quite new to this service so I could have just missed a configuration.
just fyi
]]>Hi there,
The plugin works great and all however but using the Import function becomes problematic.
The problem is that the import functionality requires to write the file on the server, but since this plugin would upload it to amazon, the import functionality cannot find the file on the webhost.
]]>the plugin is not changing the post urls to go to s3 …only a few of them …and new posts that are created seem to work fine …. with w3tc cdn for example will go and rewrite all urls for wp-content/uploads to the cdn address….
can you please suggest how to fix or what you’d suggest to workaround this? is the only way actually going into the database and changing the hardcoded image urls?
]]>this may be a life safer! is there anyway to use this with my own ftp cdn? or just s3 ?
]]>Hi,
just a quick note of support – we run a cluster of WP machines behind a load balancer and this is the best plugin I have come across so far for handling uploads to S3.
Only 250 downloads for this plugin so far, but I suspect more will come as it appears the other popular S3 plugins are being abandoned by their developers.
Please keep up the good work ??
]]>I’ve been looking for a good solution to start migrating all of our static media content into Amazon S3, and this looks like a pretty way to go, with a bit of customization. I went a bit fast and dirty, but ended up changing the following four elements:
– I installed the .php file into the wp-content/mu-plugins/ folder instead of the normal plugins folder.
– In the admin_init function, I needed to set values for all blogs so that I didn’t have to go through them one-by-one. So, where all nine settings are registered there, I just dropped nine update_option lines with my key, secret, bucket, etc. This gives all WPMU sites the same default settings.
– In the upload_dir function I need to insert a blog_id subfolder to the baseurl, so that blogs keep their media separated into dirs by blog_id. So I call “global $current_blog” at the top, and then in the two $data[‘baseurl’] lines simply inserted $current_blog->blog_id and slashes appropriately.
– Finally, since config settings were taken care of, I commented out the heart of the admin_menu function, i.e. the add_options_page call.
I have this on a test WP network and it’s really working perfectly. I have some more testing to do, specifically what happens if I add this to a network with over 200 sites already existing — my hope is that this will reroute ALL media uploads into S3, but not interfere with existing media until I can upload them into S3 and update all the links. What do you think?
I also wonder if there are media types that won’t work with this plugin? Any limitations there, as to filetype?
Am I missing anything here?
]]>I have checked the plugin on single WP and it works great, all image sizes, featured images, custom background, image editing and image uploads on custom themes options page.
Just a custom header image uploads the image but fails to crop and resize.
]]>