When I navigate to URL1 it shows blogpost coming under category: Technology, which is the expected behavior. Now, if I navigate to URL2 then instead of listing post from category: General, it shows the post from category: Technology. Now, If I wait for few minutes in URL1 and navigate to URL2 then URL2 lists posts from category: General.
I tested the behavior in different browser and the result was same which concludes that this is related to Umbraco's/Articulate's internal cache. Can somebody drop some pointers on where needs to be looked-up to analyze and fix this issue?
As I suspected, issue was with caching. There are 2 methods in Articulate's UmbracoHelperExtensions.cs - GetContentByTag and GetContentByTags which has code-block as below:
I temporarily commented-out caching logic to make it working. This sounds weird, but it works.
Cache issue in categories and tags lisitng
Hello,
I was customizing Articulate blog and noticed some caching issue with category listing and tags listing. Here is the quick summary.
Let's say, I have 2 category URL:
When I navigate to URL1 it shows blogpost coming under category: Technology, which is the expected behavior. Now, if I navigate to URL2 then instead of listing post from category: General, it shows the post from category: Technology. Now, If I wait for few minutes in URL1 and navigate to URL2 then URL2 lists posts from category: General.
I tested the behavior in different browser and the result was same which concludes that this is related to Umbraco's/Articulate's internal cache. Can somebody drop some pointers on where needs to be looked-up to analyze and fix this issue?
Any help will be appreciated.
Thanks.
I even tried rebuilding indexes as metioned here https://our.umbraco.org/documentation/Reference/Common-Pitfalls/#rebuilding-indexes but that didn't helped either. Does anyone have any clue on why this is happening so?
As I suspected, issue was with caching. There are 2 methods in Articulate's
UmbracoHelperExtensions.cs-GetContentByTagandGetContentByTagswhich has code-block as below:I temporarily commented-out caching logic to make it working. This sounds weird, but it works.
Thanks.
is working on a reply...