From cklinger at novareto.de  Mon Nov  1 12:05:28 2010
From: cklinger at novareto.de (Christian Klinger)
Date: Mon, 01 Nov 2010 16:05:28 -0000
Subject: [zope2-tracker] [Bug 452259] Re: TAL blocks inside <style> result
	in parse error
References: <20091015152904.3816.84348.malonedeb@gangotri.canonical.com>
Message-ID: <20101101160530.23226.5127.launchpad@palladium.canonical.com>

** Changed in: grok
       Status: New => Won't Fix

-- 
TAL blocks inside <style> result in parse error
https://bugs.launchpad.net/bugs/452259
You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.

From cklinger at novareto.de  Mon Nov  1 12:15:52 2010
From: cklinger at novareto.de (Christian Klinger)
Date: Mon, 01 Nov 2010 16:15:52 -0000
Subject: [zope2-tracker] [Bug 430662] Re: tal:omit-tag should be processed
	before	tal:attributes
References: <20090916113349.24838.19672.malonedeb@gangotri.canonical.com>
Message-ID: <20101101161555.23226.22234.launchpad@palladium.canonical.com>

** Changed in: grok
       Status: New => Won't Fix

-- 
tal:omit-tag should be processed before tal:attributes
https://bugs.launchpad.net/bugs/430662
You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.

From sylvain at infrae.com  Mon Nov  1 16:53:06 2010
From: sylvain at infrae.com (Sylvain Viollon)
Date: Mon, 01 Nov 2010 20:53:06 -0000
Subject: [zope2-tracker] [Bug 669649] [NEW] Url computation of a Five
	resource located in a	directory resource fails
References: <20101101205306.16000.50384.malonedeb@gandwana.canonical.com>
Message-ID: <20101101205306.16000.50384.malonedeb@gandwana.canonical.com>

Public bug reported:

If you ask via __call__() the URL of a resource on a Five resource
located in a directory resource, you obtain a URL valid only for Zope 3:

http://localhost/manfred/@@/five.grok.ftests.view/style.css

(The @@ are not implemented in Zope 2,
http://localhost/manfred//++resource++five.grok.ftests.view/style.css is
the expected result).

This result can only be obtained if you setup a local site somewhere in
the context parent list, otherwise you get an error that there is not
enough information to compute the URL (this could been seen as a bug in
zope.browserresource).

After looking a bit, this error comes from a lack of support in the
__call__ method in the class Products.Five.resource.Resource: there is a
getMultiAdapter with the resource's parent to get an AbsoluteURL
adapter, that actually return a specific adapter for resource in the
case where the parent is a DirectoryResource (implemented in
zope.browserresource, registered for IResource).

** Affects: zope2
     Importance: Undecided
         Status: New

-- 
Url computation of a Five resource located in a directory resource fails
https://bugs.launchpad.net/bugs/669649
You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.

From 669856 at bugs.launchpad.net  Tue Nov  2 06:49:18 2010
From: 669856 at bugs.launchpad.net (peter)
Date: Tue, 02 Nov 2010 10:49:18 -0000
Subject: [zope2-tracker] [Bug 669856] [NEW] mkzopeinstance is missing
	"manuel"
References: <20101102104919.18518.62315.malonedeb@wampee.canonical.com>
Message-ID: <20101102104919.18518.62315.malonedeb@wampee.canonical.com>

Public bug reported:

I installed zope with: "pip install Zope2". Running: "mkzopeinstance
tester" produced the following Error:

mkzopeinstance tester
Traceback (most recent call last):
  File "/.../bin/mkzopeinstance", line 5, in <module>
    from pkg_resources import load_entry_point
  File ".../lib/python2.6/site-packages/setuptools-0.6c11-py2.6.egg/pkg_resources.py", line 2603, in <module>
  File ".../lib/python2.6/site-packages/setuptools-0.6c11-py2.6.egg/pkg_resources.py", line 666, in require
  File ".../lib/python2.6/site-packages/setuptools-0.6c11-py2.6.egg/pkg_resources.py", line 565, in resolve
pkg_resources.DistributionNotFound: manuel

Im using Pyhton2.6.5/MacOS and the same happend on a Linux-System(Python
2.6.6).

After a "pip install manuel" mkzopeinstance works fine.

** Affects: zope2
     Importance: Undecided
         Status: New

-- 
mkzopeinstance is missing "manuel"
https://bugs.launchpad.net/bugs/669856
You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.

From hanno at hannosch.eu  Tue Nov  2 10:30:07 2010
From: hanno at hannosch.eu (Hanno Schlichting)
Date: Tue, 02 Nov 2010 14:30:07 -0000
Subject: [zope2-tracker] [Bug 669856] Re: mkzopeinstance is missing "manuel"
References: <20101102104919.18518.62315.malonedeb@wampee.canonical.com>
Message-ID: <20101102143007.16000.49426.malone@gandwana.canonical.com>

pip is not supported as a way to install Zope2. Please follow the
instructions at http://docs.zope.org/zope2/releases/2.13/INSTALL.html to
use virtualenv / easy_install.

** Changed in: zope2
       Status: New => Invalid

-- 
mkzopeinstance is missing "manuel"
https://bugs.launchpad.net/bugs/669856
You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.

From hanno at hannosch.eu  Fri Nov  5 12:02:10 2010
From: hanno at hannosch.eu (Hanno Schlichting)
Date: Fri, 05 Nov 2010 16:02:10 -0000
Subject: [zope2-tracker] [Bug 669649] Re: Url computation of a Five resource
	located in a	directory resource fails
References: <20101101205306.16000.50384.malonedeb@gandwana.canonical.com>
Message-ID: <20101105160210.3636.95967.malone@wampee.canonical.com>

Indeed. Until very recently subdirectories in resource directories
weren't supported at all inside Zope2. In the latest Zope 2.12 versions
they should no longer throw errors but might still not work in full

** Changed in: zope2
   Importance: Undecided => Low

** Changed in: zope2
       Status: New => Confirmed

-- 
Url computation of a Five resource located in a directory resource fails
https://bugs.launchpad.net/bugs/669649
You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.

From white.silenc3.lists at gmail.com  Sun Nov  7 10:15:17 2010
From: white.silenc3.lists at gmail.com (white silence)
Date: Sun, 7 Nov 2010 16:15:17 +0100
Subject: [zope2-tracker] PCGIServer.py patch proposal
Message-ID: <AANLkTikwb8tPAO88xLHcSFYi4YTZ=wT-KOVwvydmULa+@mail.gmail.com>

Even i know that the PCGI method is deprecated, IMHO it is another
richness of Zope and can be useful in some scenarios, specially now
that Plone4 is faster and less resource-consuming . Using Plone 4 i
got the error below.

Someone pointed me to this
https://bugs.launchpad.net/python/+bug/418454 , so i almost pasted the
same to the "push" method in PCGIServer.py, and it seems to work by
now.

Could some developer, please, check the patch attached and improve it
if necessary ?

Many thanks!


Error trace is :
============================================================================================
~/opt/var/zopeservers/instances/my_instance4$ ./bin/instance fg
2010-11-07 14:53:40 INFO ZServer PCGI Server started at Sun Nov  7 14:53:40 2010
	Unix socket: /home/user/opt/var/zopeservers/instances/my_instance4/var/pcgi.soc
