I'm running into a small hang-up with PerForm v1.8.  Here's the error I
get when I try to create a form:

[AxKit] [Error] Compilation failed: Too many arguments for
AxKit::XSP::WebUtils::redirect at (eval 277) line 74, near "1)"
BEGIN not safe after errors--compilation aborted at (eval 277) line 83.

And here's the line of code it's complaining about:

73 if ($redirect) {
74     AxKit::XSP::WebUtils::redirect($redirect,undef,undef,1);
75 }

The WebUtils::redirect subroutine only asks for three parameters, but
PerForm.pm is calling it with four.  Is that just an extra 'undef' in
there?

Thanks,
Scott


-----Original Message-----
From: Matt Sergeant [mailto:[EMAIL PROTECTED] 
Sent: Monday, June 16, 2003 3:27 AM
To: AxKit Users Mailing List
Subject: Re: ANNOUNCE: AxKit-XSP-PerForm 1.7

That's actually 1.8, not 1.7. Sorry.

On Mon, 16 Jun 2003, Matt Sergeant wrote:

> I have just uploaded PerForm 1.7 to CPAN. This is a major update, with
> many bug fixes and improvements. Here is the list of major changes in
this
> release:
>
> 1.7
>     - Patch from nachoman to finally properly support single and
>       multiple select
>     - Change to use can() so we can use XSP inheritance
>     - Added onload and onvalidate attributes to each tag (allow to
specify
>       external code to validate/load, or use single function for
multiple
>       tags)
>     - Patch from Mark Hershberger fixing:
>       - If the error message contains the word "at", everything
>         from that "at" to the end of the error is deleted.
>       - If a load_* function is defined, then the submit_*
>         functions get the value that load_* provides rather than
>         what was submitted.
>     - Better support for multiple forms per page
>
> The biggest change is that all form elements now support both onload
and
> onvalidate attributes so that you can assign specific functions to
form
> elements. This is especially relevant if you have repeating fields
that
> you need to validate using the same function, or if you wish to have
your
> validation outside of your XSP page (which you can now do either with
XSP
> inheritance, or via fully qualified function names).
>
> It may take 24 hours to propogate through CPAN.
>
> Do let me know if your application suddenly stops working with this
> release. I've tried as much as possible to be backward compatible, but
you
> never know what I may have missed.
>
>

-- 
<!-- Matt -->
<:->get a SMart net</:->
Spam trap - do not mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to