16 Apr
2008
16 Apr
'08
2:11 p.m.
If you are using the Magma-PersistencyManager it is
quite simple.
The site contents are stored in magma.
In the new image, when you create a new kernel (of the same name) and
switch it to "PRMagmaPersistency" it will see that there is already a
kernel in the database and will ask if you wish to adopt it for that kernel.
Doesn't work... another kernel named 'Pier' appeared.
I explored MagmaSession's and see that in different sessions roots are
different. I found in one session root a needed kernel but current
session does not see it.
What is the right strategy of managing sessions?
I do some site changes on Magma-powered image then
quit image without
saving. On next entering that image I have no those changes. Is it a
right behavior?
Changes persists only if I save the image. I thought that changes are
not dependent on saving image as your letter seems to confirm.
Daniel
Does anybody read me?