February 1999 - Zope

RE: [Zope] Problems requesting SQL date fields
by Michel Pelletier 27 Feb '99

27 Feb '99

> -----Original Message----- > From: Alexander Schad [mailto:ags@beehive.de] > Sent: Thursday, February 25, 1999 9:55 AM > To: zope(a)zope.org > Subject: [Zope] Problems requesting SQL date fields > > > I have connected my zope server with a SQL-Server but when > i'm requesting > a date field a get an error. Can anybody tell me what might > went wrong? > Maybe. This is not even close to enough information for us to consider looking at this problem. Please send a *detailed* description of your problem. To help you we need to know what version Zope, what kind and version of SQL server, if you can reproduce the problem reliably and most importantly we need the traceback that your error is producing. -Michel > Alex > > > _______________________________________________ > Zope maillist - Zope(a)zope.org > http://www.zope.org/mailman/listinfo/zope >

2 1

Re: [Zope] AW: [Zope] HELP NEEDED - EXTREMELY URGENT (Zope on NT4 SP4)
by Robin Dunn 27 Feb '99

27 Feb '99

> >Sure I will, propably within the next week. I never compiled Python >extensions myself, are there any instructions or makefiles in the >source distribution, or should I have a look into Python's E&E >manual? I have made a set of scripts for win32 that build Zope from the source distribution just like the provided scripts do on Unix systems. I just used them today on two different NT systems to build Zope 1.10.2. Go to http://starship.python.net/crew/robind/#zope to get the zip file and follow the instructions on the page. Since these scripts create makefiles and use nmake, the only requirement is having the MS VC++ 5.0 or 6.0 command-line tools installed and properly configured (with environment variables and such, use the vcvars32.bat or whatever that the VC++ install creates.) -- Robin Dunn robin(a)AllDunn.com http://AllDunn.com/robin/ http://AllDunn.com/wxPython/ Check it out! Try http://AllDunn.com/laughworks/ for a good laugh.

1 0

Zope and webreview
by Ken Manheimer 27 Feb '99

27 Feb '99

Too cool - it looks like amos will have a Zope article in WebReview, thanks to timely mention of Zope by kevin dangoor to the editors. It's amazing how a few words at the right time can make a difference in *spreading* the word! Please, everyone keep your eyes open for such opportunities - this is clearly as situation where the more is the merrier. Thanks kevin - well done! ken klm(a)digicool.com

1 0

Possible Bug Report: Corrected Broken Products do not appear righ t any more t any more
by Stefan Franke 26 Feb '99

26 Feb '99

It seems a broken product that is corrected still is shown as broken in the products folder on next restart along with the old traceback. This appeares first to me first with 10.2.1 on Win NT4. If someone could pls confirm this I'll add it to the bug tracking list - just add a typo somewhere in ExternalMethod.py, start Zope, remove it, and start over. Stefan

3 2

AW: [Zope] HELP NEEDED - EXTREMELY URGENT (Zope on NT4 SP4)
by Stefan Franke 26 Feb '99

26 Feb '99

Jim Fulton wrote: > Stefan Franke wrote: >> Ok today I checked that my problem is definitely caused by the >> Win NT SP4. > Wow. How did you determine this. Easy... I was in the lucky position to check it with two identical servers in the server pool of out customer (the public administration of the city of cologne). They were exact clones WRT Hardware, and SW either, due to M$'s Software Management System), and differed only in the OS patch version. > I'm not sure when we'll do this. If compiling with a newer > compiler fixes the problem, please let us know. Sure I will, propably within the next week. I never compiled Python extensions myself, are there any instructions or makefiles in the source distribution, or should I have a look into Python's E&E manual? Stefan

3 2

DISCUSS: Import from the web
by Paul Everitt 26 Feb '99

26 Feb '99

I need you folks to help us figure out how to add a sweet little feature: import from the web. Scenario: you work from home on a bunch of information in a Zope folder, like documents, images, Z Tables, etc. You get into work and want to blast it onto your remote Zope-based website. With Zope 1.10.2, you now have an interface to do this: you first export your folder on your laptop, move the export file to the filesystem of your webserver, and import the folder on the webserver. There are certainly some scripting things you could do in Python to make this a bit more seamless. But wouldn't it be nice if you could tell the two Zopes to swap information directly? To date we haven't done this for security reasons. Since export files are series of records containing pickles, the unpickler could be tricked into doing something unpleasant. While this could still happen under the current scheme, at least you know the person was trusted enough to log into the OS and be allowed to write to the directory. Thus, the current import/export scheme isn't about preventing damage, it (like External Methods) is about proving someone is trustworthy. Let's say we leave off the table right now consideration of making the import more immune to hijinx. Let's also leave off the table related issues (like synchronization or replication conflicts). Let's just ask the question: "Can we make import-from-the-network have as acceptible a level of trust as the filesystem?" Here are some brainstorm ideas: 1) Make the import a pull rather than a push. Instead of pushing the data from your computer into a remote Zope, you go to the remote Zope and put in the URL to your local Zope. 2) Turn import from the web off by default but have a knob to turn it on. 3) Reading directly from a Zope as it outputs an export means you're less likely to get a hacked pickle. 4) Have a shared key system, then rotor the export file (this is what we do on the unreleased Zope Network Client software). That is, wrap the data in an envelope. Of course there is still the ultimate question: is this a compelling feature? --Paul Paul Everitt Digital Creations paul(a)digicool.com 540.371.6909

