[prev in list] [next in list] [prev in thread] [next in thread] 

List:       bricolage-devel
Subject:    Re: Fwd: Re: Bric2 callbacks: trail_cb and update_cb
From:       mercie_s () denison ! edu
Date:       2009-02-12 14:42:17
Message-ID: 20090212094217.mdqmpp5ab9ws0cc4 () webmail ! denison ! edu
[Download RAW message or body]

> You might look in Params::CallbackRequest and/or Params::Callback
> (by David) for more detailed docs.

Looked at the callbacks and after some testing and comparisons with  
trunk, we found that the problem might deal more directly with the  
changes between the old prototype and the new one.  In  
/comp/media/js/lib.js, when we are trying to get the parameters to  
pass to the Ajax Updater, we use a prototype function called  
'serialize.'

When looking at the changes in this function between Prototype 1.5.0  
rc0 and the new version (1.6.0.3), we found that the way elements in  
the form are collected is vastly different.  Whereas in the older  
version, serialize grabs only certain elements, the newer version  
grabs all elements in the form.

If we print out the parameters being passed to the Updater, we can  
easily see this, as we get things like the 'Save and Stay' buttons and  
the 'Cancel' buttons whereas on trunk, we do not.

Another interesting problem we have when running the new prototype is  
we get what appears to be a mutated version of what should be the  
parameter
"container_prof|element_<container_id?>=dat<element_id?>."  The new  
prototype grabs this and passes it, but it also passes a malformed  
version of this parameter immediately before, which looks something  
like "container_prof|<element_id?>=(NULL)."

If extra parameters are being passed to the Updater, would this cause  
the error?  Does the malformed parameter have any effect on the  
Updater?  Any ideas as to how we should approach this problem?

Thanks,
Sarah Mercier




[prev in list] [next in list] [prev in thread] [next in thread]