> In my defense, since Josh asked, I have actually tried it - but only in a > browser (by copying and pasting the encoded URL) where such URL wouldn't > work for me in Chrome (target PHP page would see a variable named "amp;2" > instead of "2") but when I use an encoded URL in a Tapestry template, it > actually works as expected.
I'm guessing that what was happening was that your PHP page was doing the encoding for you and you ended up with it double encoded ("&"). Tapestry isn't doing anything special with it. > Anyway, all the fuss for such a stupid mistake... one learns every day! > Thank you for your patience and help. I know some online forums where people > would send me to hell for this, instead of patiently answering and > explaining. :-) Yeah, we've all been there! Who wants to be a part of a community that berates people for trying to learn? Josh --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org