Hello,

I am trying to update my website database but the system will not allow me. I've tried via SSH as well as by the user interface.

The error message I keep getting is:

Drupal\Component\Plugin\Exception\PluginNotFoundException: The "text_textarea_with_summary" plugin does not exist. in Drupal\Core\Plugin\DefaultPluginManager->doGetDefinition() (line 52 of /home/mywebsite/public_html/core/lib/Drupal/Component/Plugin/Discovery/DiscoveryTrait.php).

All my modules are up to date including libraries 8.x-3.x-dev. However, I was not able to update the database after updating libraries. I don't know if this is anything to do with the libraries module but I just thought I would mention it.

Without being able to update the database, I can't proceed with keeping their website updated and secure.

Any help would be gratefully appreciated.

Thank you.

m

Comments

lilbebel created an issue. See original summary.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

nagarajan kumar’s picture

I am also getting same issue when updating 8.2.8 to 8.3.1. Any one have solution for this issue. Please suggest to resolve this issue.

davemybes’s picture

Just ran into this after updating 8.2.3 to 8.3.2. It will not complete the updates due to this error.

davemybes’s picture

I got around it by commenting out a line as you can see below. I have no idea if this has any impact on anything. Everything looks OK on the site still.

diff --git a/docroot/core/modules/system/system.post_update.php b/docroot/core/modules/system/system.post_update.php
index b96d3e3..51d8459 100644
--- a/docroot/core/modules/system/system.post_update.php
+++ b/docroot/core/modules/system/system.post_update.php
@@ -43,7 +43,7 @@ function system_post_update_recalculate_configuration_entity_dependencies(&$sand
 function system_post_update_add_region_to_entity_displays() {
   $entity_save = function (EntityDisplayInterface $entity) {
     // preSave() will fill in the correct region based on the 'type'.
-    $entity->save();
+//    $entity->save();
   };
   array_map($entity_save, EntityViewDisplay::loadMultiple());
   array_map($entity_save, EntityFormDisplay::loadMultiple());

I removed the comment afterwards and no more updates were seen. The site still seems fine.

tim.plunkett’s picture

text_textarea_with_summary is provided by the Text module, which is required by Node module, not sure why that would be missing.

That update function exists to loop through all entity displays, and resave them (to add in new default values).
If you have leftover entity displays for old view modes, bundles, or entity types, that could cause this exception.

I would put debug($entity->id()); in there to help you find out which one is the problem. It would be in the form node.article.teaser

nathan tsai’s picture

Anything new? Just got this error after following this tutorial, skipping the teaser view.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

voleger’s picture

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

dimang’s picture

Like in the initial post, I'm trying to upgrade my site and I get exactly the same error. I have Drupal 8.5.9 and I'm trying to upgrade to 8.6.9. However, the same has been happening ever since 8.6.* was released, i.e. the result was the same trying to upgrade from 8.5.* to any 8.6.* version. Next, I list the plugin definitions I get, when debugging just before the exception is thrown in the DiscoveryTrait.php file (i.e. at line 51):

comment_username => array(7)
comment_default => array(7)
comment_permalink => array(6)
datetime_custom => array(6)
datetime_default => array(6)
datetime_plain => array(6)
datetime_time_ago => array(6)
file_link => array(6)
file_audio => array(7)
file_extension => array(6)
file_size => array(6)
file_uri => array(6)
file_video => array(7)
file_filemime => array(6)
file_default => array(6)
file_table => array(6)
file_rss_enclosure => array(6)
file_url_plain => array(6)
image => array(6)
image_url => array(6)
link => array(6)
link_separate => array(6)
list_default => array(6)
list_key => array(6)
entity_reference_rss_category => array(7)
text_default => array(6)
text_summary_or_trimmed => array(6)
text_trimmed => array(6)
author => array(7)
user_name => array(7)
viewsreference_formatter => array(6)
webform_entity_reference_entity_view => array(7)
webform_entity_reference_link => array(7)
webform_entity_reference_url => array(7)
basic_string => array(6)
boolean => array(6)
number_decimal => array(6)
entity_reference_entity_view => array(7)
entity_reference_entity_id => array(7)
entity_reference_label => array(7)
number_integer => array(6)
language => array(6)
email_mailto => array(6)
number_unformatted => array(6)
string => array(6)
timestamp_ago => array(6)
timestamp => array(6)
uri_link => array(6)

Expanding the text relevant ones, I see:

'text_default' => array(6)
    'field_types' => array(3)
        string(4) "text"
        string(9) "text_long"
        string(17) "text_with_summary"
    'id' => string(12) "text_default"
    'label' => Drupal\Core\StringTranslation\TranslatableMarkup(5)
        contents Available methods (14)
        protected translatedMarkup -> NULL
        protected options -> array(0)
        protected stringTranslation -> NULL
        protected string -> string(7) "Default"
        protected arguments -> array(0)
    'class' => string(60) "Drupal\text\Plugin\Field\FieldFormatter\TextDefaultFormatter"
    'provider' => string(4) "text"
        'quickedit' => array(1)
    'editor' => string(6) "editor"
'text_summary_or_trimmed' => array(6)
    'field_types' => array(1)
        string(17) "text_with_summary"
    'id' => string(23) "text_summary_or_trimmed"
    'label' => Drupal\Core\StringTranslation\TranslatableMarkup(5)
        contents Available methods (14)
        protected translatedMarkup -> NULL
        protected options -> array(0)
        protected stringTranslation -> NULL
        protected string -> string(18) "Summary or trimmed"
        protected arguments -> array(0)
    'quickedit' => array(1)
        'editor' => string(4) "form"
    'class' => string(69) "Drupal\text\Plugin\Field\FieldFormatter\TextSummaryOrTrimmedFormatter"
    'provider' => string(4) "text"
'text_trimmed' => array(6)
    'field_types' => array(3)
        string(4) "text"
        string(9) "text_long"
        string(17) "text_with_summary"
    'id' => string(12) "text_trimmed"
    'label' => Drupal\Core\StringTranslation\TranslatableMarkup(5)
        contents Available methods (14)
		protected translatedMarkup -> NULL
		protected options -> array(0)
		protected stringTranslation -> NULL
		protected string -> string(7) "Trimmed"
		protected arguments -> array(0)
	'quickedit' => array(1)
        'editor' => string(4) "form"
	'class' => string(60) "Drupal\text\Plugin\Field\FieldFormatter\TextTrimmedFormatter"
	'provider' => string(4) "text"
	

It is true that there is no plugin with id text_textarea_with_summary or textarea_with_summary in there. Does anyone have any clue about this?

dimang’s picture

Version: 8.6.x-dev » 8.5.14

Hello to all,
I 've been trying for the past few months to upgrade a site from 8.5.9 (and later from 8.5.10... until 8.5.14) to whichever version 8.6.* and today to 8.7.2, without success. In particular, the db update part (either through drush or through the web interface) displays as pending updates the following:

system module : 
  Update all entity displays that contain extra fields.
  Clear the library cache and ensure aggregate files are regenerated.
  Force cache clear for language item callback.   @see https:www.drupal.orgnode2851736
  Force cache clear to ensure aggregated JavaScript files are regenerated.   @see https:www.drupal.orgprojectdrupalissues2995570

taxonomy module : 
  Clear entity_bundle_field_definitions cache for new parent field settings.
  Clear caches due to updated taxonomy entity views data.
  Add a 'published' = TRUE filter for all Taxonomy term views and converts  existing ones that were using the 'content_translation_status' field.
  Update taxonomy terms to be revisionable.
  Remove the 'hierarchy' property from vocabularies.

views module : 
  Update exposed filter blocks label display to be disabled.
  Rebuild cache to allow placeholder texts to be translatable.

The drush updb then returns:

Post updating system                                                                                                                              [ok]
Failed: Drupal\Component\Plugin\Exception\PluginNotFoundException: The "text_textarea_with_summary" plugin does not exist. Valid plugin [error]
IDs for Drupal\Core\Field\FormatterPluginManager are: comment_username, comment_default, comment_permalink, datetime_custom, datetime_default,
datetime_plain, datetime_time_ago, file_link, file_audio, file_extension, file_size, file_uri, file_video, file_filemime, file_default,
file_table, file_rss_enclosure, file_url_plain, image, image_url, link, link_separate, list_default, list_key, entity_reference_rss_category,
text_default, text_summary_or_trimmed, text_trimmed, author, user_name, viewsreference_formatter, webform_entity_reference_entity_view,
webform_entity_reference_link, webform_entity_reference_url, basic_string, boolean, number_decimal, entity_reference_entity_view,
entity_reference_entity_id, entity_reference_label, number_integer, language, email_mailto, number_unformatted, string, timestamp_ago, timestamp, uri_link at Drupal\Core\Plugin\DefaultPluginManager->doGetDefinition() (line 53 of
./core/lib/Drupal/Component/Plugin/Discovery/DiscoveryTrait.php).
Cache rebuild complete.                                                                                                                           [ok]
Finished performing updates.                                                                                                                      [ok]

After that, trying to run the db update again, displays exactly the same pending items. Nvertheless, the site looks functional after that, but with the pending updates always there. Can anyone help with that?

In addition, a major problem is the fact, that because of the first update not being able to be applied, the others do not get to be performed as well. So, basically, the updates depend on their alphabetical order?

dimang’s picture

I finally managed to find a solution. Based on the backtrace of the error and after debugging the code, I found the problematic content type. In particular, I examined the $entity->id() referenced in the update function of the file: core/lib/Drupal/Core/Config/Entity/ConfigEntityUpdater.php (line 112):

public function update(array &$sandbox, $entity_type_id, callable $callback = NULL) {
    $storage = $this->entityTypeManager->getStorage($entity_type_id);
    $sandbox_key = 'config_entity_updater:' . $entity_type_id;
    ...
    ...
    /** @var \Drupal\Core\Config\Entity\ConfigEntityInterface $entity */
    $entities = $storage->loadMultiple(array_splice($sandbox[$sandbox_key]['entities'], 0, $this->batchSize));
    foreach ($entities as $entity) {
      if (call_user_func($callback, $entity)) {
        $entity->trustData();
        $entity->save();
      }
    }
    ...
    ...
  }

The entity was the node.faq.default, i.e., the default display of the faq content type (one of the content types I have defined). In that content type, the only field of type text with summary is the standard Body field, which however I had disabled from the default display. When I tried, I couldn't change its format in the default display. So, I reenabled it. That was it. After that, the updates were applied like a charm! No pending updates any more.

Version: 8.5.14 » 8.5.x-dev

Core issues are now filed against the dev versions where changes will be made. Document the specific release you are using in your issue comment. More information about choosing a version.

Version: 8.5.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Branches prior to 8.8.x are not supported, and Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev
larowlan’s picture

Category: Bug report » Support request
Status: Active » Closed (outdated)
Issue tags: +Bug Smash Initiative

It sounds like you're missing the text module