2010-11-07 14:53:53 WARNING ZODB.blob (10771) Blob dir
/home/user/opt/var/zopeservers/instances/my_instance4/var/blobstorage/
has insecure mode setting
2010-11-07 14:54:32 INFO Zope Ready to handle requests
2010-11-07 14:54:32 ERROR ZServerPublisher exception caught
Traceback (most recent call last):
  File "/home/user/opt/var/zopeservers/packages/eggs/Zope2-2.12.10-py2.6-linux-i686.egg/ZServer/PubCore/ZServerPublisher.py",
line 33, in __init__
    b._finish()
  File "/home/user/opt/var/zopeservers/packages/eggs/Zope2-2.12.10-py2.6-linux-i686.egg/ZServer/PCGIServer.py",
line 354, in _finish
    self.stdout.close()
  File "/home/user/opt/var/zopeservers/packages/eggs/Zope2-2.12.10-py2.6-linux-i686.egg/ZServer/PCGIServer.py",
line 385, in close
    self._channel.push('%010d%s%010d' % (l, data, 0), 0)
  File "/home/user/opt/var/zopeservers/packages/eggs/Zope2-2.12.10-py2.6-linux-i686.egg/ZServer/PCGIServer.py",
line 195, in push
    self.producer_fifo.push(producer)
AttributeError: 'collections.deque' object has no attribute 'push'
^C2010-11-07 14:54:46 INFO SignalHandler Caught signal SIGINT
2010-11-07 14:54:46 INFO Z2 Shutting down
-------------- next part --------------
A non-text attachment was scrubbed...
Name: push_pcgiserver.patch
Type: text/x-patch
Size: 1172 bytes
Desc: not available
Url : http://mail.zope.org/pipermail/zope2-tracker/attachments/20101107/87826841/attachment.bin 

From sylvain at infrae.com  Mon Nov  8 04:48:36 2010
From: sylvain at infrae.com (Sylvain Viollon)
Date: Mon, 08 Nov 2010 09:48:36 -0000
Subject: [zope2-tracker] [Bug 669649] Re: Url computation of a Five resource
	located in a	directory resource fails
References: <20101101205306.16000.50384.malonedeb@gandwana.canonical.com>
Message-ID: <20101108094836.31595.21766.malone@wampee.canonical.com>

I used that same five.grok code in Zope 2.12 (and I think 2.11), and it
used to work correctly (in exporting resources directories and computing
URLs for those resources). It is the change to zope.browserresources
which broken it, as it work differently than the previous
implementation.

-- 
Url computation of a Five resource located in a directory resource fails
https://bugs.launchpad.net/bugs/669649
You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.

From 672846 at bugs.launchpad.net  Mon Nov  8 20:48:06 2010
From: 672846 at bugs.launchpad.net (Elizabeth Leddy)
Date: Tue, 09 Nov 2010 01:48:06 -0000
Subject: [zope2-tracker] [Bug 672846] [NEW] checkValidId breaks on unicode
	ids
References: <20101109014806.7427.18128.malonedeb@gandwana.canonical.com>
Message-ID: <20101109014806.7427.18128.malonedeb@gandwana.canonical.com>

Public bug reported:

In OFS, ObjectManager.py, if you send in a unicode id it raises bad a
bad request, although it seems like one should still be able to send it
in. The code looks like its missing an else statement:

def checkValidId(self, id, allow_dup=0):
    ...
    if not id or not isinstance(id, str):
        if isinstance(id, unicode):
            id = escape(id)
        raise BadRequest, ('Empty or invalid id specified', id)
    ...

Based on this it looks like the bad request error should only be thrown if the id is not unicode. Hard to say for sure though.
Running Zope 2.12 but it looks like its in the latest release as well.

** Affects: zope2
     Importance: Undecided
         Status: New

-- 
checkValidId breaks on unicode ids
https://bugs.launchpad.net/bugs/672846
You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.

From hanno at hannosch.eu  Tue Nov  9 15:56:16 2010
From: hanno at hannosch.eu (Hanno Schlichting)
Date: Tue, 09 Nov 2010 20:56:16 -0000
Subject: [zope2-tracker] [Bug 672846] Re: checkValidId breaks on unicode ids
References: <20101109014806.7427.18128.malonedeb@gandwana.canonical.com>
Message-ID: <20101109205616.8672.18814.malone@soybean.canonical.com>

Zope2 only supports ids in ascii, so the validator is correct. Adding
support for Unicode ids is a long requested feature, which nobody had
time to implement yet.

** Changed in: zope2
   Importance: Undecided => Wishlist

** Changed in: zope2
       Status: New => Confirmed

-- 
checkValidId breaks on unicode ids
https://bugs.launchpad.net/bugs/672846
You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.

From 142148 at bugs.launchpad.net  Tue Nov  9 20:48:02 2010
From: 142148 at bugs.launchpad.net (Chris Hamono)
Date: Wed, 10 Nov 2010 01:48:02 -0000
Subject: [zope2-tracker] [Bug 142148] Re: DateTime default timezone wrong in
	some locations
References: <20070922055217.2376.87101.launchpad@carbon.canonical.com>
Message-ID: <20101110014803.24445.32330.malone@soybean.canonical.com>

CST Bug

This problem has been a long running Issue. With the help of Dixond on
the plone irc chat we have resolved the issue that was effecting us in
Adelaide Australia.

None of the other fixes noted elsewhere worked

The issue stems form both CST and EST being hard coded into the datetime
module.

I do not know why that was done, perhaps the attached patch may break
some installs but for us it meant we now get the correct date being
reported when we use plone

with the patch installed our installation now reports the correct time.
I havent checked other timezones and we are currently in DST. I haven't
yet checked normal time.

We did not require the addition of the TZ environment variable as noted
elsewhere. It did not work anyway.

DC

** Patch added: "DateTime.py and datetime/__init__.py patch for Australian CST and EST timezones"
   https://bugs.launchpad.net/datetime/+bug/142148/+attachment/1728541/+files/0001-modified-datetime-to-allow-Australian-CST-and-EST.patch

-- 
DateTime default timezone wrong in some locations
https://bugs.launchpad.net/bugs/142148
You received this bug notification because you are a member of Zope 2
Developers, which is the registrant for DateTime.

From 501805 at bugs.launchpad.net  Tue Nov  9 22:33:34 2010
From: 501805 at bugs.launchpad.net (Chris Hamono)
Date: Wed, 10 Nov 2010 03:33:34 -0000
Subject: [zope2-tracker] [Bug 501805] Re: TZ environment variable doesn't
	work when using	runzope.py
References: <20091231023909.5199.53200.malonedeb@palladium.canonical.com>
Message-ID: <20101110033334.20780.6416.malone@wampee.canonical.com>

I think this only effects CST and EST from timezones other than the US
e.g. Australia.

see https://bugs.launchpad.net/datetime/+bug/142148/comments/20

DC

-- 
TZ environment variable doesn't work when using runzope.py
https://bugs.launchpad.net/bugs/501805
You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.

From lists at zopyx.com  Tue Nov  9 22:39:43 2010
From: lists at zopyx.com (Andreas Jung)
Date: Wed, 10 Nov 2010 03:39:43 -0000
Subject: [zope2-tracker] [Bug 672846] Re: checkValidId breaks on unicode ids
References: <20101109014806.7427.18128.malonedeb@gandwana.canonical.com>
Message-ID: <20101110033943.20780.70887.malone@wampee.canonical.com>

