#2 — Migration profile from LinguaPlone

by jean-mat Grimaldi — last modified Feb 12, 2010 08:10 AM
State Confirmed
Version:
—
Area Functionality
Issue type Feature
Severity Medium
Submitted by jean-mat Grimaldi
Submitted on Feb 11, 2010
Responsible Simon Kaeser
Target release:
—
Return to tracker
A GS migration profile for contents that were using LinguaPlone (and also untranslated contents) could be useful.
Steps to reproduce:
Install raptus.multilanguagefields

Make some fields translatable for all standard Content types (Title, text and description), using raptus.multilanguageplone or using another method in your own package.

Install your package or raptus.multilanguageplone in a fresh Plone instance.

The homepage is empty, idem for the news and events folders.
Added by Simon Kaeser on Feb 12, 2010 08:10 AM
Issue state: Unconfirmed → Confirmed
Responsible manager: (UNASSIGNED) → simu
For untranslated contents this should be not a big deal. To migrate from a LinguaPlone site could be pretty complex, or what do you think?

No responses can be added.