[Seaside] upgrading methods

Brad Fuller brad at sonaural.com
Thu Feb 22 19:58:14 UTC 2007

Brad Fuller wrote:
> Lukas Renggli wrote:
>>> What is the best way to upgrade Seaside and pier, and the packages for
>>> Seaside? Is it ok to go to the latest (or near) MC package and "Merge"?
>>> Any methods on how you update would be MUCH appreciated! This is a bit
>>> confusing - it's not brain surgery, just a bit confusing to me.
>> Update in this order:
>> - Seaside
>> - Scriptaculous
>> - Magritte
>> - Pier
>> For Seaside 2.7 there are some things you need to do to recreate your
>> dispatcher configuration (discussed here and written in the commit
>> comments of Seaside).
>> The latest versions of these packages should work. In case you run
>> into some problems just ask again, I've done this a 100 times already
>> ;-)
> Glad you've done it 100times! cause I got a problem.
> I merged the latest Seaside 2.7. And I did the following from recent 
> messages:
>     WAComponent allSubclassesDo: [ :each | each initialize ].
>     WADispatcher resetAll.
> Each of these replied with a seaside config username/password, which I 
> supplied.
> Each of these replied if I wanted to create a new Pier, which I said 
> 'no' (since I already have one.
> Now, there is not access at /seaside/config, nor my pier app.
> from the browser:
> Internal Server Error
> MessageNotUnderstood: UndefinedObject>>isEmpty
> Comanche/6.2 (unix) Server at www.<my_domain> Port 9999

UPDATE: Twice I stopped WAKom and restarted. The 3rd time, I stopped it, 
  waited, and restarted and Seaside came up. Don't know if it was a 
browser cache problem or what.

But, I don't have my Pier app. And, I want my Pier app!

brad fuller
  +1 (408) 799-6124

More information about the Seaside mailing list