Trying to update from 8.3.7 to 8.4.4 and get the following error.

An AJAX HTTP error occurred.
HTTP Result Code: 200
Debugging information follows.
Path: /update.php/start?id=5927&op=do_nojs&op=do
StatusText: parsererror
ResponseText: Recoverable fatal error: Argument 1 passed to Drupal\Core\Entity\EntityStorageBase::loadMultiple() must be of the type array, string given, called in /home//public_html/.com/core/modules/taxonomy/src/Plugin/views/filter/TaxonomyIndexTid.php on line 396 and defined in Drupal\Core\Entity\EntityStorageBase->loadMultiple() (line 219 of /home//public_html/.com/core/lib/Drupal/Core/Entity/EntityStorageBase.php).

The update process was aborted prematurely while running update # in views_post_update_revision_metadata_fields.module. All errors have been logged.

Only 1 PENDING UPDATE Left - Fix table names for revision metadata fields.

Any help is greatly appreciated.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

tepelena created an issue. See original summary.

cilefen’s picture

Component: views.module » taxonomy.module

“All errors have been logged”

Is there anything more in the logs? The calling code is in the taxonomy module. If you are able to debug, focus on that views filter.

cilefen’s picture

Title: 8.4.0 Update process was aborted prematurely while running update » “Argument 1 passed to Drupal\Core\Entity\EntityStorageBase::loadMultiple() must be of the type array, string given” during views update
Priority: Normal » Major
cilefen’s picture

cilefen’s picture

Version: 8.4.4 » 8.5.x-dev
Status: Active » Needs review
FileSize
842 bytes
tepelena’s picture

Thanks for your help. I am relatively new to Drupal and also this site so I apologize if I opened a duplicate ticket. Wasn't sure where was the appropriate place to report this.

Still, have the problem. So far haven't had to apply any patches so this would be the first. Ideally, I would love to fix the view with the problem. But only if I could figure out which view it was. Have deleted some old views that we don't use but still the problem remains.

cilefen’s picture

Status: Needs review » Needs work

This patch is definitely wrong—do not use it. As far as I know the value passed should already be an array. Have you got a view with a taxonomy term filter?

cilefen’s picture

cilefen’s picture

There is a view on that site with a taxonomy term filter—it's the one labeled "Has taxonomy term". Somehow its "Select terms from vocabulary Tags" is saved as a string rather than a list of taxonomy term IDs. Check the filter settings when you find it.

cilefen’s picture

cilefen’s picture

Also it may help you to know that all this views update function is doing is opening and re-saving every view.

tepelena’s picture

Thanks for the tips. I will take a look at our views in the next few days and let you know if I have any luck.

Thank you.

tepelena’s picture

FileSize
91.19 KB

UPDATE

Just figured out which view was causing the problem. As Cilefen stated it was one view with Taxonomy Term Filter labeled "Has taxonomy term"

Disabled the view. Tried update.php and all went well.

Activated the view again and everything seems to be working fine.

Thank you for your help.

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

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now 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.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now 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.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

ultrabob’s picture

Status: Needs work » Fixed
cilefen’s picture

@ultrabob Can you explain please?

ultrabob’s picture

Sorry if I misread this. I came across it trying to find an answer for another issue and saw the last comment being from a year ago with the op saying that they found and solved their issue. If there is still an issue there please reopen. Sorry for the trouble.

cilefen’s picture

Oh, true.

Status: Fixed » Closed (fixed)

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

xjm’s picture

Category: Bug report » Support request