After posting this error yesterday and getting no reply, I decided to verify that it was not due to something left over from a previous installation. I dumped my entire installation into another directory and untarred Zope-2.0.0a2 into an empty directory. Then did the following: $ python w_pcgi.py $ ./start Upon entering the root manage view, the first thing I noticed was the QuickStart which I had never seen before. I then went to Control_Panel/Database/manage_cacheParameters and no error. Next I tried Control_Panel/Database/manage_cacheGC and again no error. At that point I thought I had solved the problem and backed out to Control_Panel when I noticed there was no restart button. Remembering that the Restart button was part of ZServer, I shutdown the Zope process and went back to look at the start file. There I changed python serve.py to python z2.py and restarted. Now upon entering the root manage view, the first thing I noticed was QuickStart was no longer visible. I proceeded to the Control_Panel/Database/manage_cacheParameters and there was the TypeError exception again. I backed out and tried Control_Panel/Database/manage_cacheCG and again there was the TypeError exception. Here again is the traceback output which is exactly the same for both cases. exceptions.TypeError Traceback (innermost last): File /opt/www/zope/lib/python/ZPublisher/Publish.py, line 255, in publish_module File /opt/www/zope/lib/python/ZPublisher/Publish.py, line 161, in publish File /opt/www/zope/lib/python/ZPublisher/mapply.py, line 154, in mapply (Object: cacheParameters) File /opt/www/zope/lib/python/ZPublisher/Publish.py, line 98, in call_object (Object: cacheParameters) File /opt/www/zope/lib/python/App/special_dtml.py, line 120, in __call__ (Object: cacheParameters) File /opt/www/zope/lib/python/DocumentTemplate/DT_String.py, line 514, in __call__ (Object: cacheParameters) File /opt/www/zope/lib/python/App/CacheManager.py, line 109, in cache_length (Object: Control_Panel) File /opt/www/zope/lib/python/ZODB/DB.py, line 272, in cacheSize TypeError: too many arguments; expected 1, got 2 The problem starts in App/CacheManager in cache_length() where it determines we are not using BoboPOS2 and tries to return db.cacheSize(). When using serve.py, we are using BoboPOS2 and thus the error in ZORB/DB.py is not encountered. At this point, I have no idea how to go about solving the problem. I have looked at the code and cannot immediately find anything wrong with it, but as I stated before, I have only been using Python for a few months so I may be overlooking something. Also, why does QuickStart show up using BoboPOS2 and not with ZORB3? Is anyone else using ZServer and getting these errors or am I the only one who seems to have this problem? Regards, Jarrod Kinsley
J Kinsley wrote At this point, I have no idea how to go about solving the problem. I have looked at the code and cannot immediately find anything wrong with it, but as I stated before, I have only been using Python for a few months so I may be overlooking something.
Also, why does QuickStart show up using BoboPOS2 and not with ZORB3?
I believe that the sample starting database shipped for ZODB3 is missing a lot of stuff, including QuickStart (and index_html :). It's possible that it's Control Panel hasn't been updated - did you submit it as a bug to the Collector? (www.zope.org/Collector) Anthony
On Wed, 16 Jun 1999, Anthony Baxter wrote:
Date: Wed, 16 Jun 1999 19:40:38 +1000 From: Anthony Baxter <anthony@interlink.com.au> To: J Kinsley <jkinsley@horus.bticc.net> Cc: zope@zope.org Subject: Re: [Zope] ZORB3 Errors
<snip>
Also, why does QuickStart show up using BoboPOS2 and not with ZORB3?
I believe that the sample starting database shipped for ZODB3 is missing a lot of stuff, including QuickStart (and index_html :). It's possible that it's Control Panel hasn't been updated - did you submit it as a bug to the Collector? (www.zope.org/Collector)
I have submitted a bug report for the TypeError, but not for the missing QuickStart since it is not a major error.
Anthony
J Kinsley wrote:
After posting this error yesterday and getting no reply,
I just replied.
I decided to verify that it was not due to something left over from a previous installation. I dumped my entire installation into another directory and untarred Zope-2.0.0a2 into an empty directory. Then did the following:
$ python w_pcgi.py $ ./start
Note that this used ZODB 2 unless you edit your PCGI resource file, Zope.cgi. To use ZODB 3, you need to publish module Zope. Zope.cgi publishes module Main.
Upon entering the root manage view, the first thing I noticed was the QuickStart which I had never seen before. I then went to Control_Panel/Database/manage_cacheParameters and no error. Next I tried Control_Panel/Database/manage_cacheGC and again no error. At that point I thought I had solved the problem and backed out to Control_Panel when I noticed there was no restart button. Remembering that the Restart button was part of ZServer, I shutdown the Zope process and went back to look at the start file. There I changed python serve.py to python z2.py and restarted.
Now upon entering the root manage view, the first thing I noticed was QuickStart was no longer visible. I proceeded to the Control_Panel/Database/manage_cacheParameters and there was the TypeError exception again. I backed out and tried Control_Panel/Database/manage_cacheCG and again there was the TypeError exception.
(snip) I've checked in fixes for these. The fix in available via the public CVS and will be in alpha 3 which I hope to make available Friday or Monday.
Also, why does QuickStart show up using BoboPOS2 and not with ZORB3?
Because we haven't gotten around to converting the default content to ZODB 3 format yet. Jim -- Jim Fulton mailto:jim@digicool.com Python Powered! Technical Director (888) 344-4332 http://www.python.org Digital Creations http://www.digicool.com http://www.zope.org Under US Code Title 47, Sec.227(b)(1)(C), Sec.227(a)(2)(B) This email address may not be added to any commercial mail list with out my permission. Violation of my privacy with advertising or SPAM will result in a suit for a MINIMUM of $500 damages/incident, $1500 for repeats.
participants (3)
-
Anthony Baxter -
J Kinsley -
Jim Fulton