Jeez, please *READ* the replies posted to you!! Obide by the etiquette
which the list expects and *STOP* repeatedly mailing "anyone there",
"please respond" etc it's just damn annoying and rude (the CAPITALS I
am using here are case in point and if deliberate"
If you had actually *READ* the previous reply you will notice that you
were provided an *ANSWER* with code.
*RESPECT* the work people who post to this list and realise this is
not a JS/Scriptaculous Support helpline but a community of it's users.
Pankaj wrote:
> Please see this function for the last ti
me. If its correct then I will
> give you a online reproducible case.
>
> I have created a new variable $num1 -->
>
> function getHTML(num) {
> var saf = 0 ;
> var num1;
> if(!num) {
> num1 = $F('refid');
> } else {
> num1 = num;
> }
> var url = '/cgi-bin/tps/search.cgi';
> var pars = {num: num1,showallfiles: saf,act:
> 'showattachedfilesection'};
> new Ajax.Updater( {success: 'placeholder'}, url, {method:
> 'get',parameters: pars,evalScripts: true ,onFailure: reportError });
> }
>
>
> On Feb 17, 4:57 pm, Christophe Porteneuve <[EMAIL PROTECTED]> wrote:
> > Hey Pankaj,
> >
> > First, please stop pinging people for reply. It's annoying, and it
> > certainly won't make people who didn't reply yet want to reply more.
> >
> > Second, please READ what we say. The trouble in your function is the
> > re-declaration of num as a local variable, which obscures your
> > parameter. Here's how it should read:
> >
> > function getHTML(num) {
> > num = num [[ $F('refid');
> > var saf = 0;
> > var url = '/cgi-bin/tps/search.cgi';
> > var pars = { num: num, showallfiles: saf,
> > act: 'showattachedfilesection' };
> > new Ajax.Updater({ success: 'placeholder' }, url, {
> > method: 'get', parameters: pars, evalScripts: true,
> > onFailure: reportError });
> >
> > }
> >
> > Finally, don't say "it's not working." There is no report less useful
> > than that. We have no idea what your function should do; we have no
> > idea where and how your function is CALLED, and what's passed as the num
> > argument; we have no idea what the server-side script does, whether it
> > does return something, and then what. We have no idea what your
> > placeholder element is, and what your reportError function does.
> >
> > You're asking us to help diagnose a problem while exposing 5% of it.
> >
> > Can't you PLEASE put up an online reproducible case, and clearly state
> > what's supposed to happen?
> >
> > Sincerely,
> >
> > --
> > Christophe Porteneuve a.k.a. TDD
> > "[They] did not know it was impossible, so they did it." --Mark Twain
> > Email: [EMAIL PROTECTED]
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Spinoffs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---
