Write D6 migration for menu links [#2212211]

Comment #1

chx CreditAttribution: chx commented 6 March 2014 at 15:50

This is waiting on menu links becoming content entities.

Log in or register to post comments

Comment #2

chx CreditAttribution: chx commented 6 March 2014 at 15:50

#1842858: [PP-1] Convert menu links to the new Entity Field API

Log in or register to post comments

Comment #3

eliza411 CreditAttribution: eliza411 commented 6 March 2014 at 18:06

Parent issue:

» #1842858: [PP-1] Convert menu links to the new Entity Field API

Do we have other issues that are postponed on core? It seems like a good idea to tag or group them so they can be worked on as soon as their parent is ready and/or the beta is ready.

Log in or register to post comments

Comment #4

penyaskito

he/him

Spanish

🧑🏽‍🌾Seville 💃, Andalusia 🇪🇸, UTC+2 🇪🇺

CreditAttribution: penyaskito commented 12 May 2014 at 00:17

Is this a dupe of #2178703: Migrate D6 menu links?

Log in or register to post comments

Comment #5

chx CreditAttribution: chx commented 12 May 2014 at 06:22

Status:

Active

» Closed (duplicate)

Yes.

Log in or register to post comments

Comment #6

jp.stacey CreditAttribution: jp.stacey commented 29 June 2014 at 11:32

Should this issue actually be a child of #2221733: [Meta] Test individual D6 > D8 content migrations. and #1842858: [PP-1] Convert menu links to the new Entity Field API be a related issue instead? It seems weird for its parent to be closed (also I think 2221733 is trying to marshal testing of all D6 migration in core into one checklist.)