If you want to do this, then please assign this issue to yourself, and post updates and patches in this thread (not in the main d6 upgrade thread). Volunteer(s) wanted! Thanks.

Comments

JirkaRybka’s picture

JirkaRybka commented

Linking a related issue: #55900: Split large imports / exports into multiple requests It's a highly needed one, but needing quite a bit of rewrite of category_legacy.

Also we need to check, how #59163: legacy taxonomy import sometimes has sequencing conflicts affects today's code, and whether we need to fix that, or just close the old issue.

nysander’s picture

nysander commented

any news on porting?

JirkaRybka’s picture

JirkaRybka commented
Component: Code » Category_legacy

The issue #73668: Order of enabling taxonomy wrapper affects taxonomy based modules (Simplenews, image_gallery) raises a point of auto-created taxonomies from other modules, such as Forum, Simplenews, and Image Gallery. These have something else than "taxonomy" in the "module" DB-table column, and possibly the vid/tid may be linked to some further data. We probably need to check that such vocabularies are available for import too, but at the same time issue a warning about possible breakage if the data [possibly] joins to something else in other modules. Forum does this, and it's already special-cased in the existing 5.x code, but we can't do the same for every single module out there (not beyond core, IMO).