| Ken Restivo 2005-01-31, 3:57 am |
| -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I think QF may be posessed of an evil spirit.
I validate form A, which has a hidden var disp_state set to "A". After validating and processing, $_REQUEST['disp_state'] === 'A'.
Then I instantiate a totally new form B. I then $formB->addElement('hidden', 'disp_state', 'B'). And when QF creates this element, it *ignores* my value passed in to addElement, and instead insists on placing into it the value "A". If I print_r the eleme
nt immediately after addElement'ing it, "A" is in there, not "B" which I specified. I have no code of my own in there between addElement and print_r. Who or what is making the decision to put a different variable in there? Only the shadow knows.
But then if I explicitly setValue("B") afterwards, it stays in there, and the behaviour I expected is exhibited.
I'm using $trackSubmit, but that doesn't look like it is the problem.
Since I found the setValue workaround and I wasn't able to isolate this in a testscript suitable for a proper bug report, I'm just going to raise an eyebrow and move on from here. It's apparently some interaction with the rest of my application, but I can
't imagine what. I'm on a tight deadline so I haven't time to do a lot of detective work on this, but I'm still curious what code of mine could be causing this strange behaviour?
- -ken
- --
- ---------------
The world's most affordable web hosting.
http://www.nearlyfreespeech.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
iD8DBQFB/dGme8HF+6xeOIcRAncmAJ9EHRl5TLxco6hp/WfMQyrODTNtAgCdE5kO
ALaOTrk1wjinCXH3U7U239E=
=VHhP
-----END PGP SIGNATURE-----
|