Problem with properties having UIHint.Image on EPiServer.CMS.UI 7

Problem with properties having UIHint.Image on EPiServer.CMS.UI 7.18.0

topi.santakivi

Vote:

Hello. Updated EpiServer.CMS.UI to version 7.18.0 earlier this week.

Now, when I try to change the value of any Url property with UIHint(UIHint.Image),
the page/block doesn't get any event indicating the value has changed, and thus i cannot
publish the latest version of the page/block. If i remove the UIHint and select the image
with the generic selection box, the changed event is triggered and the publishing works normally.

So, this doesn't work:

[UIHint(UIHint.Image)]
[Display(
 Name = "Image",
 GroupName = SystemTabNames.Content,
 Order = 110)]
public virtual Url Image { get; set; }

This works:

[Display(
 Name = "Image",
 GroupName = SystemTabNames.Content,
 Order = 110)]
public virtual Url Image { get; set; }

We are seeing this same problem on two different projects, both on 7.18.0.

#114628

Dec 16, 2014 15:20

Joshua Folkerts

Vote:

I am having the same issue. I know we should be using CotnentReference for images, but the fact this was an upgraded site and this is how it was done post episerver 7.5, we didn't want to go update all the properties and then update all the values etc.. Is there a solution for this?

#114637

Dec 16, 2014 18:16

Daniel Hart

Vote:

We're also having the same issue. I registered a developer incident to Episerver, so let's see if they'll come up with a fix. There's no way we can go to production with the current release, as we're using the UIHint.Image + Url combination in practically all commonly used content types.

#114721

Edited, Dec 19, 2014 8:31

Peter Tollnes-Flem

Vote:

We're having the same issue as well.

#114744

Dec 19, 2014 12:18

Ørjan Horpestad

Vote:

I already replied in Petter's thread, but this seems to be the same issue.

#114746

Dec 19, 2014 12:23

Miriam Y

Vote:

Update to latest package released today, and the issue seems to be resolved.

#114771

Dec 20, 2014 0:09

Kjetil Simensen

Vote:

I can confirm that update to epi 7.19.1 solves this problem

#114983

Jan 07, 2015 10:15