Take the community feedback survey now.

Problem loading All Properties view after upgrade to CMS UI 11.37.x when the content type has property decorated with UiHint.Image and uses Mediaflow

Vote:
 

Hi,

Update: 

We found that it is mediaflow's image plugin/add-on for CMS 11 that clashes with Episerver.UI.Core 11.37.0 and causes this.

https://world.optimizely.com/documentation/Release-Notes/ReleaseNote/?releaseNoteId=CMS-27106

https://support.mediaflow.com/hur-installerar-jag-mediaflows-episerver-plugin

I have created a vanilla CMS 11 project and can reproduce the problem there with a model containing a property of type ContentReference decorated with UIHint.Image, in combination with the Mediaflow image plugin package for CMS 11 that is available on the link above.

I have contacted Mediaflow Support and made them aware.

---

After updating an Episerver CMS project from 11.20.x to the latest CMS 11 minor version (11.37.1), all pages and blocks where the content type has a property (ContentReference) that is decorated with the UiHint.Image attribute no longer loads in All Properties view. 

I'm getting this error in the epi.js:

After setting  <clientResources debug="true" /> in the <episerver.framework> section in web.config (and closing the Versions gadget that gives a lot of noise in the debugger), I get this:

On-page edit kind of works, the content and the UI fields are displayed and I can drag an image into properties decorated with UiHint.Image in on-page edit mode, however when clicking in the field for the image I get this error:

lang.hitch: scope["_onButtonClick"] is null (scope="[Widget uniqName_178, uniqName_178_0]")

and I don't get any interaction, should there be a dialogue appearing there?

The updates to packages (done using nuget update):

The project is also using Geta.404Handler, and the update was applied there as well:

Has anyone else had this problem?

Best regards,
Linda

#304349
Edited, Jun 30, 2023 7:31
Vote:
 

Hello, 

Better late than never to the party. But we had the exact the same issue. We resolved it by removing the extra button in the template string in the JS-files:

<div data-dojo-type=\"dijit/form/Button\" data-dojo-attach-event=\"onClick: _onButtonClick\" data-dojo-attach-point=\"button\" data-dojo-props=\"label:'...'\" title=\"Välj bild från EPiServer\"></div>

The issue seems to be that MFP tries ti piggyback on an event that doesn't exists anymore. And since now there is a new button next to the the image component. We could just remove the double button.

I am sure we could have dug up and found the correct attach-point and and find the corrrect attach-event to make the button work again. It was just not necessary for us.

#324763
Jul 01, 2024 14:33
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.