History for BugReports

??changed:
-
  For Zope version 2.2.0, you need to install these two patches to     ../lib/python/ZPublisher/Client.py::
  
      #h.connect((self.host, self.port))
      h.connect(self.host, self.port)
      
      #sock.connect((self.host,self.port))
      sock.connect(self.host,self.port)

  See collector item #1480 http://classic.zope.org:8080/Collector/1480/view

-- Loren (lstaffor)
2000-08-04

<hr>

  Zope 2.2.0 on Linux - Zope "hangs" once ZScheduler is installed.
 
  After untaring the zscheduler distribution and restarting zope - I can't retrieve any web pages from my zope server.   The browser never gets a response.  If I delete the ZScheduler product - Zope starts to work again.

--Roman [email protected]

<hr>



  In versions of Zope prior to 2.2.0b2,
  if the webserver of the host machine listens on a port other than 80, 
  a "reschedule" operation looses the port number from the URL in the catalog;
  the rescheduled event cannot then be triggered. 
  This is due to a bug in ZPublisher/Client.py module
  of versions of Zope prior to 2.2.0b2.
  
  Workaround for older versions: 
  Patch Client.py as described in CHANGES.txt
  
  The problem is documented in the Zope bug collector:
  http://classic.zope.org:8080/Collector/1112/view

-- Loren
2000/06/22

<hr>

> When I un-tar the thing it says: decompression OK, trailing garbage
ignored.

You can safely ignore this message. I use MKS Tools on Win98 to make the tarball. Apparently puts something strange in the file. 

-- Loren 2000/03/11

<hr>

Version 0.0.3 is known to cause Zope to "freeze" on Linux and Solaris. 
Works on Win98, though.

-- Loren 
2000/03/15

I just successfully ran Version 0.0.5 
on Linux and Solaris as well as Win98. 

-- Loren 2000/06/14

<hr>

The following message appears in the log::

  currentThread(): no current thread for -1558413

As far as I can tell, this is advisory, and does not indicate a problem.

-- Loren 2000/06/13

<hr>