See the discussion on plone-dev a while ago, link integrity checking
will make Plone 3.0 broken and dangerous. Worth trying with 2.9.8 at least.
Laurence
--On 18. August 2007 21:03:43 +0200 Andreas Jung
[EMAIL PROTECTED] wrote:
--On 23. Juli 2007 08:53:32 +0200 Wichert Akkerman
[EMAIL
Summary of messages to the zope-tests list.
Period Mon Feb 18 12:00:00 2008 UTC to Tue Feb 19 12:00:00 2008 UTC.
There were 6 messages: 6 from Zope Unit Tests.
Tests passed OK
---
Subject: OK : Zope-2.7 Python-2.3.6 : Linux
From: Zope Unit Tests
Date: Mon Feb 18 21:03:01 EST 2008
This only applies to Zope3 developers and people using the Zope 3 ZMI.
I'm trying to get rid of ThreadedAsync. zope.app.server uses it to
cause the asyncore main loop to stop as part of the server-control
functionality.
There are no tests for this afaict. Trying this throigh the web,
On Feb 19, 2008, at 8:59 AM, Lennart Regebro wrote:
On Tue, Feb 19, 2008 at 12:43 PM, Jim Fulton [EMAIL PROTECTED] wrote:
This only applies to Zope3 developers and people using the Zope 3
ZMI.
I'm trying to get rid of ThreadedAsync. zope.app.server uses it to
cause the asyncore main loop
On Tue, Feb 19, 2008 at 12:43 PM, Jim Fulton [EMAIL PROTECTED] wrote:
This only applies to Zope3 developers and people using the Zope 3 ZMI.
I'm trying to get rid of ThreadedAsync. zope.app.server uses it to
cause the asyncore main loop to stop as part of the server-control
functionality.
Hi,
Jim Fulton schrieb:
This only applies to Zope3 developers and people using the Zope 3 ZMI.
I'm trying to get rid of ThreadedAsync. zope.app.server uses it to
cause the asyncore main loop to stop as part of the server-control
functionality.
There are no tests for this afaict. Trying
On Tue, Feb 19, 2008 at 3:10 PM, Jim Fulton [EMAIL PROTECTED] wrote:
It can't be that useful since restart doesn't work and no one bothered
to write a test for this functionality.
It's less useful in Zope3 than in Zope2, that's for sure.
--
Lennart Regebro: Zope and Plone consulting.
I'm told that, here at Georgia Tech, we are running our Plone's Zope
2.10 behind pound, and that we need some way to signal it about
which requests are coming in through http and which came through
https, so that all of the links generated by Plone can start with
the right protocol. So at the
Hi,
I have Zope commit rights now. I have subscribed to the zope-checkins
list:
http://mail.zope.org/mailman/options/zope-checkins
But when I commit something (I committed to the Sandbox and today to
z3c.sqlalchemy) I get an email:
=
Your mail to 'Checkins' with the subject
Jim Fulton, on 2008-02-19:
You were getting this from the Checkins list, not zope-checkins. I've
updated the list to accept your posts.
Ah, I see. They come through now. Thanks.
--
Maurits van Rees | http://maurits.vanrees.org/
Work | http://zestsoftware.nl/
This is your day,
You were getting this from the Checkins list, not zope-checkins. I've
updated the list to accept your posts.
Jim
On Feb 19, 2008, at 4:01 PM, Maurits van Rees wrote:
Hi,
I have Zope commit rights now. I have subscribed to the zope-checkins
list:
The reason that that more folks probably don't complain about this is that they
probably use Apache to do URL rewriting in conjunction with Zope's virtual host
monster. And under that scenario, you indicate that you want Zope to generate
https urls within the Apache rewrite rule as opposed to
Hi Chris
Betreff: Re: [Zope-dev] can we teach official Zope to start
detecting HTTPSheader?
[...]
(Although I'm not volunteering, every time I try to check
something in to the Zope repository these days, Philipp yells
at me about style, so I'm getting gun-shy... ;-) )
Philipp? Who's
13 matches
Mail list logo