If Magnolia cache is source of your problems, then simply switching off cache
filter in Magnolia instance should make the issue go away. That would be good
first step for looking into it. If that doesn't help, you might want to add
DumpHeaderFilter in your filter chain (I would suggest someplace
Hi Jonatan, did you found a solution for that problem? I'm facing same problem,
but I noticed that those values are "sometimes" updated, I did a new categories
import on 2 different servers, and on one I have new data in Select Field, on
second one - I don't.
Looking for solution
Thanks
Mariu
Hi again.
The page dialog does actually not work. Only the first time it loads the
values. On subsequent calls, it loads the same values again without fetching
from the repository.
Has anyone any ideas on how I can debug this?
I don't even know where to start...
Best,
Jonatan
--
Context is
Jónatan Einarsson wrote:
> The only interesting log entry I can find is this:
> The defaultPageCache property is not set for the cache CacheFilter, falling
> back to defaultPageCache
>
> The defaultPageCache is acually set in the config. I wonder why I get this.
> If it is not reading the defau
Hi Again.
This just got weirder.
I use yaml to include a tab that has this select box. When the tab is used in a
component dialog, it displays the old (perhaps cached?) values. When it is used
in a page properties dialog, it works fine and I get the new, real values. Are
the component dialogs c
Hi again.
The only interesting log entry I can find is this:
The defaultPageCache property is not set for the cache CacheFilter, falling
back to defaultPageCache
The defaultPageCache is acually set in the config. I wonder why I get this. If
it is not reading the defaultPageCache value is it per
Hello Maik.
I have already disabled the cache by setting enabled: false in the cache filter
config.
I have also tried to set magnolia.develop=true in the default magnolia
properties file.
No luck :(
I am using the same settings on my dev server as I am using on my local setup
where this works
Hi Jonatan,
Magnolia caches responses per default in production mode:
https://documentation.magnolia-cms.com/display/DOCS/Cache+core
The easy solution: just disable the cache. From there you can build up your own
strategy for (avoid) caching dynamic contents.
Cheers, Maik
--
Context is ever
