[Maypole] A few post-2.05 change questions

[Peter Speltz]

--- Jesse Sheidlower <jester@panix.com> wrote:

> 
> Hi. I'm just returning to some programming after time
> spent on $WORK, updated Maypole from 2.04 to 2.06, and
> promptly ran into two problems.
> 
> First, in one of my databases, I have a column called
> "description", which is not an SQL reserved word or a
> reserved word in CDBI or anything.

they pulled/will pull that in 2.07.

> Second, in a different application--one that, unlike most of
> my Maypole apps, is straightforward and doesn't override half
> of Maypole--I am now getting untaint errors where I didn't
> used to before. I don't want to untaint anything here, and I
> don't have required columns, but in this situation when I
> leave a field blank, I am getting "author () does not untaint
> with default pattern" errors. Now, author is a display_column
> but I don't require it for untainting anywhere.

I have this one too. I thought i got it after upgrading CGI::Untaint though.
did  CGI::Untaint get updated as well?


=====
pjs


		
__________________________________ 
Do you Yahoo!? 
The all-new My Yahoo! - Get yours free! 
http://my.yahoo.com