1. Save the image under a new name, just to be sure. 2. Disable an existing persistency strategy: aKernel persistency: PRNullPersistency new 3. Load the latest code of Magritte-Model, Magritte-Seaside and other Magritte packages you might have present in your image using Monticello. 4. Load the latest code of Pier-Model, Pier-Seaside and other Pier packages you might have present in your image using Monticello. 5. Re-enable the persistency either using the above command or through the web interface. I did the above procedure with several older images (among them lukas-renggli.ch and seaside.st) and it worked flawlessly. Some packages do an object migration when loading and detecting an incompatible model. So before you save your image again, test if everything works. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

On Thu, Feb 5, 2009 at 12:29 PM, Lukas Renggli <renggli(a)gmail.com> wrote: Lucas, Damien, Thanks for your answers. Your instructions updates the existing image to the latest version but what if I want to move the data from one image to another? eg: I'd like to move to the new pharo based one-click image. Is is possible? Is the data jailed inside the image? If so I'm afraid I'll have to stop using Pier. Cheers, -Krishna -- Why make things difficult, when it is possible to make them cryptic and totally illogical, with just a little bit more effort? - Aksel Peter Jorgensen

Hi, To which stylesheet are you referring: the from the release or the one from piercms.com? "clearly better" is clearly not helpful because it's clearly not so clear :). Seriously, is there something that confuses you in the layout? Is there something you cannot find? Cheers, Doru -- www.tudorgirba.com "Every thing should have the right to be different."

Hi Krishna, Much clearer now :) The idea behind the stylesheet of the one-click installer is to inflict as less constraints as possible on the graphic design, so that it is easier for people to adapt it to their needs. In fact, if you add the old CSS over the new structure (you can do this via the Edit Design command) it mostly match because only few things have changed in the structure. Thanks for the feedback. Cheers, Doru p.s. Is your Pier webpage online somewhere? On Feb 5, 2009, at 4:53 PM, Krishna wrote: -- www.tudorgirba.com "Being happy is a matter of choice."

I like this new pier page, but I fell like there is something missing as far as the appearancee. the site feels very "empty" possibly caused by the lack of color? -- david zmick On Feb 5, 2009, at 10:56 PM, Krishna wrote:

I will write something about the motivation behind the value links. I can't imagine how that could happen. Can you give more details? Is it a security issue? Is it just not displayed in the menu? Do you get an error? How about logging in as administrator? How about manually navigating to the settings by typing the URL and appending "?command=PRSettingsCommand"? The new parser was introduced more than a year ago on August 12, 2007. The new parser is fully backward compatible, it passes the extact same tests as the old parser did, and it made it possible to have pluggable extensions to the wiki syntax. As long as you did not patch the old SmaCC parser there should be no compatibility issues (at least none were reported to me). Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch