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

United
Nations

 

Office for Outer Space Affairs
UN-SPIDER Knowledge Portal

  • Home
  • About Us
    • What is UN-SPIDER?
    • About UNOOSA
    • Publications
    • Jobs
    • Meet the Team
    • Contact
  • Space Application
    • Satellite Technology
    • Emergency Mechanisms
    • Recovery Mechanisms
    • International Asteroid Warning Network
    • Space Mission Planning Advisory Group
    • International Space Weather Initiative
    • Space Technologies in the UN
    • User Stories
  • Links & Resources
    • Data Applications
      • Disaster Recovery
    • Data Sources
    • GIS and Remote Sensing Software
    • Online Learning Resources
    • Institutions
  • Risks & Disasters
    • Disaster Risk Management
    • Early Warning Systems
    • Emergency and Disaster Management
    • Natural Hazards
    • Sendai Framework
    • The UN and Disaster Risk Management
    • The UN and Early Warning
    • The UN and Disaster Management
  • Advisory Support
    • Advisory Missions
    • Emergency Support
    • Virtual Advisory Support
    • Recommended Practices
    • Training Activities
    • Practical Uses
  • Network
    • Regional Support Offices
    • GP-STAR
    • MHEWS
    • IWG-SEM
  • Projects
    • SPEAR
    • SEWS-D
    • EvIDENz
    • Flood GUIDE
  • News & Events
    • News
    • Events Calendar
    • UN-SPIDER Events Archive

Breadcrumb

  • Home
  • Books
  • 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