Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
By mikeryan on
Change record status:
Published (View all published change records)
Project:
Introduced in branch:
8.3.x
Introduced in version:
8.3.2
Issue links:
Description:
In Drupal 6, custom fields were provided by the CCK module, while in Drupal 7 they are provided by the core Field API. The Drupal 8 migration system initially had plugins and classes supporting field migration from Drupal 6 incorporating "Cck" in their names - as of #2631736: Cckfield Plugins must distinguish core versions, this support is largely shared with the Drupal 7 migrations, where "Cck" is a misnomer at best. To better reflect the general nature of these plugins and classes, they are being renamed to use (only) "Field" in their names. The "Cck" names are deprecated as of Drupal 8.3.2 - please update any references to these names.
Plugins
- Any references to d6_cck_file should be replaced by d6_field_file.
- Any references to d6_cck_link should be replaced by d6_field_link.
Interfaces
Any classes implementing CckFieldPluginInterface should now implement FieldPluginInterface.
Classes
- Any references to CckFieldPluginBase should now use FieldPluginBase.
- Any references to CckMigration should now use FieldMigration.
- Any references to MigrateCckFieldPluginManager should now use MigrateFieldPluginManager.
Services
Any references to plugin.manager.migrate.cckfield should now reference plugin.manager.migrate.field.
Impacts:
Module developers
