Since the latest core version (19.2.5.2) i'm running more and more into the problem that pages are cached way too long. On the advanced tab of the page properties it is possible to set the caching to a certain value. The default type is 'standard' which is valid for 4 hours. However in most cases this is way to long. Think about productoverviews which change on a regular base and also text pages give problems. I've also found out that setting the 'type' to none without changing the value for how long the page should be cached (default, 4 hours). doesn't have any influence. The page will still be cached for 4 hours!
The workaround for now is to check all page properties whenever a customer reports a problem with missing products of other changes on webpages. But it would be nice that if we set the type of caching to 'none' it actually is none. Anyone else also seeing this problem? Or has a better more generic workaround for this?
Developer forum
E-mail notifications
Page caching not working properly
Rob Lohmann
Posted on 04/10/2011 15:32:04
Replies
Nicolai Høeg Pedersen
Posted on 04/10/2011 16:04:35
The caching have not been changed since - yeah, for a long time.
Whenever you press save on a page or paragraph, the cache for that page is discarded.
If you attach a eCom catalog to a page, that cache is not used at all.
If you are logged into the backend, nothing is cached at all.
If you put things into the Page table not using the API, it is a total different story.
I'll need a description of how to recreate the problem - and maybe a link.
Whenever you press save on a page or paragraph, the cache for that page is discarded.
If you attach a eCom catalog to a page, that cache is not used at all.
If you are logged into the backend, nothing is cached at all.
If you put things into the Page table not using the API, it is a total different story.
I'll need a description of how to recreate the problem - and maybe a link.
Rob Lohmann
Posted on 10/10/2011 08:52:03
Hi Nicolai,
In release 19.2.5.2 I see that improvement 6850 has been made. Could this has something to do with it?
I'm taking the following steps to be able to reproduce the problem; It occurs at http://www.zoeandlola.nl
- Add a new designer to the english and dutch website. Designers are productgroups so manage through the ecom module. Every designer must contain an image and it's own meta url.
- Create a new designer page under 'pages'. The page contains three paragraphs. The first one with some text, the second one for the GroupID, this will be used to create an url to the designer productgroup page and a third and last paragraph for an designer image.
The designer pages on the frontend (http://www.zoeandlola.nl/nl-nl/designers.aspx) is an overview of pages, which are created in step 2. However to get them visible on the dutch website we need to recycle the application pool to get the changes visible. On the english website (the .com domain) changes are most of the times visible immediately.
Hope you can help.
Kind regards,
Rob
In release 19.2.5.2 I see that improvement 6850 has been made. Could this has something to do with it?
I'm taking the following steps to be able to reproduce the problem; It occurs at http://www.zoeandlola.nl
- Add a new designer to the english and dutch website. Designers are productgroups so manage through the ecom module. Every designer must contain an image and it's own meta url.
- Create a new designer page under 'pages'. The page contains three paragraphs. The first one with some text, the second one for the GroupID, this will be used to create an url to the designer productgroup page and a third and last paragraph for an designer image.
The designer pages on the frontend (http://www.zoeandlola.nl/nl-nl/designers.aspx) is an overview of pages, which are created in step 2. However to get them visible on the dutch website we need to recycle the application pool to get the changes visible. On the english website (the .com domain) changes are most of the times visible immediately.
Hope you can help.
Kind regards,
Rob
Nicolai Høeg Pedersen
Posted on 10/10/2011 09:01:30
6850 has nothing to do with it - just a new value added to a dropdown list.
It seems to be the product groups cache that can be the issue.
When you edit in the administration you probably use the .com domain - then there can be some delay on .nl domain in your session - but not new sessions I believe. What happens if you see the designers page in an other browser after they were created?
It seems to be the product groups cache that can be the issue.
When you edit in the administration you probably use the .com domain - then there can be some delay on .nl domain in your session - but not new sessions I believe. What happens if you see the designers page in an other browser after they were created?
Rob Lohmann
Posted on 17/10/2011 08:50:58
Hi Nicolai,
sorry for the late response. Will test this today and get back to you.
Kind regards,
Rob
sorry for the late response. Will test this today and get back to you.
Kind regards,
Rob
You must be logged in to post in the forum