Isn't there a huge Dieter patch floating around somewhere in the
tracker?

-- 
checkValidId breaks on unicode ids
https://bugs.launchpad.net/bugs/672846
You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.

From 142148 at bugs.launchpad.net  Tue Nov  9 23:15:12 2010
From: 142148 at bugs.launchpad.net (Dylan Jay)
Date: Wed, 10 Nov 2010 04:15:12 -0000
Subject: [zope2-tracker] [Bug 142148] Re: DateTime default timezone wrong in
	some locations
References: <20070922055217.2376.87101.launchpad@carbon.canonical.com>
Message-ID: <20101110041512.20607.93947.malone@wampee.canonical.com>

Chris your fix is no better than the previous ones. It will break
american EST. This is a really hard problem to solve for all the reasons
above.

The best work around for now is the one I mention in https://bugs.launchpad.net/zope2/+bug/501805.
We use this for all our australian clients. We're an Australian Plone integrator.

That is override the TZ env var on an instance by instance basis. (the
code below is up to date with the latest NSW timezone rules btw).

[instance]
recipe = plone.recipe.zope2instance
...
environment-vars =
    TZ AEST-10AEDT-11,M10.1.0/02:00:00,M4.1.0/03:00:00

The only caveat is that there seems to be a bug in zope that to make
this work you have to run

bin/instance console

instead of runzope.py.

but I'm told "instance console" is now the recommended of running plone
in production anyway so it's not that much of an issue.

It would sitll be nice to have a zope (and python) that "just works" for
AEST :)

-- 
DateTime default timezone wrong in some locations
https://bugs.launchpad.net/bugs/142148
You received this bug notification because you are a member of Zope 2
Developers, which is the registrant for DateTime.

From 501805 at bugs.launchpad.net  Tue Nov  9 23:18:47 2010
From: 501805 at bugs.launchpad.net (Dylan Jay)
Date: Wed, 10 Nov 2010 04:18:47 -0000
Subject: [zope2-tracker] [Bug 501805] Re: TZ environment variable doesn't
	work when using	runzope.py
References: <20091231023909.5199.53200.malonedeb@palladium.canonical.com>
Message-ID: <20101110041847.20690.86917.malone@wampee.canonical.com>

Hi,

No I don't believe this bug only affects CST and EST. This bug is about
overriding environment variables in zope and how it works with "instance
console" and doesn't work with runzope.py. The TZ example is just that,
an example. but then again I haven't tried other environment variables
to show that the same thing happens with them :)

-- 
TZ environment variable doesn't work when using runzope.py
https://bugs.launchpad.net/bugs/501805
You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.

From 142148 at bugs.launchpad.net  Wed Nov 10 00:34:15 2010
From: 142148 at bugs.launchpad.net (Chris Hamono)
Date: Wed, 10 Nov 2010 05:34:15 -0000
Subject: [zope2-tracker] [Bug 142148] Re: DateTime default timezone wrong in
	some locations
References: <20070922055217.2376.87101.launchpad@carbon.canonical.com>
Message-ID: <20101110053415.12465.3484.malone@gandwana.canonical.com>

Sorry but I am not particularly knowledgeable about zope/plone or even
python. I cannot find bin/instance? Perhaps it is created in the
buildout process.

We don't use buildouts, not my call that's just the way it is.
so I cant use... 
[instance]
recipe = plone.recipe.zope2instance
...
environment-vars =
    TZ AEST-10AEDT-11,M10.1.0/02:00:00,M4.1.0/03:00:00

I tried setting the TZ in zope.conf but it did not take. I assume that
is because of the environment not being passed to the child environment
as mentioned in other posts about this bug.

When I tried to use TZ I used zopectl fg it didnt work. I think zopectl
is the actual script you are talking about. I can't see any
documentation mentioning other ways to start Zope. and as stated I used
zopectl and got no joy when setting the TZ variable.

The patch I submitted makes it work for Australian and presumably other
users. The fact that the timezone was hardcoded into DateTime only shows
the bug is more insidious than a simple 'typo'.

Why was it hardcoded into DateTime? perhaps because older servers had
the timezone configured to CST instead of US/Central!

Isn't it better that they configure their servers to the correct
timezone instead of using an old non portable syntax?

I stick by the fix, cst:US/Central in DateTime appears to be a kludge it
is non conformant with other entries in there.

Needless to say it works for us and it may also be the impetus for the
maintainers to actually fix the issue, which has remained open for 8
years. It certainly points towards where the real culprit lies.

Your fix may work well for you, but for us it did not work, probably
because we don't do it the "correct way".

I only bothered posting the fix here for those miserable few like us
that can't use other fixes.

DC

-- 
DateTime default timezone wrong in some locations
https://bugs.launchpad.net/bugs/142148
You received this bug notification because you are a member of Zope 2
Developers, which is the registrant for DateTime.

From regebro at gmail.com  Wed Nov 10 04:35:40 2010
From: regebro at gmail.com (Lennart Regebro)
Date: Wed, 10 Nov 2010 09:35:40 -0000
Subject: [zope2-tracker] [Bug 142148] Re: DateTime default timezone wrong in
	some locations
References: <20070922055217.2376.87101.launchpad@carbon.canonical.com>
Message-ID: <20101110093540.20607.75414.malone@wampee.canonical.com>

Chris: bin/instance is the script you use to start the zope instance
with. It may have different names. runzope is common,

There *is no way* to reliably determine what timezone you are in.
DateTime can only do a best guess. And that means that if you are in
CST, it will guess that this means Central Standard Time, as this is
what it usually means. If it guesses incorrectly, the solution is to use
a specific TZ variable as Dylans solution above.

-- 
DateTime default timezone wrong in some locations
https://bugs.launchpad.net/bugs/142148
You received this bug notification because you are a member of Zope 2
Developers, which is the registrant for DateTime.

From 673441 at bugs.launchpad.net  Wed Nov 10 05:56:47 2010
From: 673441 at bugs.launchpad.net (M.-A. Lemburg)
Date: Wed, 10 Nov 2010 10:56:47 -0000
Subject: [zope2-tracker] [Bug 673441] [NEW] Poor installation user experience
References: <20101110105647.20536.33101.malonedeb@wampee.canonical.com>
Message-ID: <20101110105647.20536.33101.malonedeb@wampee.canonical.com>

Public bug reported:

I think that the installation part of the user experience needs to be
revisited:

<user-story>

A user wants to install Zope2 using buildout...

She goes to http://www.zope.org/, then see the note on the new website,
clicks on the link, goes to http://zope2.zope.org/

She then clicks on the release news item
http://zope2.zope.org/news/zope-2.13.0-released, finds the notes on the
release, but no download or installation information.

She then search the site and finds the "Getting Zope 2" link at the top,
clicks on it and goes to http://zope2.zope.org/releases

She reads the installation instructions, clicks on the link and gets
directed to http://docs.zope.org/zope2/releases/2.12/INSTALL.html

After some research, she finds that the page points to Zope 2.12 and not
2.13, so she goes back and clicks on the docs.zope.org link. This takes
her to a documentation overview, but there no sign of any installation
instructions, so she goes back to the 2.12 installation instructions.

After some more research, she finds a link "Zope Release Information"
and goes to http://docs.zope.org/zope2/releases/index.html

