This has been requested right here earlier than; however query is closed and Drupal Development few replies don’t present enough data.
I’m attempting ot utilizing a contrib module (sitewide_alert) which offers it is personal customized entity. I’m attempting to determine how one can patch this module to make it fieldable (and the way to do that generally).
In different posts I’ve seen options so as to add Drupal Development follinwg to Drupal Development ContentEntityType annotation:
- fieldable = TRUE;
- bundle_entity_type = ??
- field_ui_base_route -> totally different options however already exists for this module pointing to Drupal Development module’s config type.
However none of these appeared to repair this.
Drupal Development full annotation for Drupal Development entity is:
* @ContentEntityType( * id = "sitewide_alert", * label = @Translation("Sitewide Alert"), * label_plural = @Translation("Sitewide Alerts"), * label_collection = @Translation("Sitewide Alerts"), * handlers = { * "storage" = "Drupalsitewide_alertSitewideAlertStorage", * "view_builder" = "DrupalCoreEntityEntityViewBuilder", * "list_builder" = "Drupalsitewide_alertSitewideAlertListBuilder", * "views_data" = "Drupalsitewide_alertEntitySitewideAlertViewsData", * "translation" = "Drupalsitewide_alertSitewideAlertTranslationHandler", * * "type" = { * "default" = "Drupalsitewide_alertFormSitewideAlertForm", * "add" = "Drupalsitewide_alertFormSitewideAlertForm", * "edit" = "Drupalsitewide_alertFormSitewideAlertForm", * "delete" = "Drupalsitewide_alertFormSitewideAlertDeleteForm", * }, * "route_provider" = { * "html" = "Drupalsitewide_alertSitewideAlertHtmlRouteProvider", * }, * "entry" = "Drupalsitewide_alertSitewideAlertAccessControlHandler", * }, * base_table = "sitewide_alert", * data_table = "sitewide_alert_field_data", * revision_table = "sitewide_alert_revision", * revision_data_table = "sitewide_alert_field_revision", * show_revision_ui = TRUE, * translatable = TRUE, * admin_permission = "administer sitewide alert entities", * entity_keys = { * "id" = "id", * "revision" = "vid", * "label" = "title", * "uuid" = "uuid", * "uid" = "user_id", * "langcode" = "langcode", * "printed" = "standing", * }, * revision_metadata_keys = { * "revision_user" = "revision_user", * "revision_created" = "revision_created", * "revision_log_message" = "revision_log", * }, * hyperlinks = { * "canonical" = "/admin/content material/sitewide_alert/{sitewide_alert}", * "add-form" = "/admin/content material/sitewide_alert/add", * "edit-form" = "/admin/content material/sitewide_alert/{sitewide_alert}/edit", * "delete-form" = "/admin/content material/sitewide_alert/{sitewide_alert}/delete", * "version-history" = "/admin/content material/sitewide_alert/{sitewide_alert}/revisions", * "revision" = "/admin/content material/sitewide_alert/{sitewide_alert}/revisions/{sitewide_alert_revision}/view", * "revision_revert" = "/admin/content material/sitewide_alert/{sitewide_alert}/revisions/{sitewide_alert_revision}/revert", * "revision_delete" = "/admin/content material/sitewide_alert/{sitewide_alert}/revisions/{sitewide_alert_revision}/delete", * "translation_revert" = "/admin/content material/sitewide_alert/{sitewide_alert}/revisions/{sitewide_alert_revision}/revert/{langcode}", * "assortment" = "/admin/content material/sitewide_alert", * }, * field_ui_base_route = "sitewide_alert.settings", * constraints = { * "ScheduledDateProvided" = {} * } * ) */ In my trial/error method I did discover I created Drupal Development Handle Fields/Show/and so forth UI for every entity I had beforehand created. So I believe that is presumably associated to not having a bundle outlined? My use case would not require making new bundles (much like Drupal Development Consumer entity).
Regardless of Drupal Development different posted solutions; my guess is modifying Drupal Development annotation shouldn’t be sufficient so as to add this performance.
