Ulrich,
I fail to see how this would be a "solution". Under "normal"
conditions, activating a page on a public instances should flush
Magnolia's cache.
Disabling the cache just hides your actual problem, if any at all.
You said earlier it was your browser cache "fooling" you. Can you
elaborate on that? What browser are you using, how is its cache
configured?
Cheers
g
ps: please don't remove the relevant parts of the emails you're
replying to. you say here "for all users with the same problem", but
one has no idea what problem you're talking about - and it's more
than misleading with the current thread title. One could think, upon
reading this single mail, that activation in Magnolia does not work
unless you disable the cache, and that's ... disinformation.
On Jun 25, 2007, at 12:18 , Ulrich Metzger wrote:
For all users with the same problem. The solution which works for me,
is to disable the cache
in the magnoliaPublic instance. To achive this just go to
Configuration->cache and set the property "active" to false.
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