On that page, she finds the Zope 2.13 links to the "Installing and Zope
with zc.buildout" (sic !), clicks on it a finally arrives at the page
http://docs.zope.org/zope2/releases/2.13/INSTALL-buildout.html

She then follows instructions and hits the first bummer:

wget http://pypi.python.org/packages/source/Z/Zope2/Zope2-<Zope
version>.tar.gz

No .tar.gz is available. Looking at
http://pypi.python.org/packages/source/Z/Zope2/ she finds that there's a
ZIP file, so downloads that and unzips it.

Continuing with the instructions she tries to bootstrap the
installation:

/path/to/your/python bootstrap/bootstrap.py

bin/python: can't open file 'bootstrap/bootstrap.py': [Errno 2] No such
file or directory

Looking at the directory, she sees that there's a bootstrap.py in the
root dir of the distribution.

She runs that and then continues with bin/buildout.

This generates a few warnings which she ignores.

To her surprise, buildout then goes on to download a huge number of
package eggs, even though she installed from a ZIP file (which she
expected to already contain copies of all of these).

After getting coffee, she then finally sees the script complete.

She then follows instructions, runs bin/mkzopeinstance, enters instance1
as dir and the admin user details.

Finally, she starts Zope using instance1/bin/zopectl start

.
daemon process started, pid=9760

Hmm, no mention of the site URL. So she looks in instance1/etc/zope.conf
and finds that the standard location hasn't changed in the new release.

Pointing a brower at http://127.0.0.1:8080/ gives her the ZMI as
expected.

</user-story>

There are a couple of things that would greatly improve the user
experience:

 * the release news should include a link to the (correct) installation instructions
 * the download page should point to the installation instructions for each release version (since these differ per version), not only the change logs
 * the installation instructions should be updated to what's actually available on the download server
 * the buildout instructions need to be updated to what's actually in the ZIP archive
 * it would help, if the installation instructions included a hint on how to quickly fire up Zope for a test (it's not obvious that clicking "next" on the page will get you to those instructions and new users won't read the "Creating a buildout-based Zope instance", since they already followed the instructions on "Creating a Zope instance")

** Affects: zope2
     Importance: Undecided
         Status: New

-- 
Poor installation user experience
https://bugs.launchpad.net/bugs/673441
You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.

From hanno at hannosch.eu  Wed Nov 10 11:44:06 2010
From: hanno at hannosch.eu (Hanno Schlichting)
Date: Wed, 10 Nov 2010 16:44:06 -0000
Subject: [zope2-tracker] [Bug 673441] Re: Poor installation user experience
References: <20101110105647.20536.33101.malonedeb@wampee.canonical.com>
Message-ID: <20101110164406.12399.1053.malone@gandwana.canonical.com>

The install experience could certainly use some help.

** Changed in: zope2
       Status: New => Confirmed

-- 
Poor installation user experience
https://bugs.launchpad.net/bugs/673441
You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.

From hanno at hannosch.eu  Wed Nov 10 11:54:30 2010
From: hanno at hannosch.eu (Hanno Schlichting)
Date: Wed, 10 Nov 2010 16:54:30 -0000
Subject: [zope2-tracker] [Bug 672846] Re: checkValidId breaks on unicode ids
References: <20101109014806.7427.18128.malonedeb@gandwana.canonical.com>
Message-ID: <20101110165430.8560.31976.malone@palladium.canonical.com>

There's https://bugs.launchpad.net/zope2/+bug/374724 which has some code
and a really minor number of tests. With a change like this, there's
lots of places where things will go wrong. So the provided patch is not
more than a basic starting ground. The patch is even marked as "tests
failing".

-- 
checkValidId breaks on unicode ids
https://bugs.launchpad.net/bugs/672846
You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.

From lists at zopyx.com  Wed Nov 10 12:36:16 2010
From: lists at zopyx.com (Andreas Jung)
Date: Wed, 10 Nov 2010 17:36:16 -0000
Subject: [zope2-tracker] [Bug 673441] Re: Poor installation user experience
References: <20101110105647.20536.33101.malonedeb@wampee.canonical.com>
Message-ID: <20101110173616.8483.52369.malone@palladium.canonical.com>

There is perhaps _little_ help available soon. www.zope.org is subject to be relaunched soon...most of the www.zope.org
cruft should have gone. Instead people interested in Zope 2 should find their exit to 

https://zope2.zope.org/

There is a dedicated "Getting Zope" tab....there is already a list of download links and links to the installation docs.
Of course there is place for improvements :)

-- 
Poor installation user experience
https://bugs.launchpad.net/bugs/673441
You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.

From 673441 at bugs.launchpad.net  Wed Nov 10 15:51:52 2010
From: 673441 at bugs.launchpad.net (M.-A. Lemburg)
Date: Wed, 10 Nov 2010 20:51:52 -0000
Subject: [zope2-tracker] [Bug 673441] Re: Poor installation user experience
References: <20101110105647.20536.33101.malonedeb@wampee.canonical.com>
Message-ID: <20101110205153.24445.15371.launchpad@soybean.canonical.com>

** Description changed:

  I think that the installation part of the user experience needs to be
  revisited:
  
  <user-story>
  
  A user wants to install Zope2 using buildout...
  
- She goes to http://www.zope.org/, then see the note on the new website,
- clicks on the link, goes to http://zope2.zope.org/
+ She goes to http://www.zope.org/, then sees the note regarding the new
+ website, clicks on the link, goes to http://zope2.zope.org/
  
  She then clicks on the release news item
  http://zope2.zope.org/news/zope-2.13.0-released, finds the notes on the
  release, but no download or installation information.
  
- She then search the site and finds the "Getting Zope 2" link at the top,
- clicks on it and goes to http://zope2.zope.org/releases
+ She then searches the site and finds the "Getting Zope 2" link at the
+ top, clicks on it and goes to http://zope2.zope.org/releases
  
  She reads the installation instructions, clicks on the link and gets
  directed to http://docs.zope.org/zope2/releases/2.12/INSTALL.html
  
  After some research, she finds that the page points to Zope 2.12 and not
- 2.13, so she goes back and clicks on the docs.zope.org link. This takes
- her to a documentation overview, but there no sign of any installation
- instructions, so she goes back to the 2.12 installation instructions.
+ 2.13, so she goes back and clicks on the http://docs.zope.org/ link.
+ This takes her to a documentation overview, but there is no sign of
+ installation instructions, so she goes back to the 2.12 installation
+ instructions.
  
  After some more research, she finds a link "Zope Release Information"
  and goes to http://docs.zope.org/zope2/releases/index.html
  
- On that page, she finds the Zope 2.13 links to the "Installing and Zope
- with zc.buildout" (sic !), clicks on it a finally arrives at the page
+ On that page, she finds the Zope 2.13 links to "Installing and Zope with
+ zc.buildout" (sic !), clicks on it a finally arrives at the page
  http://docs.zope.org/zope2/releases/2.13/INSTALL-buildout.html
  
  She then follows instructions and hits the first bummer:
  
  wget http://pypi.python.org/packages/source/Z/Zope2/Zope2-<Zope
  version>.tar.gz
  
  No .tar.gz is available. Looking at
  http://pypi.python.org/packages/source/Z/Zope2/ she finds that there's a
  ZIP file, so downloads that and unzips it.
  
  Continuing with the instructions she tries to bootstrap the
  installation:
  
  /path/to/your/python bootstrap/bootstrap.py
  
  bin/python: can't open file 'bootstrap/bootstrap.py': [Errno 2] No such
  file or directory
  
  Looking at the directory, she sees that there's a bootstrap.py in the
