Nested Content rendering in list ConvertPropertyToNestedContent
Hi Lee,
Nice one on the latest update amends for 0.3.0. Love it. It speeds things up within the backend tremendously especially when i have list of modules.
I have got a quick question about rendering it on the front end. When i have a list of nested modules.
I've tried checking it with the mini profiler. When i have for example 6 list modules to be rendered. It takes up at least 10-15 seconds to load the page during first load.
It loads about 5-7 seconds during the second load which is fine.
It's only during the first load. When i check the profiler, there's multiple calling to ConvertPropertyToNestedContent which i guess is needed but not on the second load.
Nested Content rendering in list ConvertPropertyToNestedContent
Hi Lee,
Nice one on the latest update amends for 0.3.0. Love it. It speeds things up within the backend tremendously especially when i have list of modules.
I have got a quick question about rendering it on the front end. When i have a list of nested modules.
I've tried checking it with the mini profiler. When i have for example 6 list modules to be rendered. It takes up at least 10-15 seconds to load the page during first load.
It loads about 5-7 seconds during the second load which is fine.
It's only during the first load. When i check the profiler, there's multiple calling to ConvertPropertyToNestedContent which i guess is needed but not on the second load.
Was wondering if you encountered this before.
Thanks as always
Amended, it's normal nested content list (not nested nested content). Just noticed this.
Any idea?
Thanks
Hi JLon,
(I've been away on holiday, hence no reply)
The
ConvertPropertyToNestedContent
should only be called when Umbraco is getting the NC property value. Which I believe is then cached by Umbraco.About the caching, I'm not sure if having debug mode enabled makes any difference? It seems strange that it's being called multiple times.
Cheers,
- Lee
Thanks Lee, yup it's only during first load. So it's cached after that.
I'm thinking it's because I've got Nested Content wrapped with Vorto. So it takes longer to get the data back on first load.
But after the first load it's loading super quick
is working on a reply...