I've inspected the trace of a similar migration. In fact I see that, in order to perform a successful Plone migration, we had to add - the Zope product UserTrack - the Plone product CMFUserTrackTool in the products sub-directory of the 3.17 installation. Since I didn' take note of that, I assume that in Plone 3.17 we were able to use the same product versions, that is: - UserTrack 1.1 - CMFUserTrackTool 1.2
Then, in Plone 3, you can use collective.portlet.usertrack in place of CMFUserTrackTool. Giovanni ----- Original Message ----- From: "Flo0502" <[email protected]> To: <[email protected]> Sent: Friday, June 11, 2010 7:48 AM Subject: Re: [Setup] Plone Upgrade 2.1.2 --> 3.17 failed > > This was my first intention too > but there is nothing like portal_activeusers. > Not in the "new ready to upgrade" nor old running site.... > > -- > View this message in context: > http://plone.293351.n2.nabble.com/Plone-Upgrade-2-1-2-3-17-failed-tp5162734p5166569.html > Sent from the Installation, Setup, Upgrades mailing list archive at > Nabble.com. > _______________________________________________ > Setup mailing list > [email protected] > http://lists.plone.org/mailman/listinfo/setup > _______________________________________________ Setup mailing list [email protected] http://lists.plone.org/mailman/listinfo/setup
