Jason Johnston wrote:
I have this same problem in 2.1.7; it worked fine before we upgraded from
2.1.5.1. I've checked the cache-on-startup config parameter in the xconf
and sitemap and they're both set to false. This is happening in
non-cacheable pipelines, so it's definitely a problem with the catalogue
not being reloaded rather than a pipeline caching problem.
I haven't yet had a chance to try it under 2.1.8-dev; I will hopefully
find some time to test it in the next few days and will open a bug report
if the problem persists.
--Jason
Does this thread explain the behavior?
http://marc.theaimsgroup.com/?t=110563103100003&r=1&w=2
Ralph
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
