11/21/2023 0 Comments Drupal feeds taxonomy termsstatus: (boolean) Node published when set to TRUE.revision_log: (string_long) Briefly describe the changes you have made.revision_uid: (entity_reference to user) The user ID of the author of the current revision.revision_timestamp: (created) The time that the current revision was created.type: (entity_reference to node_type) Content type machine name.langcode: (language) Language code (e.g.Related article: Writing your first Drupal migration If subfields are available for the field type, you can migrate into them. For example, with the `standard` installation profile all content types will have a `body` field associated with it, but only the `article` content type has the `field_image`, and `field_tags` fields. For entities that can have multiple bundles, not all properties provided by the field storage configurations will be available in all bundles. Among other things, it adds a `user_picture` image field to the `user` entity and `body`, `comment`, `field_image`, and `field_tags` fields to the `node` entity. Again, this reference assumes that Drupal was installed using the `standard` installation profile. Attaching the fields to the entity can be done manually by the user, by a module, or by an installation profile. For one, they can only be added to fieldable entities. On the other hand, the presence of field storage configurations will depend on various factors. Base field configurations will always be available for the entity. It is worth noting that entity properties are divided in two categories: base field definitions and field storage configurations. This reference assumes that Drupal was installed using the `standard` installation profile and all modules that provide content entities are enabled. For instance, if the “Workspaces” module is installed, it will add a `workspace` property to many content entities. The modules that are enabled on the site can also affect the available properties. For example, if the entity is revisionable (e.g. The list of properties available for a content entity depend on many factors. For each property we will list its name, field type, a description, and a note if the field allows unlimited values (i.e. To make the process easier, in today’s article we are presenting a reference of properties available in content entities provided by Drupal core and some contributed modules.įor each entity we will present: the module that provides it, the class that defines it, and the available properties. Finding out which properties are available for an entity might require some Drupal development knowledge. In the case of users, you can set the username, password, timezone, etc. For example, when importing nodes you can specify the title, publication status, creation date, etc. When migrating into content entities, these define several properties that can be included in the `process` section to populate their values. In a previous article we explained the syntax used to write Drupal migrations.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |