[Kate]

I have an issue where the images are not loading properly from Amazon S3 within the context of the Connection plugin’s views.

Everything worked fine until we switched to S3 a week or so ago.

We are on WP Engine in case that helps.

EXAMPLE: It’s trying to load the image from /nas/content/live/northriskpart2/wp-content/uploads/connections-images/austin-borgerding/Au-Borgerding1.jpg.jpg

That url gets an error.

But loading from https://northriskpar…gerding/Au-Borgerding1.jpg.jpg works fine.

Seems like this might be a server variable issue on the plugin end… Any way to fix this?

Test at http://northriskpartners.com/about-us/our-people/apollo-team-members/char/A/

• This topic was modified 6 years, 7 months ago by Kate.

Attachments:

You must be logged in to view attached files.

[Steven Zahm]

@ northriskpartners

Connections has a security check in place to check if the image is within the local uploads path because it manipulates images on demand. The local file path check is to help ensure that third party (malicia threats) can not use the image processing code to inject “bad stuff” into the site.

I can only assume the path in the screenshot is actually correct for your site’s content in the S3 bucket. Is it?

Probably the easiest solution… does the plug you are using to add S3 support only exclusions. If it does, I would suggest excluding the connections-images folder.

The only other solution I can think will only work if the other plugin author would be will to add support specifically for Connections.

Or perhaps, maybe it might be possible to add a “shim” to Connections to work with the S3 plugin you are using. Which is?

Hope this helps!

[Kate]

Steve,
Thanks for your reply.

We are not using an S3 plugin – our hosting provider, WP Engine, makes all the connections for us. The actual connection is behind the wall.

I can only assume the path in the screenshot is actually correct for
your site’s content in the S3 bucket. Is it?

The path in the screenshot is our local server path, not the S3 path.

Probably the easiest solution… does the plug you are using to add S3
support only exclusions. If it does, I would suggest excluding the
connections-images folder.

I’ll check with WP Engine to see if they allow exclusions – would work if they do!

All images on the site are loading properly from S3 with the exception of images that utilize the Connections plugin. This leads me to believe it’s an issue with the way Connections plugin is generating the paths (or maybe the fallback…). By that I mean that surely WordPress is running security checks on manipulated images, and the issue is not occurring with non-Connections images. Is there a WordPress variable or something like that that Connections uses to generate the paths?

Thanks in advance for your continued support on this topic!

Toby

[Steven Zahm]

@ northriskpartners

I know other users use Connections on WP Engine just fine and not have run into this before. Can I have WP admin and FTP access to your staging instance on WP Engine so I can debug this thoroughly?

re: Is there a WordPress variable or something like that that Connections uses to generate the paths?

Connections does use the same login and constants WP uses for the wp-content folder path. I basically copy/pasted this from the WP core code to create my own version of the login so I could define the path without using the year/month folder structure… I needed a custom folder structure that made sense for the directory. This could have been accomplished with filters, but then other plugins would have conflicted causing all sorts of image related problem for me.

You can see the image path that Connections generates on the Connections : Tools admin page under the System Info tab. Is this correct?

Also, the security checks that Connections does in addition to what WordPress does. It does a local file path check before processing images. This is done because Connections has the ability to generate images scales/crops on demand. For example, like what TimThumb does. I believe it is this check that is failing because the S3 bucket is no a local path. I believe I may have to add some kind of tweak or workaround for your use case in your environment which is why I’ve asked for access to your staging instance on WP Engine. Without this access and being able to debug firsthand, I doubt I’ll be able to address this further.

[Toby]

This reply has been marked as private.

[Kate]

p.s. I wasn’t logged in with my previous reply, so I cannot see it anymore. Any way to assign that private comment to my account so I can view it?

[Author]

Posts