We changed our privacy policy. Read more.

Hot answers tagged

3

Fixed: I found ini_set('memory_limit', '64M'); in /system/expressionengine/third_party/assets/sources/s3/source.s3.php and changed it to 1024M


2

All you have to do is move the files to S3 from within Assets’ File Manager itself. If you do that, all of your existing data will automatically start pointing to the new location on S3.


2

Turned out the update seemed to change my S3 location; I updated them to the correct server and they started working again. Latest version of the add-on doesn't seem to have this issue anymore.


2

Take a look at CE Image. Can implement dynamic resizing based on request (use segment variables or GET variables for the dimension parameters on the CE Image template tag). Will save manipulated images to Amazon S3. Can be used in conjunction with Channel Images (just don't bother with the Channel Image's resizing feature and rely completely on CE Image ...


2

When updating files connected to a CloudFront distribution you can speed up the required waiting period by invalidating the modified files. In many cases this reduces the waiting period to update CloudFront edge locations from days to under an hour. Details here: http://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/Invalidation.html


1

A good way to do this is to cache the output of the tag. You can use built-in EE tag caching or something like CE cache, either with fragment caching or full page static. This way you're getting the resized URL and CE Image doesn't keep hitting S3. We've had extremely high traffic sites where we actually create a local redis key/value store to keep track ...


1

I know this issue has been addressed multiple times in the support forums (and possibly already on EE Stack Exchange), but hopefully answering here too will be helpful to others down the road: The long URLs are the automatic naming convention that CE image uses to prevent naming conflicts, and to mitigate the possibility of overwriting images. However, you ...


1

There's no hook for this in Assets, so you'd have to hack the add-on to add it. Look at line 821 of sources/s3/source.s3.php ... right after this line: $headers = array(); You can add something like: $ext = strtolower(pathinfo($file_path, PATHINFO_EXTENSION)); if($ext == 'pdf') { $headers['Content-Disposition'] = 'attachment'; } Of course, this isn'...


1

No there's not, but there's nothing stopping you from using a global variable for this purpose.


1

We've been working like maniacs to hit a deadline on this project, and hadn't had time to deploy the updated version of Assets that P&T's support quickly provided; although I did notice yesterday that the file I was testing this issue with had updated... apparently it just took a few days. I strongly suspect this was a problem for us because we're using ...


1

Assets recently added support for setting bucket names in config.php, like this: $config['assets_source_settings'] = array( 1 => array ( 'access_key_id' => 'key-id-goes-here', 'secret_access_key' => 'secret-key-goes-here', 'bucket' => 'bucket-name-goes-here' ) ); That by itself should be sufficient to ...


1

Enabling cURL in PHP resolved this issue.


1

There are a couple other PHP settings you might need to adjust to allow for large files to be uploaded. Try also increasing these two: max_input_time 300 max_execution_time 300 You may also peek at your php error log file to see if anything more specific is getting logged there.


1

As of version 2.1, you have to hard-code the source folder: source-folder/{assets_field:server_path} However, a solution for this is in active development for version 2.2.


1

Per original question poster's comment above: Thanks, Lisa. Ended up tracking this one down, and updated my original post. This was a firewall issue. May be something to look at for the future though, that if Assets doesn't get a valid response from S3, that some error is displayed. As always, thanks for your help!


1

Two ways: You could mount s3 using s3fs-fuse^ onto your structure, so EE would experience it as a local file-system and the URL could be the s3 bucket URL. Another way is to use aws s3 sync^^ to synchronise the upload/media folder with s3, that way EE just uses the local file-system and your visitors use s3. ^ https://github.com/s3fs-fuse/s3fs-fuse ^^ ...


Only top voted, non community-wiki answers of a minimum length are eligible