What the alternative then... change the persistency to
PRNullPersistency, makes changes and updates and then redo image
persistency.
Yes, it is dangerous that this suddenly triggers a snapshot when you
are in the middle of doing something. Depending on when this happens
(what is quite likely after all) your changes are screwed ...
I've seen there are evolutions to ImagePersistency
in the last
commits...
As far as I know these changes are made by Doru. He made it easier to
make Pier be deployed on seasidehosting.st where there are certain
disc limits. I didn't had a look at his changes though.
ps: btw, I found pier really great as a user :) I
serve it at home
ans this is working nicely. I have suggestions as an admin page per
default but I'llcome back later for that ... :)
Yes, we are working on that. Also on a decent default layout. Etc.
Cheers,
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch