Just curious if anyone knows if this will work with the amazon s3 module....

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

denison’s picture

This patch resolves the URI that comes from S3.

The patch was applied in version 7.x-1.0

infines’s picture

Status: Active » Closed (fixed)
joetsuihk’s picture

Version: 7.x-2.x-dev » 7.x-1.x-dev
Category: support » feature
Status: Closed (fixed) » Needs work

@gridbitlabs Why is this "fixed"?

@denison thank you for the work, sure drupal_realpath is deprecated, can you add some comment explaining this remove, and will this affect local files handling?

jonloh’s picture

Issue summary: View changes

Seems to work with s3fs module, but the position of the cropping target isn't saved...

1kenthomas’s picture

Both 1.0, 1.x-dev and 2.0 versions seem to fail entirely with both current amazons3 and s3fs modules. As do most other crop modules (manual crop seems to have been altered to work).

deneus18’s picture

Hi,
I know this issue is old, but it's still open and I'm facing it today.
I suggest the following patch which keeps the original version of the module working and add Amazon S3 support.
I'm using

ram4nd’s picture

Status: Needs work » Needs review
wannesdr’s picture

I too have come up to this issue. My setup uses the s3fs module.
The patch from #6 doesn't fix the issue for me.

I'm going to test and see if the manual crop module does any better. I will let you guys know.

jenlampton’s picture

@Wannes DR you might try the patch in https://www.drupal.org/project/imagefield_crop/issues/2928174 (if you still care about this problem, 5 years later!) as that one is specifically for the s3fs module.