On Fri, 11 Oct 2002, Adrian Hungate wrote:
I don't know if this is a Zope, CMF, Plone or DCWorkflow issue, but I just
got bitten by what appears to be a bug in someone's security handling.
If you create some content as user A, then delete user A, no one can edit
the content, or change it's
SHH == Stefan H Holek [EMAIL PROTECTED] writes:
SHH Hi All! I am experiencing a lot of 'ZODB conflict error at
SHH ...' that I can reliably reproduce by hitting my browser's
SHH Refresh button at a high rate. The bad news is that the
SHH conflicts happen on pages that are not supposed
At 17:48 2002-10-11 +0200, Holger Blasum said:
I observed that under Debian woody, Zope 2.5.1 runs under the
user id 'www-data'.
The python OS command os.getgroups() gives me an empty list when called
from an external method, although I had configured the user 'www-data'
to be the
On Fri, Oct 11, 2002 at 06:05:59PM +0200, Johan Carlsson [EasyPublisher] wrote:
The way that Zope changes user under the start up sequence
doesn't change the groups.
man 2 setgroups
should be called after (before?) the user id change in the
Zope startup script.
it is called for you by PAM
Thanks Jerome, Johan,
it is called for you by PAM when you log in, AFAIK, this is
why it works from your command line
That was the missing bit.
After following some blind alleys (pam-python seems to be only
available for py 1.5 and os.setgroups() is only available in py 2.2)
From: Craeg K Strong [EMAIL PROTECTED]
Here is my question. Should ZWiki, my web app, and everybody else's
Zope-based web app in the world have to add Date headers?
Or maybe MailHost should be smart enough to add a Date header with
Date=now if Date is missing from the header...?
conflict errors do not imply conflicting writes by definition. there is
a thing called read conflict, which is probably what happens to you.
On Friday, Oct 11, 2002, at 07:47 US/Eastern, Stefan H. Holek wrote:
I am experiencing a lot of 'ZODB conflict error at ...' that I can
From: Lennart Regebro [EMAIL PROTECTED]
Indeed, reading in RFC 2822, the origination date-field is required, which
means that the header munging done in MailHost should also look for a date
header and add it if it doesn't exist.
A simple addition of:
if not mo.getheader('Date'):
RFC 2822 (which is the currently valid one, if I understand correctly)
specifies the date format to have four digit zone specifications, ie
GMT+0200, while DateTime.rfc822() happily returns GMT+2. Not that this
seems to be any problem, I'm just looking for an answer if this is how it's
Yes, but AFAIK read conflicts mean that something has changed during a
read. I do not expect this to happen either...
--On Freitag, 11. Oktober 2002 07:54 -0400 Jens Vagelpohl [EMAIL PROTECTED]
conflict errors do not imply conflicting writes by definition. there is a
Mail list logo