TC McCarthy

Thank you for the thorough review. I have addressed a number of the concerns in this review.

1. I have updated the inline instructions to include links to the aws s3 IAM keys.
2. I have updated the language to match the references in the IAM section of AWS dashboard
3. Trailing and leading slashes are now being JS enforced where appropriate. Good catch! This is a pet project of mine that I developed on my own, serving as my own QA so things like this slipped through.
4. With regards to the local path and URL, I am populating initial values via the WP_CONTENT_PATH and WP_CONTENT_URL constants, which can be overridden. If you had an older version of this plugin initially I didn’t replace those values since there were hundreds of people out there whose configurations could be hosed by the upgrade. There are regular expressions in my code for building the S3 keys in a multisite environment. This plugin is in use in 3 enterprise-level multisite installs (that I know of) without issue. One of them even uses the multinetwork plugin and it’s fine. Unless I’m not understanding your issue correctly, it seems you had an issue specific to you.
5. With regards to the delete local files option, you’re right! I had an unset call for non-image uploads but neglected to supply one for my image upload handler. That’s now included in the latest version.

Your nice-to-haves are truly nice to have — I will try and accommodate in coming releases but, fair warning, my development cycle is based on juggling real life. Most of this plugin’s maintenance happens organically as I use it in my business.

Maybe check your error logs? It’s possible your EC2 instance’s file system has a permissions error? Or if you’re using environment variables are they set properly on your instance? Do you have any restrictions on your IAM keys? The latest version of tcs3 is coming out in a couple of weeks and it now supports instance profiles.

sorry, instead of network_add_menu I meant network_admin_menu.

Folks,

I apologize for this — it was inadvertent. I was working up something on another branch and it seems to have been merged well before it was ready (ergo, why there was no mention of it in the changelogs). Please remember this plugin is provided free of charge and that many developers hold down full-time jobs which can inhibit our ability to answer quickly.

I apologize for the mistake and have pushed an update that removes it.

*Returns to full-time job*

Thank you! Good thinking on the conditional, I hacked it in quickly for demonstration purposes in our post but yes you are right, limiting queries is always a good thing.

To answer the question in your initial post, my use case is that I am extending my tcS3 plugin to work with nextgen. I am using your hooks to make it seamless — when any user adds or deletes an image using the existing methods provided by Nextgen I want those behaviors to be repeated on their S3 bucket. The plugin will also modify the URL so that images uploaded to the user’s server to be added to a NexGen gallery get mirrored to S3 and read from it. The problem I had was, the mirroring relied on data in the database but the image was being removed from the database before The delete hook fired to run the delete operation on the S3 bucket, so my code did not know what object to delete.

Your code above should work. I’ll let you know if I hit another snag.

Thanks again!

Hi Traci,

Do you think you could provide a screen grab of your tcs3 settings screen? Please be sure to obfuscate your IAM keys (or take them out entirely for the grab).

Also, the latest version of the plugin displays a banner at the top of the dashboard on every screen to tell you that the plugin is active but not set up — are you seeing that banner?

Thanks!

Hi Sebastien,

I have updated the repo to match WP.

Thanks cbonastre for jumping in! I’m sorry I missed these things — I have sent version 1.7.1 to the repo. Hopefully you all will be prompted for the update shortly!

Hi and thanks for your inquiry! The latest version of tcS3, version 1.7, has this feature addition. Enjoy!

Hi and thanks for your inquiry! The latest version of tcS3, version 1.7, has this feature addition. Enjoy!

Hi,

Thanks for the tip! As suggested, I’ve set the hook priority as ’20’ in version 1.5 of this plugin.

Thanks again!

Hi,

You can download version 1.5 which allows you to disable the fallback URL. This will send image traffic directly to the S3 URL you specify. If you wish to be able to use cloudfront, use the cloudfront URL in the S3 URL field. Images will be uploaded to your bucket, but image URLs will be pointed at cloudfront!

Enjoy!

Hi!

This should be working, but if it’s not there are a couple of options. Try resaving your permalinks and/or tcs3 settings. The latest version of the plugin has a fallback option, which you can turn off. Turning it off will send all traffic directly to the S3 bucket, as opposed to the default which lets WordPress determine the 301 URL. Disabling it will end the use of tcs3_media urls.

Hi,

This plugin uses the Amazon AWS SDK for PHP to facilitate all connections to S3. This will ensure constant compatibility even as their API landscape changes. That being said, the SDK determines the endpoint URL once you’ve passed the region and S3 bucket name to it, which is why there’s nothing in my plugin you can use to “force it around.”

Looks to me like the API you found at developer.wordpress.com is for wordpress.com sites only. This plugin gets installed into a self-hosted wordpress instance (www.remarpro.com).