Site import bug in combination with language packs

[DrCyb3r]

When using a different language than english (in my case german) and not downloading the language pack before the import, all pages are lost somewhere in the background. The english menu will have all the folders but no sites and after downloading the german language pack, the menu is empty and you would likely have to move all the pages by hand to the /de folder. Maybe consider adding an extra verification step in the import process to abort the import when the language pack is missing. Otherwise it's very confusing to users.

[IlyaKhalafi]

Check the stored page locale before moving anything. In the current 3.x importer, content can still be imported when its locale is unavailable. If no active locale matches, the original locale code is kept. Installing a language pack afterward does not remap those existing pages.

For a fresh import, install and activate the destination locale first, or include Settings in the import so it can install and map the source locales. Check the import warnings for failed downloads or unmatched locales. For a 2.x migration, also check whether your build includes 523473c, which applies the locale mapping to pages, folders, history and navigation.

For the existing import, compare the pages' stored locale with the site's active locales before changing paths. A stored de with only de-DE active can leave content outside the visible locale tree. I haven't inspected your database, so check the stored records before treating this as a display-only problem.

523473c951

[NGPixel]

Fixed by 9575873. Will land in next release.