Hi Gregory, i noticed afterwards, that the update problem still remains. When changed some content the public instance did not deliver the new page, but the data stored in cache. I updated the header.inc with "cache-control" "no-cache" to be shure, that the browser does allways request the data from server. (I tried with Firefox and IE on Linux and XP). I noticed, that deleting the cache directory (as told in this thread before) on the public instance had the wished effect. But i could not find a way to clear the cache manually from within the admin interface. (if you know e.g. typo3 there is manually clearing of the cache a often done task during website content creation).
Because i'm new to magnolia i skipped exploring caching properties, instead i disabled the cache completely. It is very important, for every editor/deployer that published content can be seen at once in the public Instance. As far as i can see at the moment, the internal caching of magniolia 3.0.2 does not work correctly, e.g is not properly configured. The correct behavior would be, that any change in the website content repository must delete or refresh the assigned cahing data. But this does definitively not happen. Uli 2007/6/25, Grégory Joseph <[email protected]>:
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 ----------------------------------------------------------------
---------------------------------------------------------------- for list details see http://documentation.magnolia.info/docs/en/editor/stayupdated.html ----------------------------------------------------------------
