typo i assumed you would see that
- Original Message -
From:
To: "Prototype & script.aculo.us"
Sent: Tuesday, June 02, 2009 9:30 PM
Subject: [Proto-Scripty] Re: Problem with Ajax.Updater...
>
> ok, I tried your suggestion but this doesn't work at all
&g
I was not suggesting that at all
- Original Message -
From:
To: "Prototype & script.aculo.us"
Sent: Wednesday, June 03, 2009 1:06 AM
Subject: [Proto-Scripty] Re: Problem with Ajax.Updater...
>
> @T.J.
> I didn't say it's not valid, but Alex was sugg
make that 2 typos !
- Original Message -
From: Rick Waldron
To: prototype-scriptaculous@googlegroups.com
Sent: Tuesday, June 02, 2009 10:01 PM
Subject: [Proto-Scripty] Re: Problem with Ajax.Updater...
I noticed you're missing a comma...
var myAjax = new Ajax.Up
Searching around, I found a very similar issue here:
http://stackoverflow.com/questions/676448/prototype-js-1-6-0-3-ajax-updater-not-working-in-ie7-or-ie8-help-please
Seems IE 7&8 have problem with prototype and utf8 encoding?
I can't work without UTF, this is ridiculous! IE is ridiculous
anyway
@T.J.
I didn't say it's not valid, but Alex was suggesting to omit the comma
before onComplete, which is not valid.
I tried step #3, but in a very smaller scale and it works. I can't add
all the code needed to replicate, this would take pages!
@Rick
That's what I was trying to say to Alex too ;)
I noticed you're missing a comma...
var myAjax = new Ajax.Updater(target, url, {method: 'post',
parameters: { params: pars } onComplete:function(){
Between "{ params: pars } onComplete" (should be right before onComplete)
That may be unrelated, but an observation worth noting.
On Tue, Ju
Hi,
Guys, you're talking past each other.
@Alex:
This is perfectly valid:
var x = "one=1&two=2&three=3";
new Ajax.Updater(target, url, {parameters: x});
@OP:
This is perfectly valid (and preferred):
new Ajax.Updater(target, url, {
parameters: {
'one':1,
'two':2,
; }
> - Original Message -
> From:
> To: "Prototype & script.aculo.us"
> Sent: Tuesday, June 02, 2009 8:29 PM
> Subject: [Proto-Scripty] Re: Problem with Ajax.Updater...
>
> > Hello Alex,
> > no I didnt have a trailing comma after the closi
ok, I tried your suggestion but this doesn't work at all
have you ever tried the syntax you are suggesting? Because I think
it's wrong...
Caught also in FF's error console as:
Error: missing } after property list
Source File:
Line: 52, Column: 94
Source Code:
var myAjax =
ok, I tried your suggestion but this doesn't work at all
have you ever tried the syntax you are suggesting? Because I think
it's wrong...
Caught also in FF's error console as:
Error: missing } after property list
Source File:
Line: 52, Column: 94
Source Code:
var myAjax =
ok, I tried your suggestion but this doesn't work at all
have you ever tried the syntax you are suggesting? Because I think
it's wrong...
Caught also in FF's error console as:
Error: missing } after property list
Source File:
http://www.sitedarling.com/partyspots/components/com_cbactivity/add-
02, 2009 8:29 PM
Subject: [Proto-Scripty] Re: Problem with Ajax.Updater...
>
> Hello Alex,
> no I didnt have a trailing comma after the closing bracket, because
> there is no closing bracket there!
>
> syntax:
> Ajax.Updater(container, url[, options])
>
> quoting my line of
Hello Alex,
no I didnt have a trailing comma after the closing bracket, because
there is no closing bracket there!
syntax:
Ajax.Updater(container, url[, options])
quoting my line of code:
var myAjax = new Ajax.Updater
(target,
url,
{ /* opening bracket for options...
me
nal Message -
From:
To: "Prototype & script.aculo.us"
Sent: Tuesday, June 02, 2009 3:13 PM
Subject: [Proto-Scripty] Re: Problem with Ajax.Updater...
>
> @Alex
> I encodeURIComponent them now, thanks for suggestion
>
> notice that when you are sending the key values with the
@Alex
I encodeURIComponent them now, thanks for suggestion
notice that when you are sending the key values with the url, they get
caught as $_GET, no matter if you use {method: 'post'} (!)
@T.J.
all your assumptions are right ;)
anyway, if you add some alerts to see what's going on like this:
.
Hi,
As Alex says, you need to URIEncode the values you're getting from the
inputs, but that would probably result in a different symptom. Other
than that, the code quoted works fine this end (provided I add the
missing '}' at the end to close the function, but I'm assuming that's
a copy and past
try URIencoding it ..
Also if its post why are you sending it as key/value pairs . try the
following to see if its whats messing it up
var myAjax = new Ajax.Updater(target, url+'?'+pars, {method: 'post',
parameters: foo: 'BAR'}); // notice i am sending your key value pairs in the
URL stri
Thanks for your explanation Walter. My problem was that I had
expected the Updater to know whether to use .value or .innerHTML
automagically.
cheers,
Matthew
On Sep 30, 8:56 pm, Walter Lee Davis <[EMAIL PROTECTED]> wrote:
> No, it's not a bug. A Textarea is a form element, not a DIV or
> a
No, it's not a bug. A Textarea is a form element, not a DIV or
another text container. Form elements have a value, and therefore
that's what you change. DIVs and Ps and other valid text containers
do not have a value attribute, only children. innerHTML is a way to
change the children witho
19 matches
Mail list logo
