Drupal 8.6.1, php 7.1, MariaDB
--

composer update drupal/consumers
drush updb:

consumers module :
  8103 -   Make consumers translatable.

Do you wish to run all pending updates? (y/n): y
Placeholders must have a trailing [] if they are to be expanded with an array of values.                                         [error]
Performing consumers_update_8103                                                                                                 [ok]
Failed: Placeholders must have a trailing [] if they are to be expanded with an array of values.                                 [error]

Another example:

consumers module :
  8103 -   Make consumers translatable.

Do you wish to run all pending updates? (y/n): y
SQLSTATE[42S22]: Column not found: 1054 Unknown column 'base.owner_id' in 'field list': SELECT base.id AS id, base.uuid AS uuid, [error]
base.owner_id AS owner_id, base.label AS label, base.description AS description, base.image__target_id AS image__target_id,
base.image__alt AS image__alt, base.image__title AS image__title, base.image__width AS image__width, base.image__height AS
image__height, base.third_party AS third_party
FROM
{consumer} base; Array
(
)

After that I disabled Consumer and Consumer Images and enable them again.

There is an error while batch with translate update:

AJAX HTTP

/batch?id=76&op=do_nojs&op=do

TypeError: Argument 2 passed to Drupal\locale\LocaleConfigManager::filterOverride() must be of the type array, object given, called in /var/www/html/logi-ru1/web/core/modules/locale/src/LocaleConfigManager.php on line 636 in Drupal\locale\LocaleConfigManager->filterOverride() (line 629 of /var/www/html/logi-ru1/web/core/modules/locale/src/LocaleConfigManager.php).

Despite this, as a result both modules work.

CommentFileSizeAuthor
#3 consumers-3003277-3.patch1.02 KBdanielen

Comments

galactik created an issue. See original summary.

sipicsg’s picture

As I can see entity needs to be updated before 8103 runs.

I've used this patch with success.

diff --git a/consumers.install b/consumers.install
index 4a7b17cd3e06f30b750f3595d31d58a2642d4802..fca1fed1230224df097bf04b4347e3416130022e 100644
--- a/consumers.install
+++ b/consumers.install
@@ -52,6 +52,14 @@ function consumers_update_8103() {
   $entity_type = $entity_definition_update_manager->getEntityType('consumer');
   $last_installed_field_storage_definitions = \Drupal::service('entity.last_installed_schema.repository')->getLastInstalledFieldStorageDefinitions('consumer');

+  // Update consumer entity type
+  if (!\Drupal::database()->schema()->tableExists('consumer_field_data')) {
+      \Drupal::entityTypeManager()->clearCachedDefinitions();
+      \Drupal::entityDefinitionUpdateManager()->installEntityType(\Drupal::entityTypeManager()->getDefinition('consumer'));
+  } else {
+      return 'The \'consumer_field_data\' table already exists.';
+  }
+
   /** @var \Drupal\Core\Entity\Sql\SqlContentEntityStorage $storage */

   // Initialize the storage with the currently installed entity type and field storage definitions.

danielen’s picture

StatusFileSize
new1.02 KB

#2 nice thx, works on 8.6.4. Patch above as file

Prevents the error on updb

TypeError: Argument 2 passed to Drupal\locale\LocaleConfigManager::filterOverride() must be of the type array, object given, called in /var/www/drupal/public_html/docroot/core/modules/locale/src/LocaleConfigManager.php on line 636 in /var/www/drupal/public_html/docroot/core/modules/locale/src/LocaleConfigManager.php on line 629 #0 /var/www/drupal/public_html/docroot/core/modules/locale/src/LocaleConfigManager.php(636): Drupal\locale\LocaleConfigManager->filterOverride(Array, Object(Drupal\Core\StringTranslation\TranslatableMarkup))
danielen’s picture

Status: Active » Needs review
danrod’s picture

Thanks for the patch #2, it worked for me when doing the upgrade from 8.x-1.0 to 8.x-1.9 (upgraded Drupal Core from 8.6.3 to 8.6.13 as well).

Using the Acquia Lightning distribution.

eojthebrave’s picture

Status: Needs review » Fixed

This shouldn't be an issue any longer. In #3052959: Add an update path test and fix any bugs it finds we removed the code from consumers_update_8103 completely. Which means you won't run into this error anymore.

Thanks for reporting this error, and for the proposed solutions. Sorry it took so long to get around to actually fixing the problem.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.