4 3

Gratuitous password reminders a few days ago...
by Ken Manheimer 26 Feb '99

26 Feb '99

As many of you must have noticed, a few days ago a batch of password reminders were sent out by www.zope.org to you all. This batch was not the regularly scheduled one - in fact, it was spectacularly off-schedule - a few of you may have noticed that the reminders were dated Feb 6, 2036. The www.zope.org machine has been having some clock drift problems. We set up a frequent rdate synchronization with one of the NIST standard clocks to correct for it until we could concentrate on getting the clock problem repaired (we have enough fires besides), but either the clock drifted suddenly enough, or the rdate/standard clock sustained some terrible fluke, that a bad time slipped by. In any case, in its addled state the machine apparently decided it's time to send out the notices. The regular time for sending the notices is the first hour of the first day of the month. I will disable that for this upcoming month, and not trust it to a automatically scheduled routine until we track down this problem. Anyway, sorry about the gratuituous messages... Ken Manheimer klm(a)digicool.com

1 0

Summary of my Problems / Solutions upgrading from 1.9 to 2.0
by solberg＠platinum.com 26 Feb '99

26 Feb '99

Hello, I thought that a summary might help others that might be running into the same problem. The task: Upgrade my 1.9 test Zope to 1.10 and move it to Apache. The Problems: 1) I had Apache 1.2.6 and didn't want to lock down the zope.cgi program for all users. --- Solved this by upgrading to 1.3.3. Briefly hit a problem due to not having the ExecCGI option on the script directory. Applied the rewrite rule without much difficulty. (Hint: Don't get the binary version of apache. We needed the source to do the mod_rewrite adjustment.) 2) After having Zope running with the default database, and attempting to migrate my 1.9 database (I'll discuss this one later), we went home for the night and came back the next morning. At this point Zope wouldn't come up anymore. We could tell that the machine had been restarted. --- This one sent us on a wild goose chase. We tried the suggestions from Jeff Bauer and setup some pcgi tests. Unfortunately, all of those tests seem to refer to cgi_module_publisher or something like that. The tests all showed that this module was not found. Apparently, these tests are all out of date. The simple solution was to delete the pcgi.* files from the var directory. This allowed Zope to come back up. We decided to create a system startup script that removes these files and also loads a web page using lynx -dump. This allows us to get the pcgi process started and to test that everything is working. I volunteered to have my pager paged when the tests fail. : ( 3) We couldn't get the 1.9 database to work when we tried it in 1.10. We followed the instructions on shutting the processes down and copying the Data.bbb file. We always got a system error message. --- Within the source of the message was a traceback to the cPickle program and something about "G". Jim Fulton responded to my plea in the mailing list informing me that I needed to get cPickle enabled for binary floats. To do this, we went to the Python Modules directory and edited Setup. (By the way, we had just installed 1.5.1 of Python from Python.org.) In Setup, near the bottom, there is a line for cPickle. We added the -DFORMAT_1_3 to this line and rebuilt Python (make clean, make, make install, make test). After this our 1.9 database worked with our new 1.10 install. Thanks a bunch to Jim. I hope this helps out. Good Luck and thanks for all the great support, John Solberg

1 0

RE: [Zope] [ZOPE.ORG] suggestion for download area (replacement)
by Paul Everitt 26 Feb '99

26 Feb '99

Philip wrote: > On the download page it would be nice to have an explination > of what the > software is for. Ditto for contributed software. Funny you should mention that. Two hours I scheduled a chat with Ken to talk about restructuring the package information on zope.org. Good timing! If any of you have ideas on how you'd like it to be, whip up some HTML and send it to me. > For example, how do I find out what confera will do without > installing it > and spending a week playing with it? That is what I did with > Zope. It is > not the best way to sell software, even free stuff! Funny thing is that I don't think you can actuall find Confera on the site right now if you don't know the URL. But you're right, everything should have a Summary. Ahh, but then we slip instantly into a metadata discussion: "Is it Summary or Description? We ought to use a standard set of metadata, like [RPM, IAFA, Trove, Dublin Core, ...]" For once I'd like an answer without ten questions attached :^) > Maybe there could be a second link to a document explaining what the > component does. (It could be writen by the contributer of the > software, so > it wouldn't be much work for the zope.org webmaster.) That would be > especially great in the contributed software. What are > XMLConfig, MySQL > Input Wizard, slashdot.py anyways! They sound interesting but > I am still > learning 10 other things, I need to know what they do first! Yup. > This is the INFORMATION AGE, afterall! Oh, that's what you call the stuff I'm drowning in? :^) --Paul

1 0

RE: [Zope] Splitting the Zope mailling
by Michel Pelletier 26 Feb '99

26 Feb '99

> -----Original Message----- > From: Michael Bernstein [mailto:mbernstein@profitscape.net] > > Ok, after a bit more thought, I came up with a fourth list: > zope-bugs(a)zope.org > Bugs should be reported to the Bug Collector, not to a mail list. I think I might understand your reasoning, but it is reasonable enough for someone to post a message to the zope@ list to find out if their problem is their fault or a bug, and then to report it to the Collector. -Michel (Keep the sugestions coming) > Michael Bernstein. > > _______________________________________________ > Zope maillist - Zope(a)zope.org > http://www.zope.org/mailman/listinfo/zope >

3 3