> I think this is actually Zope's bug - if I'm not mistaken, the
> TinyTables product uses the Results class provided in
> lib/python/Shared/DC/ZRDB/Results.py, which would make it
> subject to breaking in the same way that SQLMethod results
> broke in the 2.2 alpha. I've included a copy of the no
> Even when I have logged in as the admin user I get an error
> message I suppose from the dtml fragment
> >
> >
> >
> >
>
> If I force validate to be None inside DT_In.py (renderwob)
> then I can at
> least get a dtml-in TinyTable to work. It seems as though the
> tinytable
> product
In article , Robin Becker
<[EMAIL PROTECTED]> writes
>I have started with clean 2.2.0a1 and have then created an admin user. As this
>user I have
>imported my old 2.0 exported database.
>
>I have given anonymous rights to query Tinytables, but am still forced to
>attem
I have started with clean 2.2.0a1 and have then created an admin user. As this user I
have
imported my old 2.0 exported database.
I have given anonymous rights to query Tinytables, but am still forced to attempt to
login. Even
when I have logged in as the admin user I get an error message I sup
Kyler B. Laird ([EMAIL PROTECTED]) posted a quick n' dirty fix on the
Zope mailing list. I'll include it here for convenience:
-- snip --
After beating on this over the last day or so trying to
understand what was happening at the Web interface level
(thinking that I must have just screwed up a
In article <000401bfc224$475de410$8119adcf@Pooky>, T.J. Mannos
<[EMAIL PROTECTED]> writes
>Hi, all,
>
>I tried compiling 2.2.0a1 straight out of the box on Solaris 7. Everything
>worked great until I tried querying a tiny table or MySQL database. The
>following code causes Zope to prompt me for
Hi, all,
I tried compiling 2.2.0a1 straight out of the box on Solaris 7. Everything
worked great until I tried querying a tiny table or MySQL database. The
following code causes Zope to prompt me for a login, and no matter what user
name I use (even the superuser), it comes back "unauthorized."