problems with rc4 and stylesheet

[Magnolia - User mailing list]

I know there were some messages in the last few weeks about 3.6 and
disappearing css from the admin - I just got this problem in RC4 as well
- can I do something to help solve the issue? The problem seems to
appear after working a bit with magnolia (new war import in exlipse,
tomcat5.5, jdk1.6) - I add one or two templates, reload a couple of time
and then make an error in a jsp of a template, correct the error and the
css is gone.

Thanks

Ruben

----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------

[Magnolia - User mailing list]

Hi Ruben,
could you try to switch off the cache (remove cacheFilter) and see
whether problem disappears or not.
Also could you send the response headers next time when you encounter
the problem?

I have created the http://jira.magnolia.info/browse/MAGNOLIA-2280 to
keep all the evidence in one place. Could you please attach your
findings to the issue?

Thanks,
Jan

On Tue, 2008-07-22 at 22:31 -0700, Ruben Reusser wrote:

> I know there were some messages in the last few weeks about 3.6 and
> disappearing css from the admin - I just got this problem in RC4 as well
> - can I do something to help solve the issue? The problem seems to
> appear after working a bit with magnolia (new war import in exlipse,
> tomcat5.5, jdk1.6) - I add one or two templates, reload a couple of time
> and then make an error in a jsp of a template, correct the error and the
> css is gone.
>
> Thanks
>
> Ruben
>
> ----------------------------------------------------------------
> for list details see
> http://documentation.magnolia.info/
> ----------------------------------------------------------------

----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------

[Magnolia - User mailing list]

After all of a sudden loosing the public css (not the admin css) I  
thought I'd give the cache manipulation a shot also. I added a new  
"excludes" setting for the whole /docroot folder et voila: the css  
files were there again.

What's up with that? Magnolia hates css files in general now?

will

On 23.07.2008, at 11:26, Jan Haderka wrote:

> Hi Ruben,
> could you try to switch off the cache (remove cacheFilter) and see
> whether problem disappears or not.
> Also could you send the response headers next time when you encounter
> the problem?
>
> I have created the http://jira.magnolia.info/browse/MAGNOLIA-2280 to
> keep all the evidence in one place. Could you please attach your
> findings to the issue?
>
> Thanks,
> Jan
>
> On Tue, 2008-07-22 at 22:31 -0700, Ruben Reusser wrote:
>> I know there were some messages in the last few weeks about 3.6 and
>> disappearing css from the admin - I just got this problem in RC4 as  
>> well
>> - can I do something to help solve the issue? The problem seems to
>> appear after working a bit with magnolia (new war import in exlipse,
>> tomcat5.5, jdk1.6) - I add one or two templates, reload a couple of  
>> time
>> and then make an error in a jsp of a template, correct the error  
>> and the
>> css is gone.
>>
>> Thanks
>>
>> Ruben
>>
>> ----------------------------------------------------------------
>> for list details see
>> http://documentation.magnolia.info/
>> ----------------------------------------------------------------
>
>
> ----------------------------------------------------------------
> for list details see
> http://documentation.magnolia.info/
> ----------------------------------------------------------------

----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------

[Magnolia - User mailing list]

On Jul 23, 2008, at 5:59 PM, Will Scheidegger wrote:

> After all of a sudden loosing the public css (not the admin css) I  
> thought I'd give the cache manipulation a shot also. I added a new  
> "excludes" setting for the whole /docroot folder et voila: the css  
> files were there again.
>
> What's up with that? Magnolia hates css files in general now?

Did you try getting a fresh cache config from one of the RCs like I  
suggested earlier ?

-g

----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------

[Magnolia - User mailing list]

I guess it must be the cache - After a while the css was available again
- I then disabled the cache (is there no global property anymore to
disable it?) and now the css works fine.

Ruben

Grégory Joseph wrote:

>
> On Jul 23, 2008, at 5:59 PM, Will Scheidegger wrote:
>
>> After all of a sudden loosing the public css (not the admin css) I
>> thought I'd give the cache manipulation a shot also. I added a new
>> "excludes" setting for the whole /docroot folder et voila: the css
>> files were there again.
>>
>> What's up with that? Magnolia hates css files in general now?
>
> Did you try getting a fresh cache config from one of the RCs like I
> suggested earlier ?
>
> -g
>
> ----------------------------------------------------------------
> for list details see
> http://documentation.magnolia.info/
> ----------------------------------------------------------------

--
=================================================================
 java consulting  - swing, web UI, hibernate, cms, magnolia, jcr
 flash consulting - openlaszlo, flex
 headwire.com, inc ++1 949 595 4365


----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------

[Magnolia - User mailing list]

Yes, of course. This is on a fresh RC 3

will

On 23.07.2008, at 18:30, Grégory Joseph wrote:

>
> On Jul 23, 2008, at 5:59 PM, Will Scheidegger wrote:
>
>> After all of a sudden loosing the public css (not the admin css) I  
>> thought I'd give the cache manipulation a shot also. I added a new  
>> "excludes" setting for the whole /docroot folder et voila: the css  
>> files were there again.
>>
>> What's up with that? Magnolia hates css files in general now?
>
> Did you try getting a fresh cache config from one of the RCs like I  
> suggested earlier ?
>
> -g
>
> ----------------------------------------------------------------
> for list details see
> http://documentation.magnolia.info/
> ----------------------------------------------------------------

----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------

[Magnolia - User mailing list]

On Jul 23, 2008, at 9:27 PM, Will Scheidegger wrote:

> Yes, of course. This is on a fresh RC 3

Ok - just to be sure.

>> On Jul 23, 2008, at 5:59 PM, Will Scheidegger wrote:
>>
>>> After all of a sudden loosing the public css (not the admin css) I  
>>> thought I'd give the cache manipulation a shot also. I added a new  
>>> "excludes" setting for the whole /docroot folder et voila: the css  
>>> files were there again.

So docroot is never cached? Not really what we'd want, strange.

Is this issue happening on a public or author instance? Both?

What's the value of your magnolia.develop property ?

Cheers,

-g

----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------

[Magnolia - User mailing list]

Hi Grégory

On 24.07.2008, at 12:03, Grégory Joseph wrote:

>>> On Jul 23, 2008, at 5:59 PM, Will Scheidegger wrote:
>>>
>>>> After all of a sudden loosing the public css (not the admin css)  
>>>> I thought I'd give the cache manipulation a shot also. I added a  
>>>> new "excludes" setting for the whole /docroot folder et voila:  
>>>> the css files were there again.
>
> So docroot is never cached? Not really what we'd want, strange.

No, not really. I did turn caching back on for the docroot folder  
afterwards and was fine since.

> Is this issue happening on a public or author instance? Both?

When I first reported it, the magnolia admin css files got lost on the  
admin instance (Mag 3.6 m3).
This time, the site specific css files (under /docroot/mysite/css/...)  
on the public instance got lost (Mag 3.6 RC3).

> What's the value of your magnolia.develop property ?

magnolia.develop=false

Cheers,
will
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------