-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In article <NBBBLMKDDAEIBGKHFKKCAENMCLAA.rbickers@logicetc.com>, Ron Bickers <rbickers@logicetc.com> writes
I fought for a full day to get my ZSQLMethods working in 2.1.6, but apparently the argument aquisition or something like that is still so broken that I had to jump back to 2.1.4. I applied the various unofficial "fixes" from the list archives (not all at the same time, of course) and none of them did the trick. I know others beat themselves up over this too.
The problem I'm talking about is the one where the arguments to the sql method seem to be ignored. That is, if I have an argument 'order', and I have a DTML method (or any other "item") named 'order' in the same folder, <dtml-var order> in the sql method refers to the DTML method, not the argument. This breaks dozens of sql methods I have.
With all of these security issues popping up, I don't like not being able to upgrade. Does anyone have a real fix for the ZSQLMethod problems in 2.1.6 that could be officially applied to the 2.1 series, or should I start using the 2.2 betas?
May I second this! - -- Regards, Graham Chiu gchiu<at>compkarori.co.nz http://www.compkarori.co.nz/index.php Powered by Interbase and Zope 2.1.4 and not willing to run beta on production -----BEGIN PGP SIGNATURE----- Version: PGPsdk version 1.7.1 iQA/AwUBOUjFD7TRdIWzaLpMEQK6+QCgijhq2oTAgjc72mYhLlC9m+cLJt4AoKkc qZyj4nVLszB1QoBUQuZibW9U =BDlD -----END PGP SIGNATURE-----