Re: Pier Stylesheets - Help!

I am not sure what is going on at seaside hosting, but I had a look at another site on there and guess what, it has no style! So it looks like the default pier configuration may be unable to get to the style sheet served by lukas' machine at the moment. This might explain your problem. No it shouldn't, but I recall my initial time with Pier; it took me at least two weeks to get the hang of the packages so that they installed correctly. I had never used MC before, so it took me a while to get used to its quirks. At the moment with pier-magma integration we are in a period of limbo, where things are not actually expected to work out of the box. You see I made some changes to both pier and magma in making the seaside-pier-magma image work. I was waiting for Lukas and Chris to update the mainstream of pier and magma to incorporate my changes. They have both done this now, so it remains for me to review their changes (not all were accepted) and update the pier-magma package. Now that the necessary infrastructure changes (apart from one; I suspect PRKernel realizeKernel may still have to be added) are in both pier and magma, the process should be much smoother. In theory, pier-magma will not have to touch pier or magma to work. The plan is to pull my contribution to Pier-Seaside, including the item that uses the elusive WADispatcherEditorPlugin into a separate package for "persistency management". This is the code and UI that enables switching between persistency schemes on the fly. With this in mind, I will point out that Magma supports pier in an entirely transparent manner. Pier really does nothing special to support Magma. Therefore I can encourage you to get going with Pier, safe in the knowledge that enabling magma persistency requires nothing more than a drop down menu selection.