OK, I've bee trailing this bug for quite some time, and haven't found a solution other
than not use 2.2.1 :(
In PortalMembership's acl_users folder's MailPassword Process ...
We have mailPasswordTemplate.
==
From: "&dtml-email_from_name;" <&dtml-email_from_address>
To:
Subject: Mem
When trying out the mailPassword function (which creates a new encrypted password, and
sends the raw password to the
user), I get this error (I swear it worked in 2.2.0):
Traceback (innermost last):
File /local/ZopeSites/TestBed/lib/python/ZPublisher/Publish.py, line 222, in
publish_module
Jim Fulton wrote:
>
> The initial beta release of an Oracle-based storage for ZODB
> is available at:
>
> http://www.zope.org/Products/OracleStorage
>
> The Oracle storage provides full ZODB storage capabilities,
> including undo and versions, by storing serialized objects
> and meta data in
The initial beta release of an Oracle-based storage for ZODB
is available at:
http://www.zope.org/Products/OracleStorage
The Oracle storage provides full ZODB storage capabilities,
including undo and versions, by storing serialized objects
and meta data in Oracle tables.
Jim
--
Jim Fulton
Mostly bugfixes and internal reorganizations, some very minor feature
additions. This thing is finally beginning to stabilize a bit. Wish me
luck on getting some time to document SkinScript... :)
Meanwhile, my department is about to embark on a significant production
product using ZPatterns, a
Hi,
I think I have traced my error with cut and paste, I am getting an error on
_setObject. If the object is not registered with Zope properly this will be
a problem. Basic synopsis:
Im importing an object from a script so Im getting a handle to the folder I
would like the object to be in: this
> I'm absolutely sure that NONE of the things which were broken in the
> original Data.fs had the slightest/faintest connection with any of the
> products I expunged. It was removing the cruft alone which fixed the
> problem.
>
> Doesn't this (and the other episode reported by Andy) raise
> the
On Mon, 28 Aug 2000 20:41:05 -0700, Kapil Thangavelu
<[EMAIL PROTECTED]> wrote:
>i ran some basic tests comparing a btree folder against a folder. i'm
>not sure about my testing methodology but here are the results. the test
>code is at the end of this email.
Im not sure this benchmark is measu
On Thu, 31 Aug 2000, Andre Schubert wrote:
> I'm discovering the EMarket Product and test it to with it in our Firm.
> I'm working with Zope 2.2.0 and i have 2 problems.
EMarket is not yet 2.2-safe, as Steve mentioned. If you come up
with bug fixes, let us know .
That said, I don't have any pro
If you said you had patches for me, now is the time.
I have some fairly significant improvements and fixes ready (missing a deluser
function at the moment, can't even find
delItem in my tree anywhere...)
(I've been working at it for the last 5 hours straight, my brain is a bit too fizzeled
to
Hi andre...
Sorry.. EMarket is currently broken in 2.2.x. I'm trying to
find time to fix it (actually... I'm changing the code pretty
significantly to use the ZPatterns product) but it's slow going
as I have lots of other competing projects.
Help, as always, is appreciated. ;-)
-steve
>
Petru Paler wrote:
>
> Hi eveyone.
>
> While playing around with the development version of ACS (ArsDigita Community
> System), I noticed a very nice feature they introduced, namely page contracts.
I've been working with the ACS quite a bit lately (day-job:). its a nice
a system that offers a l
Bill Anderson wrote:
>
> (Membership devel issue)
>
> OK, since I was getting nowhere, I tried a nre tack. I made the roles property a
>multiple_select. Seemed to work great.
> I could give roles to members.
>
> BUT, as soon as I deleted it ...
>
> TypeError
Found it. Seems I set role
(Membership devel issue)
OK, since I was getting nowhere, I tried a nre tack. I made the roles property a
multiple_select. Seemed to work great.
I could give roles to members.
BUT, as soon as I deleted it ...
TypeError
Sorry, a Zope error occurred.
Traceback (innermost last
14 matches
Mail list logo