Re: [PHP] Question:maybe urldecode

2004-12-11 Thread Stuart Felenstein
--- Richard Lynch <[EMAIL PROTECTED]> wrote: > > I made the correction , using $_GET now. Values > are > > printing out, aside from the select lists (arrays) > > which print out as "array". > > Yes. > > An array will print as "Array" > > You'll need to dig into the Array for what you need, >

Re: [PHP] Question:maybe urldecode

2004-12-10 Thread Richard Lynch
Stuart Felenstein wrote: > > --- Jason Wong <[EMAIL PROTECTED]> wrote: > >> > Nothing is printing out on $_POST['var'] or $var >> > s makes sense. >> >> Now why are you looking in $_POST for your form >> values? They're in $_GET. You >> said earlier that you understood POST and GET? > > I made the

Re: [PHP] Question:maybe urldecode

2004-12-10 Thread Stuart Felenstein
--- Jason Wong <[EMAIL PROTECTED]> wrote: > > Nothing is printing out on $_POST['var'] or $var > > s makes sense. > > Now why are you looking in $_POST for your form > values? They're in $_GET. You > said earlier that you understood POST and GET? I made the correction , using $_GET now. Value

Re: [PHP] Question:maybe urldecode

2004-12-10 Thread Jason Wong
On Saturday 11 December 2004 00:19, Stuart Felenstein wrote: > > > $queryString = ($_SERVER['QUERY_STRING']); > > > > What is in $queryString after this? var_dump() it > > and show us the result. > > This is the var_dump of the query string after I've > made some selections in the page. > string(

Re: [PHP] Question:maybe urldecode

2004-12-10 Thread KJ
Just want to double check that you're using the correct array in $_POST! Are you using ? If not then you should be using $_GET, not $_POST. $_SERVER['REQUEST_METHOD'] will have the method that you are using, remember to use the corresponding pre-defined variables. KJ Stuart Felenstein wrote: --

RE: [PHP] Question:maybe urldecode

2004-12-10 Thread Stuart Felenstein
--- "Ford, Mike" <[EMAIL PROTECTED]> wrote: > AARRGGHHH! Vague, generalized, woolly!! > > SHOW US the relevant bits of code. SHOW US what you > get printed out, > especially anything that isn't what you expect, and > tell us exactly what you > did expect. > SPECIFICS, man, SPECIFICS!! > > S

RE: [PHP] Question:maybe urldecode

2004-12-10 Thread Ford, Mike
To view the terms under which this email is distributed, please go to http://disclaimer.leedsmet.ac.uk/email.htm On 10 December 2004 13:27, Stuart Felenstein wrote: > --- Jason Wong <[EMAIL PROTECTED]> wrote: > > > Now in an earlier response I asked you to track your variables and > > see at

Re: [PHP] Question:maybe urldecode

2004-12-10 Thread Stuart Felenstein
--- Jason Wong <[EMAIL PROTECTED]> wrote: > Now in an earlier response I asked you to track your > variables and see at > which point they cease to contain what you expect > them to contain. Did you do > that? If you're not doing *your* part to help solve > *your* problem then what > are you ex

Re: [PHP] Question:maybe urldecode

2004-12-10 Thread Jason Wong
On Friday 10 December 2004 18:59, Stuart Felenstein wrote: > I don't believe that the description of my issue was > vague. I provided not only what was expected but an > example. It's still reasonable to believe that there > could only be a limited number of factors involved as > to what is missi

RE: [PHP] Question:maybe urldecode

2004-12-10 Thread Stuart Felenstein
--- "Ford, Mike" <[EMAIL PROTECTED]> wrote: > Please, stop giving us vague, generalized > descriptions of your application, > and how it is or isn't working "right", and vague, > generalized descriptions > of the data it's supposed to be working with. I don't believe that the description of my

RE: [PHP] Question:maybe urldecode

2004-12-10 Thread Ford, Mike
To view the terms under which this email is distributed, please go to http://disclaimer.leedsmet.ac.uk/email.htm On 09 December 2004 20:10, Stuart Felenstein wrote: > > Sorry, I'm not following you. Where are my GET > > parameters ? The way I've built my present script > > is > > the reults

RE: [PHP] Question:maybe urldecode

2004-12-09 Thread Stuart Felenstein
> --- Richard Lynch <[EMAIL PROTECTED]> wrote: > > > Then your new script is broken, as clearly the GET > > paramters *ARE* there. > > Sorry, I'm not following you. Where are my GET > parameters ? The way I've built my present script > is > the reults page is grabbing the parameters. Do I > n

RE: [PHP] Question:maybe urldecode

2004-12-09 Thread Stuart Felenstein
--- Richard Lynch <[EMAIL PROTECTED]> wrote: > Then your new script is broken, as clearly the GET > paramters *ARE* there. Sorry, I'm not following you. Where are my GET parameters ? The way I've built my present script is the reults page is grabbing the parameters. Do I need to set up GET pa

Re: [PHP] Question:maybe urldecode

2004-12-09 Thread Jason Wong
On Friday 10 December 2004 00:24, Stuart Felenstein wrote: > Jason, I don't think you read or understood my > question. > As I said, it doesn't seem to be a debugging > scenario.I was asking if anyone would know a > reason why on one page , one could apply the query > string to url and t

Re: [PHP] Question:maybe urldecode

2004-12-09 Thread Stuart Felenstein
--- Jason Wong <[EMAIL PROTECTED]> wrote: > > Basically I'm throwing this out though since I'm > > wondering if there is something that should be in > the > > search script , that when I apply a query string > to it > > would fill in the field (like magic hands) > > Yeah I wish I had some magic

Re: [PHP] Question:maybe urldecode

2004-12-09 Thread Jason Wong
On Thursday 09 December 2004 23:16, Stuart Felenstein wrote: > I'm not sure if this particular is a matter of > debugging. Your program doesn't work the way you intended it? So if you don't debug it, how is it going to get from a "not working as intended" state, to a working state? > There is

RE: [PHP] Question:maybe urldecode

2004-12-09 Thread Stuart Felenstein
--- "Ford, Mike" <[EMAIL PROTECTED]> wrote: > > Lastly, I wasn't concerned about the hex code, but > I just made some reconnections of scripts. Users > can save their search parameters. I am saving the > query string. Now I had this set up before and the > way it "was" working , is when the u