Skip to main content
  • English
  • Español
  • Français

United
Nations

 

Office for Outer Space Affairs
UN-SPIDER Knowledge Portal

  • Inicio
  • Sobre nosotros
    • Sobre ONU-SPIDER
    • Acerca de UNOOSA
    • Publicaciones
    • Ofertas de trabajo
    • Conozca el Equipo
    • Contacto
  • Aplicación Espacial
    • Guías Tecnológicas
    • Mecanismos de Emergencia
    • Mecanismos de Recuperación
    • Red Internacional de Alerta de Asteroides
    • Grupo Asesor para la Planificación de Misiones Espaciales
    • Iniciativa Internacional sobre Meteorología Espacial
    • Tecnologías Espaciales en la ONU
    • Historias de Usuarios
  • Enlaces y Recursos
    • Aplicación de datos del mes
      • Disaster Recovery
    • Fuentes de Datos
    • SIG y Software de Percepción Remota
    • Recursos de capacitación en línea
    • Instituciones
  • Riesgos y Desastres
    • Gestión del Riesgo de Desastres
    • Alerta temprana
    • Gestión de Desastres y Emergencias
    • Amenazas Naturales
    • El Proceso de la Reducción de Desastres Post-2015
    • La ONU y la Gestión del Riesgo de Desastres
    • La ONU y Alerta Temprana
    • La ONU y la Gestión de Desastres
  • Asesoría
    • Misiones de Asesoría
    • Apoyo en caso de Emergencia
    • Asesoría Virtual
    • Prácticas Recomendadas
    • Actividades de Entrenamiento
    • Usos Prácticos
  • Redes
    • Oficinas Regionales de Apoyo
    • GP-STAR
    • IN-MHEWS
    • IWG-SEM
  • Proyectos
    • SPEAR
    • FOSAT-S
    • EvIDENz
    • Flood GUIDE
    • CommonSpace Initiative
  • Noticias y Eventos
    • Noticias
    • Eventos
    • Eventos pasados

Breadcrumb

  • Home
  • Get Rid of Error Messages Regarding Non Existing Fields
  • Get rid of error messages regarding non existing fields

Get rid of error messages regarding non existing fields

By admin_wla | Sun, 17 Oct 2021 - 17:36

[error]  A non-existent config entity name returned by FieldStorageConfigInterface::getBundles(): entity type: comment, bundle: comment_node_internal_information, field name: comment_body
[error]  A non-existent config entity name returned by FieldStorageConfigInterface::getBundles(): entity type: comment, bundle: comment_node_recommendedpractices_details, field name: comment_body
[error]  A non-existent config entity name returned by FieldStorageConfigInterface::getBundles(): entity type: comment, bundle: comment_node_recommendedpractices_stepbystep, field name: comment_body
[error]  A non-existent config entity name returned by FieldStorageConfigInterface::getBundles(): entity type: comment, bundle: comment_node_recommended_practices, field name: comment_body
[error]  A non-existent config entity name returned by FieldStorageConfigInterface::getBundles(): entity type: comment, bundle: comment_node_glidenumber, field name: comment_body
[error]  A non-existent config entity name returned by FieldStorageConfigInterface::getBundles(): entity type: comment, bundle: comment_node_geo_information_resource, field name: comment_body
[error]  A non-existent config entity name returned by FieldStorageConfigInterface::getBundles(): entity type: comment, bundle: comment_node_projects, field name: comment_body
[error]  A non-existent config entity name returned by FieldStorageConfigInterface::getBundles(): entity type: comment, bundle: comment_node_un_spider_training_activity, field name: comment_body
[error]  A non-existent config entity name returned by FieldStorageConfigInterface::getBundles(): entity type: node, bundle: glidenumber, field name: body
[error]  A non-existent config entity name returned by FieldStorageConfigInterface::getBundles(): entity type: node, bundle: projects, field name: body
[error]  A non-existent config entity name returned by FieldStorageConfigInterface::getBundles(): entity type: node, bundle: glidenumber, field name: upload
[error]  A non-existent config entity name returned by FieldStorageConfigInterface::getBundles(): entity type: node, bundle: projects, field name: upload

The installation shows error messages regarding no longer existing fields which partially existed back in the Drupal 6 version of spider and are long gone. The Update processes from Drupal 6 to Drupal 7 to Drupal 8 however saved this old information in the database. The removal of those definitions can only be done via programming (see https://codimth.com/blog/web/drupal/how-fix-non-existent-config-entity-name-drupal-8-9, example 3).

By using update hooks in the custom module "practical_use" these errors could be removed one by one.

 

Documentation
0
0
wla
  • Printer-friendly version

Footer menu

  • Contact
  • Terms of Use

User account menu

  • Log in