On May 17, 2007, at 13:49 , David Smith wrote:
Well... it seems that Magnolia builds a list of page templates on
startup in memory. Then on listing them for adminCentral, it looks
at the in-memory list instead of actually querying templates from
the repository. Great optimization for a faster experience, but a
pain for instances under heavy development.
Ha! Yes, sorry I didn't quite follow this thread; you're talking
about the dropdown template selector in the website tree.
Are you using 3.0.2 ?
Never invested the time to corner the issue and provide a patch
though. I should. I'll try to reproduce the issue and provide
logs for it tonight (US/Eastern Daylight time).
Great - ping me if you need some directions.
g
David,
Could you please elaborate your experience? It seems related to
MAGNOLIA-1394 [1], so you might want to comment there.
Thanks !
g
[1] http://jira.magnolia.info/browse/MAGNOLIA-1394
On May 17, 2007, at 13:05 , David Smith wrote:
You beat me to the punch. It's been my experience that every
time I add/move a page template, it requires bouncing the service.
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
