Watch for http://127.0.0.1 vs. http://localhost. The two are not the same from Mozilla's perspective. I spent hours trying to troubleshoot a non-existent problem all because I was referencing 127.0.0.1 in the code and localhost in the browser. Mozilla would throw an exception: "Permission denied to call method XMLHttpRequest.open" whenever I tried do an xmlrpc request from Mozilla using the jsolait libraries. The same code had worked previously without monkeying around with signed.applets.codebase_principal_support but was failing because I was pointing the browser at localhost!
I noticed my IBM ThinPad A21p running Mandrake 9.1 was taking an inordinate amount time to boot so I paid attention to where it was stuck. The machine seemed to have hung at the "Loading sound module" step of the boot process so I just powered off and restarted the machine. This time, I got a notice that the filesystem needed checking but when I typed "Y", it complained that there was no such file as e2fsck.hda1, or something to that effect. Mandrake suggested that I should run e2fsck -b 8193 /dev/hda1. I did that but this time it responded:
I was having trouble compiling psycopg. It would link against the version of Python that was installed via RPM on my Mandrake 9.1 box, which was version 2.2.3. I knew I had to link against the latest version of Python that I had installed from source. At the recent PyGTA meeting I attended, I asked if anyone knew about compiling psycopg from source. No one volunteered an answer but the fellow sitting next to me was looking over my shoulder as I attempted various things. He noticed that I had not specified where the python executable was but had only specified the version.
Though I have been using Python for a few years, I had never managed to get to a PyGTA PyGTA (Greater Toronto Area Python User Group) meeting until last Tuesday night. Brian Sullivan of Courses by Wire was the featured speaker. He presented his company's Zope based e-learning application and talked about not just the technical details of the application but also about the business aspects of the e-learning vertical market.
Installing Nucleus was quite easy.
1. Downloaded the zip file.
2. Unzipped file in public_html.
3. Renamed nucleus directory to blog.
4. Followed the directions in the on-line manual.
... and here we are.