Migration tab missing when LinguaPlone is installed in parallel

[cburghardt]

This is plone 4.3.2 and plone.app.multilingual 1.2.1 I have an existing LinguaPlone site and want to switch to PAM in order to get multilanguage support for an existing Dexterity type. I have installed the products but no language folders are created. I have selected German as default language and English as translatable in the language control panel. There is no migration tab. I also get the following error on my german startpage: ERROR plone.app.viewletmanager rendering of plone.contentviews in plone.contentactions fails: ('Could not adapt', <PloneSite at /special>, )

[acsr]

It is not a good idea to put three issues into one ticket.

• The issue why "no language folders are created". If you are using LinguaPlone without having the language folder approach, you should not expect to have plone.app.multilingual messing up your site, creating them! That would be a worse implementation.
• No idea what is causing the viewlet manager related issue.
• For the missing migration tab I figured out the solution for exactly the same issue yesterday:

You have still installed LinguaPlone! The documentation is missing a hint, that the new controlpanel code/template of plone.app.multilingual that is pointing to the migration template with a tab is maybe overridden by the existing installed LinguaPlone. So you can reach the migration template by typing @@lp-migration it is there but just a macro that is integrated into the main controlpanel when you call the one from plone.app.multilingual.

Try uninstalling LinguaPlone from the Add-On Controlpanel (not buildout)! and the migration shows up. So the code is still available to the migration machinery but leaves the stage for plone.app.multilingual.

Good luck!

.. todo :: Create an issue to update the docs related to uninstall LinguaPlone before migration. (but first I have to finish a successful migration myself ;-)

[cburghardt]

I'm sorry I thought those issues are related. So let's focus on the obvious part: the migration. I have followed your advice and now the migration tab shows up. Unfortunately I get an error already in the first step (relocate): Zope.SiteErrorLog 1390134641.80.825490982004 http://78.46.40.137:28080/special/relocate-content Traceback (innermost last): Module ZPublisher.Publish, line 138, in publish Module ZPublisher.mapply, line 77, in mapply Module ZPublisher.Publish, line 48, in call_object Module plone.app.multilingual.browser.migrator, line 142, in call TypeError: 'NoneType' object is not iterable

[acsr]

cburghardt: cool , so you get exactly the same issue as me (sorry, but yes you are not alone!). But I wanted to try to reproduce it before I post the issue. This would be also a seperate issue, even if it is releated (what we hopefully later know, with the excellent help of our friends ;-) )

Please be not ashamed. It is just a suggestion. I think it is better to have sepereate prominent headlines for the individual issues and then quote the other issues as related. It is important to have those issues identifyable when looking for existing tickets.

On Topic: I am now not sure if my hint to uninstall LinguaPlone is a faulty solution. Instead it is maybe a failure how plone.app.multilingual misses to take over the controlpanel and coordinates both packages in a proper way. So I now reinstall LinguaPlone and try to navigate to the @@lp-migration controlpanel by hand and see if this changes anything.

I was not able to google any hints related to "TypeError: 'NoneType' object is not iterable" together with plone.app.multilingual and migration.

[acsr]

Sugested name of the ticket: Migration tab missing when LinguaPlone is installed in parallel.

[acsr]

Update: It seems that reinstalling LinguaPlone again after plone.app.multilingual was installed fixes the issue that the migration tab is not visible (for me). The "TypeError: 'NoneType' object is not iterable" error remains in Step2 but I have custom Archetypes installed. Need to check that again with vanilla Plone 4.3. Please read carefully the instructions for Step 3.

[cburghardt]

I can confirm that the error from step2 persists. This product is unusable for me unfortunately.

[cburghardt]

If I remove the faulty line 142 from the migrator.py the migration step is executed

[jensens]

This is an old issue addressing an old version of plone.app.multilingual and probably very outdated. I close this issue now. If I am wrong please reopen the issue