Posted by shorterboy smith
on 10.02.2007 15:52
I have this prototype (1.5) fragment that has historically worked, when 
I include rico.js the query is no longer sent to the server. The rico 
specific ajax stuff just makes no sense to me so I want to avoid using 
it, but I like the pretty decoration stuff.

 new Ajax.Updater("test","/ajax/ullist",{
                  encoding:'',
                  parameters:{text: $F("ftest")}});

Is the prototype ajax object shagged by rico.js or am I missing 
something??
Posted by David de Kock
on 12.02.2007 15:49
I've got problems too after upgrading to prototype.js 1.5.0
None of my Ajax.requests are working anymore, they all silently die and 
nothing is send to the server.

Problems are gone if I comment out the rico.js (1.1.2) include.

Seems there is a bit of an incompatibility isse here.
I will look into it further but hopefully someone has come up with a fix 
:)
Posted by David de Kock
on 12.02.2007 16:42
and yes a fix was already available add to this forum by Lucas Persona.

http://forum.openrico.org/topic/2228#new

not sure if I like to apply a fix to prototype.js instead of rico.js but 
at least there is a fix.

btw. this fix is also applicable for json.js 
(http://www.json.org/json.js)

for more background info on prototype.js development on this is issue:
http://dev.rubyonrails.org/ticket/7444
http://dev.rubyonrails.org/ticket/7475

have fun,
David
Posted by shorterboy smith
on 13.02.2007 08:06
Been there done that as they say, tried the fix, no success. Maybe I did 
something wrong, but it's not a difficult mod.

Is this supposed to be a definite fix or a maybe?
Posted by Issachar Brooks
on 08.05.2007 16:52
I did this fix, as the issue still isn't solved in Prototype, and it 
worked, but the Ajax.Updater still doesn't evaluate scripts in FF. IE6 
and Opera work fine.
Any Ideas?