hi, i don't want to spam the mailing lists, so...
please post all the questions to the mailing-list, this is much
easier for: (1) other people can profit as well (2) the questions are
indexed by Google and people not being in the mailing list can read
about it as well (3) other people reply and discuss with you, so I
don't have to do all by myself ;-)
i want to use Seaside to build my private site (much more for
learning than anything serious) a i'm considering using Pier as the
basis, there are some problems though (i don't exactly know which
of them are Pier-related) -> i've managed to run a Pier app on
gil.seasidehosting.st and set up some (unix) security but there are
the running packages are: Seaside2.6b1.pmm-66 merged with .gk-30 (i
really need WAKomEncoded39), Pier-Model.kph-77, Pier-Seaside.lr-75,
Pier-Security.kph-40 - i loaded them via SqueakMap, so there
weren't the Pier-All and Magritte-All packages, and updated some of
them from the mc.lukas-renggli.ch/ repositories (which wasn't such
of a great idea; i already know).
I still don't know what the problems are with the latest versions,
since I cannot reproduce on my machine, sorry.
1. i don't see a way to limit regular users to adding a page or
external file, without allowing them to add a component or internal
That's currently not possible. The security-model has to be enhanced
to allow that kind of fine grained security.
2. the 'logout' function doesn't bring me to the first
page (and i
can't set the 'first' page for a user after logging in) - i think i
can manage this by editing the components in-image, but it would be
nice to have a direct setting possibility.
Logout does simply reset the currently logged in user to anonymous,
it is not supposed to jump to a specific page. Though you can
implement such a logout action easily by subclassing the PULogou
3. the image keeps growing slowly, even if i do a 'cleanup'
each save (MCFileBasedRepository flushAllCaches. WARegistry
clearAllHandlers. WAHalo initialize. Smalltalk garbageCollect).
If you add contents it naturally grows. Are you using a persistency
4. if i break something in the image (or even load a slightly
different version of Pier/Magritte), i don't see a way to migrate
the Pier kernel to another version or constructing a new kernel
with the contents of the old one (pages, components, users&groups,
Really? That shouldn't happen. Can you elaborate? I am using the same
image for over a year now and nothing broke. The model of Pier and
Magritte didn't changed much in the past.
5. the 'add' command is kind-of broken: if the operation (add
external file) breaks, there is a entry poit to the new structure
without it actually present - so any acces attempt results in a
walkback and there is no possibility to remove the faulty structure
I don't understand. What is the operation 'add external file'? I
don't have such a thing in my image.
6. the 'remove' command seems not to work (i didn't
It works for me, so the question is: do the tests run in your image?
i will be grateful for any advices (even if it'll be along the
lines "throw away the image/pier-kernel and start in a more sane
Feel free to ask as many questions as you like. If you find bugs that
you can fix yourself, just commit to the repository.