Hi Philippe,

Open the monticello browser and there open the Seaside repository. Select the Scriptaculous package on the left pane and then select the latest version on the right pane. Then hit load.

When I try this I get:

This package depends on the following classes: BlockClosure You must resolve these dependencies before you will be able to load these definitions: BlockClosure>>asFunction

Any suggestions how to proceed?

Thanks.

Thanks Philippe,

If you don't have a BlockClosure class you don't need that method anyway. Alternatively you can also create an empty BlockClosure class somewhere.

This did get past the load stage, but lead to a later error in the application itself that seems to be related to BlockContext (see *** below) which I am guessing is related to BlockClosure.

Any idea where I can get BlockClosure and its related dependencies?

Thanks.

Internal Error MessageNotUnderstood: UndefinedObject>>updateRoot:

[] in WAApplication>>updateRoot: {[:ea | ea updateRoot: anHtmlRoot]} OrderedCollection>>do: WAApplication>>updateRoot: WASession>>updateRoot: WARender>>buildDocRoot WARender>>buildResponse [] in WARender>>render {[:u | url := u. self buildResponse]} [] in WASession>>respond: {[:cc | url := self actionUrlForContinuation: cc. response := responseBlock...]} ResponseContinuation class(Continuation class)>>currentDo: WASession>>respond: WARender>>render [] in WARender>>go {[self render]} BlockContext>>on:do: WARender>>withRenderNowHandler: [] in WARender>>go {[self withRenderNowHandler: [self render]. self shouldRedirect ifTrue: ...]} BlockContext>>on:do: WARender>>withPageExpiredHandler: WARender>>go [] in WARenderLoop>>run {[(WARender new root: root) go]} BlockContext>>repeat

...

...

If you don't have a BlockClosure class you don't need that method anyway. Alternatively you can also create an empty BlockClosure class somewhere.

This did get past the load stage, but lead to a later error in the application itself that seems to be related to BlockContext (see *** below) which I am guessing is related to BlockClosure.

What makes to think so? To me I looks like "self libraries" in WAApplication returns a collection with a nil element inside.

This problem has nothing to do with BlockClosure and BlockContext. Your list of library classes contains nil as Philippe said.

As Philippe said in an earlier thread, the API slightly changed for version > 100. One of the changes was that I renamed SUScriptaculousLibrary to SULibrary and this very probably causing your problem. To fix it you need to remove nil (the obsolete class) and add SULibrary from library list in the Seaside application config interface.

Hope this helps, Lukas

...

To fix it you need to remove nil (the obsolete class) and add SULibrary from library list in the Seaside application config interface.

I will try that. As soon as I figure out how to recover that toolbar ... which I disabled when playing with "production" mode. I had earlier also changed WAKom class default from '/seaside' to '/mine'. Any suggestions warmly welcome :-)

Inspecting "WARegistry default" and browsing to your application should allow you to change this setting from within your image.

Cheers, Lukas