We have upgraded Sites from 9.1 to 9.6 and the Widen ECL add-on is working fine on classic UI. That means we are able to access the folders, images etc. But when we switch to new UI, the parent level folder(Widen folder) opens, but next-level folders wont open and throw some errors on the cme. Can somebody help to make it work on experience space as well? I have attached the errors snapshot displayed on cme.

enter image description here

1 Answer 1


In general, you want to obtain more information (e.g. Stack Trace) from the ECL log file, but in this particular case, it seems the error message presented to the end user is already quite explicit: the ECL Provider (Widen ECL V2 Provider) returned null for a GetItem request for a given Widen ECL Folder.

ECL Providers (or Connectors) should never return null when ECL wants to get an item which they put in some list themselves. However, in releases before Sites 9.6 you may get quite far without noticing this bug in the ECL Provider.

Sites 9.6 does retrieve ECL Folders (in order to build full paths) from the ECL Providers and therefore, you will quickly get such error if the ECL Provider return null for its own ECL Folders.

See also Custom ECL Provider GetItem method behaving differently in 9.6 environment

  • Just wondering to ask this - the same widen is working totally fine on 9.6 classic UI, but fails to load the folders when switched to experience space. Is this still expected? Commented Jun 22, 2023 at 6:42
  • Yes, that is expected. The new CM/ECL integration is mostly used for the Core Service REST integration (used by Experience Space). Commented Jun 22, 2023 at 7:45

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.