- root dir of the distribution.
+ root dir of the distribution (not in a bootstrap/ subdir).
  
  She runs that and then continues with bin/buildout.
  
  This generates a few warnings which she ignores.
  
  To her surprise, buildout then goes on to download a huge number of
  package eggs, even though she installed from a ZIP file (which she
  expected to already contain copies of all of these).
  
- After getting coffee, she then finally sees the script complete.
+ After getting coffee, she finally sees the script complete.
  
  She then follows instructions, runs bin/mkzopeinstance, enters instance1
  as dir and the admin user details.
  
  Finally, she starts Zope using instance1/bin/zopectl start
  
  .
  daemon process started, pid=9760
  
  Hmm, no mention of the site URL. So she looks in instance1/etc/zope.conf
  and finds that the standard location hasn't changed in the new release.
  
  Pointing a brower at http://127.0.0.1:8080/ gives her the ZMI as
  expected.
  
  </user-story>
  
  There are a couple of things that would greatly improve the user
  experience:
  
-  * the release news should include a link to the (correct) installation instructions
-  * the download page should point to the installation instructions for each release version (since these differ per version), not only the change logs
-  * the installation instructions should be updated to what's actually available on the download server
-  * the buildout instructions need to be updated to what's actually in the ZIP archive
-  * it would help, if the installation instructions included a hint on how to quickly fire up Zope for a test (it's not obvious that clicking "next" on the page will get you to those instructions and new users won't read the "Creating a buildout-based Zope instance", since they already followed the instructions on "Creating a Zope instance")
+ ?* the release news should include a link to the (correct) installation instructions
+ ?* the download page should point to the installation instructions for each release version (since these vary per version), not only the change logs
+ ?* the installation instructions should be updated to what's actually available on the download server
+ ?* the buildout instructions need to be updated to what's actually in the ZIP archive
+ ?* it would help, if the installation instructions included a hint on how to quickly fire up Zope for a test (it's not obvious that clicking "next" on the page will get you to those instructions and new users won't read the "Creating a buildout-based Zope instance", since they already followed the instructions on "Creating a Zope instance")

-- 
Poor installation user experience
https://bugs.launchpad.net/bugs/673441
You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.

From mikko at redinnovation.com  Tue Nov 23 04:14:08 2010
From: mikko at redinnovation.com (Mikko Ohtamaa)
Date: Tue, 23 Nov 2010 09:14:08 -0000
Subject: [zope2-tracker] [Bug 680403] [NEW] unrestrictedTraverse() relies on
	REQUEST
References: <20101123091409.25701.39254.malonedeb@potassium.ubuntu.com>
Message-ID: <20101123091409.25701.39254.malonedeb@potassium.ubuntu.com>

Public bug reported:

unrestrictedTraverse() relies on the presence of acquired HTTP REQUEST
object and does not gracefully handle situation when
unrestrictedTraverse() is called outside HTTP request lifecycle. If you
call getObject() for a catalog brain which does not exist from a command
line script, the following exception is produced.

Sample traceback:

  import ZPublisher, Zope
