> "PloneSVNaccessVersioning" property (added by that product).
Awesome!! Removing that property from portal_memberdata did the trick!
It's unfortunate that the PlonePAS migration script errors that were
generated (from sheet.py and property.py) weren't more verbose about the
property, as I suspect we'd have tracked this down almost immediately.
Thanks, Tomasz! I'm now running 2.5 and have opened up a whole new can
of worms trying to covert to LDAP authentication! :-)
Out of curiosity (and for future reference), what did you do to identify
the specific problem? Did you hack sheet.py and/or property.py to
provide more debug info during its migration attempt? Or some other
voodoo magic? I'm still new with zope/plone and need to improve my
debugging skills.
thanks again (and to everyone else who contributed to the thread),
-hoss
Tomasz wrote:
David Hostetler <[EMAIL PROTECTED]> writes:
Hi Tomasz,
Thanks for the reply. I, too, have had to just stick with 2.1.2 for the
time being because of this, though I am continuing to experiment with
2.5 on a test machine.
I will post back to this thread if I'm able to discover anything else
related to the acl_users/PlonePAS migration issue.
-hoss
Hello again,
No need to thank me, my pleasure.
I have solved the problem. The cause of it was
"PloneSVNaccessVersioning" property (added by that product). You just
need to get rid of it (or modify PlonePAS migration scripts to ignore
it - sheet.py and property.py in my case, though I am sure PlonePAS
guru would achieve the same thing in a much more elegant way).
Anyway - the copy of my Plone installation was successfully updated so
I am almost ready to migrate my production server to the 2.5 version
(that is after I resolve other problems ;-) ).
Cheers,
Tomasz
_______________________________________________
Setup mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/setup
