Hi Will,
I've been fighting with this and related issue for a few hours now.
This seemed - at first - related to leopard's firewall, but I'm really
still not sure exactly what's going on. Strangely enough, it seems now
that it behaves better when Magnolia/Tomcat is accessed from a
different machine - could you try that ?
-g
ps: try the RC instead - it's just been released yesterday, not
officially announced because of the issue I'm having right now.
On Jul 16, 2008, at 6:16 PM, Will Scheidegger wrote:
Dear Magnolias
Before I create a JIRA issue I wanted to ask you if you have seen
the same effects: In Mag 3.6m3 every once in a while the admin css
info gets lost and the page displayes like this:
http://www.fastforward.ch/personal/will/mag36_loosing_css.png
Most of the time one does not notice it because the css is fetched
from the browser's cache, but when you clear the cache you end up
with an unusable Magnolia. This _is_ a show stopper of corse.
- When you try to load /cms/.resources/admin-css/admin-all.css in
these cases, all you get is an empty page (no error message, nothing)
- All the files in the magnolia cache folder are empty (don't know
if the admin css stuff get's cached in the first place)
- clearing the instance's "tmp" folder did not change anything eiter
=> Restarting Magnolia solves the problem!
Any ideas or experiences on your part?
-will
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
