[Seaside] ShoreComponents cant cope with latest Scriptaculous
renggli at gmail.com
Sat Nov 10 08:17:47 UTC 2007
> this.setOptions is not a function
I don't know who is calling setOptions? Presumabely this is done from
somewhere in ShoreComponents.
ANN: With the announcement of the final versions of Prototype 1.6.0
and script.aculo.us 1.8.0 I integrated these libraries into the latest
Scriptaculous pacakge. Many internal details of these libraries have
change (see the change-logs in Monticello and on their respective web
sites). Most of these changes are automatically handled on the
setOptions) directly you might have to adapt your code.
It could also be that your browser did not refresh all the libraries
and caches some incompatible versions.
More information about the seaside