November Happy Hour will be moved to Thursday December 5th.
November Happy Hour will be moved to Thursday December 5th.
This puzzled me
Some questions.
I'd like to know if this issue persist if you disable all caches.
We encountered this after updating a bunch of Episerver.* packages. We had to revert the update due to this bug. Below is our git diff:
- <PackageReference Include="EPiServer.CMS.AspNetCore.HtmlHelpers" Version="12.22.0" />
- <PackageReference Include="EPiServer.CMS.AspNetCore.Routing" Version="12.22.0" />
- <PackageReference Include="EPiServer.CMS.AspNetCore.TagHelpers" Version="12.22.0" />
- <PackageReference Include="EPiServer.CMS.Core" Version="12.22.0" />
- <PackageReference Include="EPiServer.Framework" Version="12.22.0" />
- <PackageReference Include="EPiServer.CloudPlatform.Cms" Version="1.6.2" />
- <PackageReference Include="EPiServer.Find.Cms" Version="16.3.1" />
+ <PackageReference Include="EPiServer.CMS.AspNetCore.HtmlHelpers" Version="12.21.8" />
+ <PackageReference Include="EPiServer.CMS.AspNetCore.Routing" Version="12.21.8" />
+ <PackageReference Include="EPiServer.CMS.AspNetCore.TagHelpers" Version="12.21.8" />
+ <PackageReference Include="EPiServer.CMS.Core" Version="12.21.8" />
+ <PackageReference Include="EPiServer.Framework" Version="12.21.8" />
+ <PackageReference Include="EPiServer.CloudPlatform.Cms" Version="1.6.1" />
+ <PackageReference Include="EPiServer.Find.Cms" Version="16.3.0" />
Had some time to test today.
@Eric Herlitz I don't have any ResponseCache or OutputCache implemented, and disabling all caches as suggested helps. (The site is as expected realy slow but the problem does not persist)
@huseyinerdinc I also recently updated my packages, but I'm not entirely sure the problem wasn't there before.
These are the package versions I currently use (so quite similar):
<PackageReference Include="EPiServer.CloudPlatform.Cms" Version="1.6.1" />
<PackageReference Include="EPiServer.CMS" Version="12.31.2" />
<PackageReference Include="EPiServer.CMS.AspNetCore" Version="12.22.0" />
<PackageReference Include="EPiServer.CMS.AspNetCore.TagHelpers" Version="12.22.0" />
<PackageReference Include="EPiServer.CMS.AspNetCore.Routing" Version="12.22.0" />
<PackageReference Include="EPiServer.CMS.UI.AspNetIdentity" Version="12.31.2" />
<PackageReference Include="EPiServer.Find.Cms" Version="16.3.0" />
<PackageReference Include="EPiServer.Framework" Version="12.22.0" />
We have confirmed this is a bug and are working to fix it: Bug - CMS-38033
Also note the workround in the bug description:
"Link collection properties might load data incorrectly when lazy loading is enabled. The error is often intermittent and can be worked around by disabling lazy loading (set ContentOptions.PropertyLazyLoadThreshold = 0)."
Are there any downsides of setting ContentOptions.PropertyLazyLoadThreshold = 0? Is this what the bugfix will be?
Hi all,
I yesterday stubled on some strange behaviour in a CMS 12 (latest packages) website I'm working on.
Behaviour:
On a specific page there is a LinkItemCollection property that is used to show some links to other parts of the site.
After a restart the list would not show any links to the visitor, but when I view the page in the CMS in preview mode the links are visible. After a publish the links are visible to the visitor, and after a restart they are gone again.
What I found out so far:
It seems that caching plays a part in this. If I load the page, check if the collection is null and then
invalidate the cache and load the page again the links are there.
Then I tried to find out, why an incomplete page was cached. I implemented my own ObjectInstanceCache to intercept the page being cached, and use the callstack to find the origin.
It seems now, that on loading the homepage. The children (including my page) of the homepage are loaded:
And in loading this children I see the page being cached without the QuickNavigationLinks.
Then when I navigate to this page, this page is loaded from cache, and no links are shown.
My questions:
Is this something that makes sence?
Am I missing something here?
Why is the page cached differently when loading is from GetChildren in comparison to the normal Get of the ContentLoader?