How do I fix error with the new (4.6.0) Drupal views image handler for CiviCRM contact images

Question

Just upgraded to 4.6.0 and now I see that the CiviCRM Contact Image field in Drupal views now uses the views image handler! Awesome! Prior to 4.6 it was just a string containing a URL to the image. Thanks to @Shawn Duncan for his efforts and contribution.

However, I can't get it to work. The image URL it produces gives a 404

Example URL that returns 404:

http://example.com/sites/example.com/files/example.com/civicrm/contact/imagefile%3Fphoto%3Dmbd_logo_01cf3f5560578c6554b9ba009f6b42b7.png

But the actual working URL to the file is:

http://example.com/sites/example.com/files/civicrm/custom/mbd_logo_01cf3f5560578c6554b9ba009f6b42b7.png

So it's inserting an extra example.com after the /files/ and it's using this /contact/imagefile%3Fphoto%3D instead of the actual path to my custom uploads.

---

[Edit]

Using Drupal image presets is broken in 4.6 since at least 4.6.6; if you select an image style in Views, it mangles the URL to something like

<img typeof="foaf:Image" src="http://styles/medium/http/example.org/civicrm/contact/imagefile?photo=bsglo‌​go_49524b829beb4448767ee75a42f2dcc0.jpg&amp;itok=dGLXdcig" width="220" height="220" alt="" title="">

Is there a suitable workaround?

Answer 1

Your site is affected by CRM-16009 - URL for Contact Image in View incorrectly generating.

That URL should look like this -

http://example.com/civicrm/contact/imagefile?photo=mbd_logo_01cf3f5560578c6554b9ba009f6b42b7.png

rather than this -

http://example.com/sites/example.com/files/example.com/civicrm/contact/imagefile%3Fphoto%3Dmbd_logo_01cf3f5560578c6554b9ba009f6b42b7.png

The civicrm/contact/imagefile handler permits CiviCRM to provide its permissions checks on whether the image in question should be served up.

Since that code was merged, there's a good chance it worked for someone and this may be fixable in configuration. It looks like the URLs you're getting from Views are confused - possibly by CiviCRM configuration, or by an issue with the views implementation as it currently stands, possibly an incorrect assumption in code about the location of CiviCRM codebase or system files, etc.