[Remember Mailing List] migration from plone3.3.2 to plone4
Бессарабова Ирина
I have custom product based on Products.remember. It provides three types extended BaseMember. О©╫After migration site content via portal_migration tool i have a clean portal_memberdata, without any members. There are no errors and seems no warnings during migration. My custom product works fine after migration. Only members data have been lost.
How make migration properly?
Versions of products:
Plone 4.0.9
Products.remember 1.9b1
Products.membrane 2.1.0
Products.FacultyStaffDirectory 3.0
Irina
--
Archive: http://www.coactivate.org/projects/remember/lists/remember/archive/2011/11/1321967074229
To unsubscribe send an email with subject "unsubscribe" to reme...@lists.coactivate.org. Please contact remember...@lists.coactivate.org for questions.
Бессарабова Ирина
22.11.11, 17:04, "О©╫О©╫О©╫О©╫О©╫О©╫О©╫О©╫О©╫О©╫О©╫ О©╫О©╫О©╫О©╫О©╫" <be...@yandex.ru>:
> To unsubscribe send an email with subject "unsubscribe" to reme...@lists.coactivate.org. О©╫Please contact remember...@lists.coactivate.org for questions.
>
>
>
--
Archive: http://www.coactivate.org/projects/remember/lists/remember/archive/2011/11/1322054538482
Maurits van Rees
> I set up a new plone 3.3.2 site with Products.remember installed, without my custom product. Then I made standart migration's actions - copy Data.fs in plone4.0.9 instance and make migration with portal_migration tool. There were no users in portal_memberdata and i was not able to login on site with an existing in plone 3.3.2 user. As I understand, all data inside the portal_memberdata were deleted during migration.
Hi Irina,
It's been a while since I have actively used Products.remember, so this
is just a guess, but I wonder if it helps to go to the membrane_tool in
the ZMI and (clear and) rebuild that catalog.
Hm, I did release Products.membrane 2.1.0 earlier this month. Oh, I see
you are already using that. In that release there have been changes
around the indexing code, mostly with collective.indexing. It should all
work fine, but maybe I and others have overlooked something that
negatively impacts migration to Plone 4. You could try 2.0.2 and see if
that works better.
Let us know if you find out something more.
Thanks,
--
Maurits van Rees http://maurits.vanrees.org/
Web App Programmer at Zest Software: http://zestsoftware.nl
"Logical thinking shows conclusively that logical thinking
is inconclusive." - My summary of Gödel, Escher, Bach
--
Archive: http://www.coactivate.org/projects/remember/lists/remember/archive/2011/11/1322215224832
Maurits van Rees
> Thanks for your reply.
> Neither reindexing membrane catalog nor pinning membrane to 2.0.2 version didn't help me.
> Seems that something happened with portal_memberdata object itself during migration. Look at plone.app.upgrade.v40.configure.zcml, lines 45-48. There is an handler=".alphas.updateToolset" and in update_toolset/toolset.xml portal_memberdata is mentioned. I have tried to comment out portal_memberdata in toolset.xml.
> Then I made migration, reinstalled membrane and remember, reindexed membrane_tool (i had to delete the broken SearchableText index before reindexing). After all, I was able to login with membrane user, create a new user and user profiles were in portal_memberdata.
> So I wonder, if it is a normal thing - not to update portal_memberdata? Are there any risks that something will be broken in future?
Hi,
I had another look. Indeed: the core Plone 4 migration apparently wants
to make sure that portal_memberdata is available as a tool and that it
is the standard MemberDataTool from PlonePAS. In Products.remember we
want it to be our own tool. What Plone does also means most properties
of portal_memberdata are removed. It probably works fine for a normal
website, but not with membrane and remember installed.
A second problem is that Products.membrane has some upgrade steps that
replace the SearchableText index of the membrane_tool catalog with a
better one. The way in which this is done, means that the new
SearchableText index is filled but the other indexes are empty.
I have fixed both problems with some upgrade steps in new releases:
Products.membrane 2.1.2:
- Fixed problem that occurs after upgrading the SearchableText index
of the membrane_tool, which happens after upgrading to membrane 2.0
or to Plone 4: the membrane_tool catalog would be empty. Now we
refresh the membrane_tool catalog when we upgrade the index. If
this has already happened to you, it should work to just go to the
membrane_tool, then the Advanced tab, and click on 'Update Catalog.'
Products.remember 1.9.1:
- Added upgrade step to restore our portal_memberdata settings, as
they get destroyed by an upgrade to Plone 4.
I hope this helps you and other migrators.
Cheers,
--
Maurits van Rees http://maurits.vanrees.org/
Web App Programmer at Zest Software: http://zestsoftware.nl
"Logical thinking shows conclusively that logical thinking
is inconclusive." - My summary of Gödel, Escher, Bach
--
Archive: http://www.coactivate.org/projects/remember/lists/remember/archive/2011/12/1324073841754