Traceback (most recent call last):
  File "<string>", line 1, in ?
  File "src/collective.mountpoint/collective/mountpoint/bin/update.py", line 31, in ?
    sys.exit(main(app))
  File "/srv/plone/saariselka/src/collective.mountpoint/collective/mountpoint/updateclient.py", line 243, in main
    exit_code = updater.updateAll()
  File "/srv/plone/saariselka/src/collective.mountpoint/collective/mountpoint/updateclient.py", line 151, in updateAll
    mountpoints = list(self.getMountPoints())
  File "/srv/plone/saariselka/src/collective.mountpoint/collective/mountpoint/updateclient.py", line 49, in getMountPoints
    return [ brain.getObject() for brain in brains ]
  File "/srv/plone/saariselka/parts/zope2/lib/python/Products/ZCatalog/CatalogBrains.py", line 86, in getObject
    target = parent.restrictedTraverse(path[-1])
  File "/srv/plone/saariselka/parts/zope2/lib/python/OFS/Traversable.py", line 301, in restrictedTraverse
    return self.unrestrictedTraverse(path, default, restricted=True)
  File "/srv/plone/saariselka/parts/zope2/lib/python/OFS/Traversable.py", line 259, in unrestrictedTraverse
    next = queryMultiAdapter((obj, self.REQUEST),
AttributeError: REQUEST

This is a corner case inside exception handler, but it should still be
able to work without REQUEST.

** Affects: zope2
     Importance: Undecided
         Status: New

-- 
unrestrictedTraverse() relies on REQUEST
https://bugs.launchpad.net/bugs/680403
You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.

From 680458 at bugs.launchpad.net  Tue Nov 23 07:12:54 2010
From: 680458 at bugs.launchpad.net (ChrisW)
Date: Tue, 23 Nov 2010 12:12:54 -0000
Subject: [zope2-tracker] [Bug 680458] [NEW] parseIndexRequest can't handle
	TaintedStrings
References: <20101123121254.25763.90402.malonedeb@gandwana.canonical.com>
Message-ID: <20101123121254.25763.90402.malonedeb@gandwana.canonical.com>

Public bug reported:

Line 83 of Products/PluginIndexes/common/util.py chokes on
ZPublisher.TaintedString.TaintedString instances rather than treating
them as strings.

I discovered this when attempting to search with a parameter that
contained an html tag.

I'm included to say that TaintedStrings should be ignored in the same way that DateTime's are.
What do others feel about this?

Regardless, this is a bug that should be addressed.

** Affects: zope2
     Importance: Undecided
         Status: New

-- 
parseIndexRequest can't handle TaintedStrings
https://bugs.launchpad.net/bugs/680458
You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.

From kevin at bud.ca  Tue Nov 23 19:24:48 2010
From: kevin at bud.ca (Kevin Teague)
Date: Wed, 24 Nov 2010 00:24:48 -0000
Subject: [zope2-tracker] [Bug 680403] Re: unrestrictedTraverse() relies on
	REQUEST
References: <20101123091409.25701.39254.malonedeb@potassium.ubuntu.com>
Message-ID: <20101124002448.6858.60621.malone@palladium.canonical.com>

You can also bump into this bug when running the upgrade profile for
PloneHelpCenter (Plone 4.0.2 with Zope 2.12.13).

-- 
unrestrictedTraverse() relies on REQUEST
https://bugs.launchpad.net/bugs/680403
You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.

From natea at jazkarta.com  Tue Nov 23 22:10:51 2010
From: natea at jazkarta.com (nateaune)
Date: Wed, 24 Nov 2010 03:10:51 -0000
Subject: [zope2-tracker] [Bug 680752] [NEW] Cannot traverse to /manage when
	running under Zope	2.13 and paster
References: <20101124031051.31770.58493.malonedeb@soybean.canonical.com>
Message-ID: <20101124031051.31770.58493.malonedeb@soybean.canonical.com>

Public bug reported:

I'm running Plone 4.0.1 under Zope 2.13 using paster, and when I go to
http://localhost:8080, I can see the welcome text "Plone is up and
running", but when I click the button to "Create a new Plone site"
(http://localhost:8080/@@plone-addsite?site_id=Plone), I get a blank
screen.

The same thing happens if I click on the "Zope Management Interface"
link (http://localhost:8080/manage). In Lynx, these links give me a 401
error.  Does this mean I need to authenticate using repoze.who?

Here is a traceback of the internal server error if I try to access http://localhost:8080/Plone
 
$ ./bin/paster serve zope2.ini
Starting server in PID 10230.
serving on 0.0.0.0:8080 view at http://127.0.0.1:8080
----------------------------------------
Exception happened during processing of request from ('24.218.26.40', 48847)
Traceback (most recent call last):
  File "/opt/wsgi/eggs/Paste-1.7.5.1-py2.6.egg/paste/httpserver.py", line 1068, in process_request_in_thread
    self.finish_request(request, client_address)
  File "/usr/lib/python2.6/SocketServer.py", line 322, in finish_request
    self.RequestHandlerClass(request, client_address, self)
  File "/usr/lib/python2.6/SocketServer.py", line 617, in __init__
    self.handle()
  File "/opt/wsgi/eggs/Paste-1.7.5.1-py2.6.egg/paste/httpserver.py", line 442, in handle
    BaseHTTPRequestHandler.handle(self)
  File "/usr/lib/python2.6/BaseHTTPServer.py", line 329, in handle
    self.handle_one_request()
  File "/opt/wsgi/eggs/Paste-1.7.5.1-py2.6.egg/paste/httpserver.py", line 437, in handle_one_request
    self.wsgi_execute()
  File "/opt/wsgi/eggs/Paste-1.7.5.1-py2.6.egg/paste/httpserver.py", line 287, in wsgi_execute
    self.wsgi_start_response)
  File "/opt/wsgi/eggs/repoze.retry-1.0-py2.6.egg/repoze/retry/__init__.py", line 90, in __call__
    app_iter = self.application(environ, replace_start_response)
  File "/opt/wsgi/eggs/repoze.tm2-1.0a5-py2.6.egg/repoze/tm/__init__.py", line 23, in __call__
    result = self.application(environ, save_status_and_headers)
  File "/opt/wsgi/eggs/Zope2-2.13.0-py2.6.egg/ZPublisher/WSGIPublisher.py", line 219, in publish_module
    response = _publish(request, 'Zope2')
  File "/opt/wsgi/eggs/Zope2-2.13.0-py2.6.egg/ZPublisher/WSGIPublisher.py", line 181, in publish
    object = request.traverse(path, validated_hook=validated_hook)
  File "/opt/wsgi/eggs/Zope2-2.13.0-py2.6.egg/ZPublisher/BaseRequest.py", line 503, in traverse
    subobject = self.traverseName(object, entry_name)
  File "/opt/wsgi/eggs/Zope2-2.13.0-py2.6.egg/ZPublisher/BaseRequest.py", line 348, in traverseName
    ob2 = adapter.publishTraverse(self, name)
  File "/usr/lib/plone40/eggs/Plone-4.0.1-py2.6.egg/Products/CMFPlone/browser/admin.py", line 39, in publishTraverse
    return DefaultPublishTraverse.publishTraverse(self, request, name)
  File "/opt/wsgi/eggs/Zope2-2.13.0-py2.6.egg/ZPublisher/BaseRequest.py", line 105, in publishTraverse
    raise e
NotFound:   <h2>Site Error</h2>
  <p>An error was encountered while publishing this resource.
  </p>
  <p><strong>Resource not found</strong></p>

  Sorry, the requested resource does not exist.<p>Check the URL and try again.</p><p><b>Resource:</b> Plone
GET</p>
  <hr noshade="noshade"/>

  <p>Troubleshooting Suggestions</p>

  <ul>
  <li>The URL may be incorrect.</li>
  <li>The parameters passed to this resource may be incorrect.</li>
  <li>A resource that this resource relies on may be
      encountering an error.</li>
  </ul>

  <p>For more detailed information about the error, please
  refer to the error log.
  </p>

  <p>If the error persists please contact the site maintainer.
  Thank you for your patience.
  </p>
----------------------------------------

Please note that I did not use the "addzope2user" script, because I
presume that the Zope admin user has already created for me with the
plone.recipe.zope2instance buildout recipe.

** Affects: zope2
     Importance: Undecided
         Status: New


** Tags: paster plone wsgi

-- 
Cannot traverse to /manage when running under Zope 2.13 and paster
https://bugs.launchpad.net/bugs/680752
You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.

From natea at jazkarta.com  Fri Nov 26 11:39:56 2010
From: natea at jazkarta.com (nateaune)
Date: Fri, 26 Nov 2010 16:39:56 -0000
Subject: [zope2-tracker] [Bug 681853] [NEW] Callback registration for
	signals ignored under	mod_wsgi
References: <20101126163956.27491.95297.malonedeb@palladium.canonical.com>
Message-ID: <20101126163956.27491.95297.malonedeb@palladium.canonical.com>

Public bug reported:

[Fri Nov 26 16:07:55 2010] [warn] mod_wsgi (pid=6747): Callback registration for signal 15 ignored.
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/parts/modwsgi/wsgi", line 227, in <module>
[Fri Nov 26 16:07:55 2010] [warn]     application = loadapp("config:/opt/wsgi/zope2.ini")
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/PasteDeploy-1.3.4-py2.6.egg/paste/deploy/loadwsgi.py", line 203, in loadapp
[Fri Nov 26 16:07:55 2010] [warn]     return loadobj(APP, uri, name=name, **kw)
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/PasteDeploy-1.3.4-py2.6.egg/paste/deploy/loadwsgi.py", line 224, in loadobj
[Fri Nov 26 16:07:55 2010] [warn]     return context.create()
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/PasteDeploy-1.3.4-py2.6.egg/paste/deploy/loadwsgi.py", line 617, in create
[Fri Nov 26 16:07:55 2010] [warn]     return self.object_type.invoke(self)
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/PasteDeploy-1.3.4-py2.6.egg/paste/deploy/loadwsgi.py", line 163, in invoke
[Fri Nov 26 16:07:55 2010] [warn]     app = context.app_context.create()
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/PasteDeploy-1.3.4-py2.6.egg/paste/deploy/loadwsgi.py", line 617, in create
[Fri Nov 26 16:07:55 2010] [warn]     return self.object_type.invoke(self)
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/PasteDeploy-1.3.4-py2.6.egg/paste/deploy/loadwsgi.py", line 109, in invoke
[Fri Nov 26 16:07:55 2010] [warn]     return fix_call(context.object, context.global_conf, **context.local_conf)
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/PasteDeploy-1.3.4-py2.6.egg/paste/deploy/util/fixtypeerror.py", line 57, in fix_call
[Fri Nov 26 16:07:55 2010] [warn]     val = callable(*args, **kw)
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/Zope2-2.13.0-py2.6.egg/Zope2/Startup/run.py", line 68, in make_wsgi_app
[Fri Nov 26 16:07:55 2010] [warn]     starter.prepare()
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/Zope2-2.13.0-py2.6.egg/Zope2/Startup/__init__.py", line 90, in prepare
[Fri Nov 26 16:07:55 2010] [warn]     self.registerSignals()
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/Zope2-2.13.0-py2.6.egg/Zope2/Startup/__init__.py", line 340, in registerSignals
[Fri Nov 26 16:07:55 2010] [warn]     self.cfg.trace])
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/Zope2-2.13.0-py2.6.egg/Signals/Signals.py", line 111, in registerZopeSignals
[Fri Nov 26 16:07:55 2010] [warn]     SignalHandler.registerHandler(SIGTERM, shutdownFastHandler)
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/Zope2-2.13.0-py2.6.egg/Signals/SignalHandler.py", line 37, in registerHandler
[Fri Nov 26 16:07:55 2010] [warn]     signal.signal(signum, self.signalHandler)
[Fri Nov 26 16:07:55 2010] [warn] mod_wsgi (pid=6747): Callback registration for signal 2 ignored.
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/parts/modwsgi/wsgi", line 227, in <module>
[Fri Nov 26 16:07:55 2010] [warn]     application = loadapp("config:/opt/wsgi/zope2.ini")
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/PasteDeploy-1.3.4-py2.6.egg/paste/deploy/loadwsgi.py", line 203, in loadapp
[Fri Nov 26 16:07:55 2010] [warn]     return loadobj(APP, uri, name=name, **kw)
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/PasteDeploy-1.3.4-py2.6.egg/paste/deploy/loadwsgi.py", line 224, in loadobj
[Fri Nov 26 16:07:55 2010] [warn]     return context.create()
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/PasteDeploy-1.3.4-py2.6.egg/paste/deploy/loadwsgi.py", line 617, in create
[Fri Nov 26 16:07:55 2010] [warn]     return self.object_type.invoke(self)
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/PasteDeploy-1.3.4-py2.6.egg/paste/deploy/loadwsgi.py", line 163, in invoke
[Fri Nov 26 16:07:55 2010] [warn]     app = context.app_context.create()
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/PasteDeploy-1.3.4-py2.6.egg/paste/deploy/loadwsgi.py", line 617, in create
[Fri Nov 26 16:07:55 2010] [warn]     return self.object_type.invoke(self)
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/PasteDeploy-1.3.4-py2.6.egg/paste/deploy/loadwsgi.py", line 109, in invoke
[Fri Nov 26 16:07:55 2010] [warn]     return fix_call(context.object, context.global_conf, **context.local_conf)
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/PasteDeploy-1.3.4-py2.6.egg/paste/deploy/util/fixtypeerror.py", line 57, in fix_call
[Fri Nov 26 16:07:55 2010] [warn]     val = callable(*args, **kw)
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/Zope2-2.13.0-py2.6.egg/Zope2/Startup/run.py", line 68, in make_wsgi_app
[Fri Nov 26 16:07:55 2010] [warn]     starter.prepare()
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/Zope2-2.13.0-py2.6.egg/Zope2/Startup/__init__.py", line 90, in prepare
[Fri Nov 26 16:07:55 2010] [warn]     self.registerSignals()
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/Zope2-2.13.0-py2.6.egg/Zope2/Startup/__init__.py", line 340, in registerSignals
[Fri Nov 26 16:07:55 2010] [warn]     self.cfg.trace])
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/Zope2-2.13.0-py2.6.egg/Signals/Signals.py", line 112, in registerZopeSignals
[Fri Nov 26 16:07:55 2010] [warn]     SignalHandler.registerHandler(SIGINT, shutdownHandler)
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/Zope2-2.13.0-py2.6.egg/Signals/SignalHandler.py", line 37, in registerHandler
[Fri Nov 26 16:07:55 2010] [warn]     signal.signal(signum, self.signalHandler)
[Fri Nov 26 16:07:55 2010] [warn] mod_wsgi (pid=6747): Callback registration for signal 1 ignored.
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/parts/modwsgi/wsgi", line 227, in <module>
[Fri Nov 26 16:07:55 2010] [warn]     application = loadapp("config:/opt/wsgi/zope2.ini")
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/PasteDeploy-1.3.4-py2.6.egg/paste/deploy/loadwsgi.py", line 203, in loadapp
[Fri Nov 26 16:07:55 2010] [warn]     return loadobj(APP, uri, name=name, **kw)
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/PasteDeploy-1.3.4-py2.6.egg/paste/deploy/loadwsgi.py", line 224, in loadobj
[Fri Nov 26 16:07:55 2010] [warn]     return context.create()
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/PasteDeploy-1.3.4-py2.6.egg/paste/deploy/loadwsgi.py", line 617, in create
[Fri Nov 26 16:07:55 2010] [warn]     return self.object_type.invoke(self)
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/PasteDeploy-1.3.4-py2.6.egg/paste/deploy/loadwsgi.py", line 163, in invoke
[Fri Nov 26 16:07:55 2010] [warn]     app = context.app_context.create()
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/PasteDeploy-1.3.4-py2.6.egg/paste/deploy/loadwsgi.py", line 617, in create
[Fri Nov 26 16:07:55 2010] [warn]     return self.object_type.invoke(self)
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/PasteDeploy-1.3.4-py2.6.egg/paste/deploy/loadwsgi.py", line 109, in invoke
[Fri Nov 26 16:07:55 2010] [warn]     return fix_call(context.object, context.global_conf, **context.local_conf)
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/PasteDeploy-1.3.4-py2.6.egg/paste/deploy/util/fixtypeerror.py", line 57, in fix_call
[Fri Nov 26 16:07:55 2010] [warn]     val = callable(*args, **kw)
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/Zope2-2.13.0-py2.6.egg/Zope2/Startup/run.py", line 68, in make_wsgi_app
[Fri Nov 26 16:07:55 2010] [warn]     starter.prepare()
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/Zope2-2.13.0-py2.6.egg/Zope2/Startup/__init__.py", line 90, in prepare
[Fri Nov 26 16:07:55 2010] [warn]     self.registerSignals()
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/Zope2-2.13.0-py2.6.egg/Zope2/Startup/__init__.py", line 340, in registerSignals
[Fri Nov 26 16:07:55 2010] [warn]     self.cfg.trace])
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/Zope2-2.13.0-py2.6.egg/Signals/Signals.py", line 114, in registerZopeSignals
[Fri Nov 26 16:07:55 2010] [warn]     SignalHandler.registerHandler(SIGHUP, restartHandler)
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/Zope2-2.13.0-py2.6.egg/Signals/SignalHandler.py", line 37, in registerHandler
[Fri Nov 26 16:07:55 2010] [warn]     signal.signal(signum, self.signalHandler)
[Fri Nov 26 16:07:55 2010] [warn] mod_wsgi (pid=6747): Callback registration for signal 10 ignored.
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/parts/modwsgi/wsgi", line 227, in <module>
[Fri Nov 26 16:07:55 2010] [warn]     application = loadapp("config:/opt/wsgi/zope2.ini")
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/PasteDeploy-1.3.4-py2.6.egg/paste/deploy/loadwsgi.py", line 203, in loadapp
[Fri Nov 26 16:07:55 2010] [warn]     return loadobj(APP, uri, name=name, **kw)
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/PasteDeploy-1.3.4-py2.6.egg/paste/deploy/loadwsgi.py", line 224, in loadobj
[Fri Nov 26 16:07:55 2010] [warn]     return context.create()
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/PasteDeploy-1.3.4-py2.6.egg/paste/deploy/loadwsgi.py", line 617, in create
[Fri Nov 26 16:07:55 2010] [warn]     return self.object_type.invoke(self)
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/PasteDeploy-1.3.4-py2.6.egg/paste/deploy/loadwsgi.py", line 163, in invoke
[Fri Nov 26 16:07:55 2010] [warn]     app = context.app_context.create()
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/PasteDeploy-1.3.4-py2.6.egg/paste/deploy/loadwsgi.py", line 617, in create
[Fri Nov 26 16:07:55 2010] [warn]     return self.object_type.invoke(self)
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/PasteDeploy-1.3.4-py2.6.egg/paste/deploy/loadwsgi.py", line 109, in invoke
[Fri Nov 26 16:07:55 2010] [warn]     return fix_call(context.object, context.global_conf, **context.local_conf)
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/PasteDeploy-1.3.4-py2.6.egg/paste/deploy/util/fixtypeerror.py", line 57, in fix_call
[Fri Nov 26 16:07:55 2010] [warn]     val = callable(*args, **kw)
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/Zope2-2.13.0-py2.6.egg/Zope2/Startup/run.py", line 68, in make_wsgi_app
[Fri Nov 26 16:07:55 2010] [warn]     starter.prepare()
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/Zope2-2.13.0-py2.6.egg/Zope2/Startup/__init__.py", line 90, in prepare
[Fri Nov 26 16:07:55 2010] [warn]     self.registerSignals()
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/Zope2-2.13.0-py2.6.egg/Zope2/Startup/__init__.py", line 340, in registerSignals
[Fri Nov 26 16:07:55 2010] [warn]     self.cfg.trace])
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/Zope2-2.13.0-py2.6.egg/Signals/Signals.py", line 115, in registerZopeSignals
[Fri Nov 26 16:07:55 2010] [warn]     SignalHandler.registerHandler(SIGUSR1, showStacks)
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/Zope2-2.13.0-py2.6.egg/Signals/SignalHandler.py", line 37, in registerHandler
[Fri Nov 26 16:07:55 2010] [warn]     signal.signal(signum, self.signalHandler)
[Fri Nov 26 16:07:55 2010] [warn] mod_wsgi (pid=6747): Callback registration for signal 12 ignored.
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/parts/modwsgi/wsgi", line 227, in <module>
[Fri Nov 26 16:07:55 2010] [warn]     application = loadapp("config:/opt/wsgi/zope2.ini")
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/PasteDeploy-1.3.4-py2.6.egg/paste/deploy/loadwsgi.py", line 203, in loadapp
[Fri Nov 26 16:07:55 2010] [warn]     return loadobj(APP, uri, name=name, **kw)
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/PasteDeploy-1.3.4-py2.6.egg/paste/deploy/loadwsgi.py", line 224, in loadobj
[Fri Nov 26 16:07:55 2010] [warn]     return context.create()
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/PasteDeploy-1.3.4-py2.6.egg/paste/deploy/loadwsgi.py", line 617, in create
[Fri Nov 26 16:07:55 2010] [warn]     return self.object_type.invoke(self)
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/PasteDeploy-1.3.4-py2.6.egg/paste/deploy/loadwsgi.py", line 163, in invoke
[Fri Nov 26 16:07:55 2010] [warn]     app = context.app_context.create()
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/PasteDeploy-1.3.4-py2.6.egg/paste/deploy/loadwsgi.py", line 617, in create
[Fri Nov 26 16:07:55 2010] [warn]     return self.object_type.invoke(self)
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/PasteDeploy-1.3.4-py2.6.egg/paste/deploy/loadwsgi.py", line 109, in invoke
[Fri Nov 26 16:07:55 2010] [warn]     return fix_call(context.object, context.global_conf, **context.local_conf)
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/PasteDeploy-1.3.4-py2.6.egg/paste/deploy/util/fixtypeerror.py", line 57, in fix_call
[Fri Nov 26 16:07:55 2010] [warn]     val = callable(*args, **kw)
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/Zope2-2.13.0-py2.6.egg/Zope2/Startup/run.py", line 68, in make_wsgi_app
[Fri Nov 26 16:07:55 2010] [warn]     starter.prepare()
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/Zope2-2.13.0-py2.6.egg/Zope2/Startup/__init__.py", line 90, in prepare
[Fri Nov 26 16:07:55 2010] [warn]     self.registerSignals()
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/Zope2-2.13.0-py2.6.egg/Zope2/Startup/__init__.py", line 340, in registerSignals
[Fri Nov 26 16:07:55 2010] [warn]     self.cfg.trace])
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/Zope2-2.13.0-py2.6.egg/Signals/Signals.py", line 116, in registerZopeSignals
[Fri Nov 26 16:07:55 2010] [warn]     SignalHandler.registerHandler(SIGUSR2, LogfileReopenHandler(loggers))
[Fri Nov 26 16:07:55 2010] [warn]   File "/opt/wsgi/eggs/Zope2-2.13.0-py2.6.egg/Signals/SignalHandler.py", line 37, in registerHandler
[Fri Nov 26 16:07:55 2010] [warn]     signal.signal(signum, self.signalHandler)

