Images do not render from Content Hub DAM about synthesis

[blipson89]

Fixed in Synthesis 9.1.2

Thank you for the help @rkuchler

[jroho]

Do you want to request a feature or report a bug?
I think this issue needs to be reopened.

What is the current behavior?
This issue appears to persist when accessing Url from ContentHubImageField which is derived from IImageField :: FileField. I followed the instructions to implement ContentHubImageField, but there appears to be issues accessing Url, which is inherited from Synthesis.FieldTypes.Interfaces.IFileField, and IImageField. It's always null for images set from Content Hub.

If the current behavior is a bug, please provide the steps to reproduce.

1. Install and configure the Sitecore Connect™ for Sitecore DAM 2.0 module in a Sitecore 9.3 XP solution
2. Add an image field to any template
3. Create an item based on that template
4. In the content editor edit that item and click on the Browse Sitecore DAM link to add an image
5. Preview the item and note that the image does not render
6. Url property is always null for the ContentHubImageField (We don't use Render() or ImageFor() as we have a custom library that inherits from IImageField)

What is the expected behavior?
I would expect to be able to access data member, Url, from ContentHubImageField, derived from IImageField :: IFileField. I also added IsContentHub property to the IContentHubImageField interface. This property is useful when exposed here.

My pr does solve the issue for us (we are fully integrated with content hub), if you want to take a look: #97

Please mention your Sitecore version and Synthesis version.
Sitecore 9.3
Synthesis 9.1.0.2

[blipson89]

Hi @jroho,

It looks like a potential fix was released a while ago but I forgot to follow up. Is this issue resolved?

Thanks,
Ben

[jroho]

Hey Ben, Yep, already using it on a newer project. Working as intendended without the need to override your dll. Thanks, Jesse

…

On Sat, Apr 23, 2022, 10:06 AM Ben Lipson ***@***.***> wrote: Hi @jroho <https://github.com/jroho>, It looks like a potential fix was released a while ago but I forgot to follow up. Is this issue resolved? Thanks, Ben — Reply to this email directly, view it on GitHub <#93 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AALJHDMWB53UYS4VTH4PJ3LVGQGYJANCNFSM45JK5CTQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[blipson89]

Glad to hear it! I'm going to close this issue out then.