Yeah, that'd be a temporary solution until you figure out the proper
configuration: just add a bypass *on the filter* for your directory.
About the debugger: there's a magic thing called remote debugging. I
don't know how it works in eclipse, but you need to start Magnolia (ie
the JVM) with extra parameters such as "-Xnoagent -Djava.compiler=NONE
-Xdebug -
Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005". Of
course that slows things down A LOT, so you might not want to do this
in production, but I do this all the time on my machine, while I don't
run tomcat/jetty from my IDE.
Also, you might want to use jmx to flush your cache instead of losing
time activating pages ;)
Have a look at CacheConfigurationSetupTest (in m-m-cache/src/test),
especially if you have the shell module. Using similar code, you might
be able to figure out the proper configuration for your case. (and the
wiki would be a great support to document that research). Since the
"bypassWhenAuthenticated" voter isn't covered by this test, it could
also be that it's just buggy....
-g
On Aug 8, 2008, at 7:41 PM, Ruben Reusser wrote:
have you tried just to remove the magnolia cache filter?
Ruben
Will Scheidegger wrote:
Hi Ruben
Thanks for the support. As you might see below, I tried this about
an hour ago. Unfortunately this had no effect!
I now also added a "bypass" config node as it was used in Mag
3.6M1, but this did not solve the problem either.
I'm thinking about trashing the cache module and trying to run Mag
without it or maybe adding the cache module from mag 3.6M1 - which
would be a drag too because it has the tendency to keep css files
to itself after a while...
will
On 08.08.2008, at 18:52, Ruben Reusser wrote:
Will,
I had a similar problem - I ended up changing the allowd cache
from / to /bla and the deny cache to /, restarting the server and
making sure my browser is not caching it as well (clear browser
cache).
Ruben
Grégory Joseph wrote:
Is it really caching it, or just serving what's been cached
previously ? ;)
Plugging your debugger in the CacheFilter should help figuring
out what's going on.
-g
On Aug 8, 2008, at 6:44 PM, Will Scheidegger wrote:
Now I even tried this:
- cachePolicy/voters/urls/include/all/pattern: /none
I.e. an url which does not exist. And since this is the only
include pattern... I do really not know why Magnolia is _still_
caching the pages!?!
On 08.08.2008, at 17:55, Will Scheidegger wrote:
Sorry for the second "urgend" post today, but we need to go
only with an update and it's giving me a very hard time.
We have a closed user group where pages are personalized with
user data etc. after the user has logged in. Therefore it's an
absolute MUST that the cache is turned off on these pages. This
has worked fine so fare (Mag 3.6 M1) but now with Mag 3.6.1
pages seem to get cached no matter what I'm trying.
Settings I have tried under config:/modules/cache/config/
configurations/default/ What I tried:
- cachPolicy/voters/bypassWhenAuthenticated/enabled = true
-> did not work!?
- cachPolicy/voters/urls/excludes/my_cug/pattern = /url/to/
cug/root/folder/
-> did not work either!?
I did not restart the server so far though. Could that be the
problem? Or what am I doing wrong?
Again:
- I need caching to be turned off, when a user is logged in
- If this is not possible, I need caching to be turned off for
a certain url and all pages below it
Any help warmly (desperately) appreciated!
will
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
