Nick (et al),
I have, for all intents and purposes, an empty site.
There's maybe 3 folders and 5 files that I created. I downloaded one
skin () but didn't install it, changed a few colours in the default
skin, and created a couple test user accounts. I think that counts as
"empty".
So I'd have to agree with you that this may be a repeatable bug in
CMFEditions.
BTW: I'm running Plone 2.5.2 right from Plone.org.
Cheers.
Fil
Nick Davis <[EMAIL PROTECTED]> wrote:
Hi Filippo,
By coincidence I was also trying to install CMFEditions today, and
got the exact same error. This was CMFEditions 1.1.2, (and I tried
earlier 1.1 in case something in 1.1.2 had broken 2.5.x compatibility)
Platform - Plone 2.5.3, Zope 2.9.8, python 2.4.4, Debian Etch.
I did this on a copy of our live site which has a long history since
2.0.x and a bunch of stuff installed. I had planned to next test this on
a fresh empty Plone site.
If you're doing this on an empty Plone site, then this sounds like a
repeatable bug in CMFEditions.
If it works on an empty Plone site, but works for neither of us in
copies of our live sites, then I was wondering about whether the
2.1->2.5.3 migration leaves something in a messed up state that
CMFEditions install can't cope with. In particular GenericSetup, though
I don't know enough about that yet.
Cheers
Nick
--
Filippo A. Salustri, Ph.D., P.Eng.
Department of Mechanical and Industrial Engineering
Ryerson University
350 Victoria St, Toronto, ON, M5B 2K3, Canada
Tel: 416/979-5000 ext 7749
Fax: 416/979-5265
Email: [EMAIL PROTECTED]
http://deseng.ryerson.ca/~fil/
_______________________________________________
Setup mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/setup
