Peter,
Unfortunately I haven't found a pattern. It seems quite random,
basically during random clicking around our site. My test was to go
visit several collections in communities which use custom XMLUI themes,
and by a few collections into this exercise I'd see mismatched elements
(CSS
Hi Alan,
great to hear that disabling the pipeline cache did not substantially
increase your memory footprint in development.
Did you see the same on production?
best regards,
Bram
--
[image: logo]
*Bram Luyten* *@mire*
*2888 Loker Avenue East, Suite 315, Carlsbad, CA. 92010*
*Esperantolaan
Hi Alan,
Disabling cache all-together was too high of a performance cost for us.
Depending on your usage, you might be fine though.
If you can narrow your problems/grievances with incorrectly-cached-pages to
a number of certain activities / use-cases, then it is worth it to debug
those, and find
Hi,
So for now I *seem* to have found a work around: setting the pipeline
to noncaching. I found the hint referenced in Jira DS-298, and have
modified my code[1] to use the noncaching pipeline type.
It's been working on my development instance for a few hours now, and
I've been refreshing
All,
I've been battling with overly-aggressive XMLUI caching ever since
version 1.7. We use DSpace 3.1 with 14 different XMLUI themes, and
after a fresh restart it only takes around 5 minutes before themes start
getting jumbled between communities. 1.8 introduced the ability to
clear the
5 matches
Mail list logo
