Problems with Multiproperty

volume_up

A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More.

volume_up

A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More.

Home / Forums / Legacy forums / Episerver 7 CMS /

Problems with Multiproperty

Tore Lervik

Vote:

expand_less 0 expand_more

We got the Multiproperty to work well with EPiServer 7, but we have one issue. It seems the property is never initialized when the app loads or after an iisreset.

It works correctly in edit mode and when we see the page in edit (cause it's not cached(?))
The property has the correct values on the page after we publish
The property is null on the page after a iisreset or fresh iis instance.

#65572

Feb 01, 2013 12:42

Marija Jemuovic

Vote:

expand_less 0 expand_more

Can you post your property definition? Could it be that you have forgotten virtual keyword?

#65605

Feb 01, 2013 17:28

Tore Lervik

Vote:

expand_less 0 expand_more

We forgot to set stringDelayedLoadThreshold="0" in episerver.config / sitesettings.

#65700

Feb 06, 2013 13:19

määäts

Vote:

expand_less 0 expand_more

#71624

May 24, 2013 11:52

Vote:

expand_less 0 expand_more

Just a side note.

If not defined in episerver.config, stringDelayedLoadThreshold is 255 by default. (in CMS 7)

#75853

Oct 08, 2013 22:26

error This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.