VA 8.0.1. Scriptaculous updater does'nt trigger callback

[klaus]

Hello,

the following method, which was implemented in VA SMalltalk 8.0 (Seaside 2.9) returns a block for rendering a password input and does'nt work anymore in VA Smalltalk 8.0.1 Build B128 and B130. Input fields, radio buttons are concerned too. The callback method #setPassword isn't called any more.

What is wrong with my example below?

Kind regards

Klaus

Code: Select all

renderBlockKennwortFieldOn: html
   "^<Block>, html <WARenderCanvas>"

   ^ [ | anUpdater |
   
         anUpdater :=
            html scriptaculous updater
               triggerForm: self fid;                                       
               yourself.
         
         html div
            class: (self divCssClassField);
            with: [         
               html passwordInput
                  value: nil;
                  disabled: false;
                  callback: [ :value | self setPassword: value ];
                  onChange: anUpdater;
                  size: 12;
                  maxLength: 8 ] ]

[jtuchel]

Klaus,

I guess that's the Seaside Issue 460, which has just recently been fixed. Maybe it's not in the Seaside Alpha which is part of VAST 8.0.1 (B130, however, says it contains 3.0a5, which is younger than the fix, so it should be there...) :

http://code.google.com/p/seaside/issues/detail?id=460

cu

Joachim

[wembley]

The fix for Seaside issue 460 is in both B128 and B130.

[klaus]

Hello,

thanks for your replies, but the code works in VA Smalltalk 8.0 with Seaside 2.9, but not in VA Smalltalk 8.0.1 Build B128 and B130 with Seaside 3.
There must be another reason.

The only callback which works is #onSubmit:

Firebug stops with this error when I'm leaving the input field:

Code: Select all

function onchange(event) {
Ajax is not defined2 new (Ajax.Updater)(this, "/CASCADE-PC/CPC%20Root%20View", {evalScripts: true, parameters: ["_s=2TIIuLLeUdRsxRtj", "_k=-L9IJ6xAV6a0Hm2B", "29", $("id28").serialize()].join("&")});
3 }

Kind regards

Klaus

[klaus]

Hello,

the problem is solved: there is a new library called #PTDeploymentLibrary, which has several scripts, which were implemented in #SUDeploymentLibrary. I added the #PTDeploymentLibrary to my application and everthing run fine.

Kind regards

Klaus