Hi Florent
> -Original Message-
> From: Florent Guillaume [mailto:[EMAIL PROTECTED]
> Sent: Thursday, December 01, 2005 4:24 PM
> To: [EMAIL PROTECTED]
> Cc: zope3-dev
> Subject: Re: ObjectMover events
>
> Florent Guillaume wrote:
> >> I dont' know if this affect the events itself but t
Hi folks,
When you do HTTP DELETE on objects that do not explicitly support
deletion, the default view (zope.app.http.delete.DELETE) tries to adapt
self.context.__parent__ to IWriteDirectory, which raises a TypeError
which is never caught. I suggest changing the view to raise
MethodNotAllowed inst
Florent Guillaume wrote:
I dont' know if this affect the events itself but there is also a
problem in the ObjectMover.
If you use the ObjectMover from copypastemove on IDependable
(registered) objects, it's not possible to move a object because of
the order the move process is implemented.
On Thursday 01 December 2005 09:50, Christian Theune wrote:
> I'll start about 12am CET. I'm not sure if there would be a seperate
> channel than #zope3-dev for this event.
Let's keep it on #zope3-dev.
Here is a third person acknowledging the date. :-)
Regards,
Stephan
--
Stephan Richter
CBU Ph
Hi,
I'm a bit confused but I'll just go forward, because I was motivated by
#zope3-dev.
Tomorrow was a date in question for a bug day. Two people acknowledged
it and I just realized that Zope 3.2 is already at risk for falling
behind schedule. Therefor I'm willing to spend my time tomorrow to wor
Hi All,
Do we want Zope to always respond to this header?
Yes, it's helpful for testing, but surely it risks information
disclosure vulnerabilities or worse if used on a production application?
cheers,
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www
The Buildbot has detected a failed build of Zope3 trunk 2.4 Linux tlotze.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 1889
Blamelist: mgedmin
BUILD FAILED: failed test_2
sincerely,
-The Buildbot
___
Zope3-dev ma
The Buildbot has detected a failed build of Zope3 trunk 2.4 Linux zc-buildbot.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 1889
Blamelist: mgedmin
BUILD FAILED: failed test_2
sincerely,
-The Buildbot
___
Zope3-d
On Dec 1, 2005, at 5:46 AM, Chris Withers wrote:
Gary Poster wrote:
I have a form as follows:
...
...
Now, I do the following with a zope.testbrowser.browser:
browser.getForm(name='form_name').getControl(' Do Something
').click()
However, the value of REQUEST.form['action'] in aPyth
On Nov 30, 2005, at 2:18 PM, Chris Withers wrote:
Gary Poster wrote:
Zope 2 depends on Zope 3, via Five. Zope 3 does not depend on
Zope 2.
A very good point, but one which makes me feel that Zope 2
shouldn't be merged in with Zope 3 ;-)
Actually, yes, all of my points were made to that
I dont' know if this affect the events itself but there is also a
problem in the ObjectMover.
If you use the ObjectMover from copypastemove on IDependable (registered)
objects, it's not possible to move a object because of the order the move
process is implemented.
---
target[new_name] = obj
Gary Poster wrote:
I have a form as follows:
...
...
Now, I do the following with a zope.testbrowser.browser:
browser.getForm(name='form_name').getControl(' Do Something ').click()
However, the value of REQUEST.form['action'] in aPythonScript is " Go
", not " Do Something ", as I'd ex
12 matches
Mail list logo