The attached patch as submitted by Reed O'Brien
(http://svn.plone.org/svn/plone/sandbox/wsgi-
plone4.1-devel/wsgi/signals.patch) seems to solve the problem and makes
these warnings go away.

** Affects: zope2
     Importance: Undecided
         Status: New


** Tags: wsgi

-- 
Callback registration for signals ignored under mod_wsgi
https://bugs.launchpad.net/bugs/681853
You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.

From natea at jazkarta.com  Fri Nov 26 11:39:56 2010
From: natea at jazkarta.com (nateaune)
Date: Fri, 26 Nov 2010 16:39:56 -0000
Subject: [zope2-tracker] [Bug 681853] Re: Callback registration for signals
	ignored under	mod_wsgi
References: <20101126163956.27491.95297.malonedeb@palladium.canonical.com>
Message-ID: <20101126163956.27491.23003.malone@palladium.canonical.com>


** Patch added: "Patch to avoid the signals warnings"
   https://bugs.launchpad.net/bugs/681853/+attachment/1746083/+files/signals.patch

-- 
Callback registration for signals ignored under mod_wsgi
https://bugs.launchpad.net/bugs/681853
You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.

From natea at jazkarta.com  Fri Nov 26 20:55:47 2010
From: natea at jazkarta.com (nateaune)
Date: Sat, 27 Nov 2010 01:55:47 -0000
Subject: [zope2-tracker] [Bug 680752] Re: Cannot traverse to /manage when
	running under Zope	2.13 and paster
References: <20101124031051.31770.58493.malonedeb@soybean.canonical.com>
Message-ID: <20101127015547.27491.2128.malone@palladium.canonical.com>

Here are the response headers when I click on the "Zope Management
Interface" link:

http://174.143.150.34:8080/manage_main

GET /manage_main HTTP/1.1
Host: 174.143.150.34:8080
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US;
rv:1.9.2.12) Gecko/20101026 Firefox/3.6.12
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: http://174.143.150.34:8080/

HTTP/1.0 401 Unauthorized
Server: PasteWSGIServer/0.5 Python/2.6.4
Date: Sat, 27 Nov 2010 01:08:08 GMT, Sat, 27 Nov 2010 01:08:08 GMT
X-Powered-By: Zope (www.zope.org), Python (www.python.org)
Content-Length: 0
Connection: close

-- 
Cannot traverse to /manage when running under Zope 2.13 and paster
https://bugs.launchpad.net/bugs/680752
You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.