Updated my development site from 8.5.6 to 8.6.0
on any page, I see:

InvalidArgumentException: Field reusable is unknown.
in Drupal\Core\Entity\ContentEntityBase->getTranslatedField()
(line 586 of core/lib/Drupal/Core/Entity/ContentEntityBase.php)

searching around -- not sure if this is a related issue?
https://www.drupal.org/project/business_rules/issues/2973664

switched back to 8.5.6 -- things seem normal again.

Steve

Comments

saweyer created an issue. See original summary.

cilefen’s picture

cilefen commented
Priority: Normal » Major
Issue tags: +8.6.0 update
larowlan’s picture

larowlan
Location 🇦🇺🏝.au GMT+10
commented
Category: Bug report » Support request

Did you run update.php?

saweyer’s picture

saweyer commented

just displaying any admin page generated error,
so there was no obvious way to run update.php
or check system status or logs.

saweyer’s picture

saweyer commented

I tried installing 8.6.0 again.
then running update.php from address bar, but got same error.

after trying a few times, I finally got update.php to run and install its db changes.

kartagis’s picture

kartagis
Primary language Turkish
Location Istanbul
commented

In my case, I had to run drush cr because update.php threw permission error after clicking Continue.

thoreauinsf’s picture

thoreauinsf commented

I get this exact same error when i upgrade to Drupal 8.6

No amount of drush cr or run updates helps.

Anonymous’s picture

Anonymous (not verified) commented

I get this exact same error when i upgrade to Drupal 8.6

Could you help me please ?

switched back to 8.5.4 -- things seem normal again.

saweyer’s picture

saweyer commented

since I had some open-ended time (in case I needed to revert), I decided to try upgrading again.

after upgrading to 8.6.0, I was able to "Run Updates" via Admin Toolbar interface
(the 8.5.6 version of Maintenance page still in browser).

however, the updates page displays the following errors:
Notice: Undefined index: #summary_attributes in template_preprocess_details()
(line 244 of core/includes/form.inc).
Warning: Invalid argument supplied for foreach() in Drupal\Core\Template\Attribute->__construct()
(line 81 of core/lib/Drupal/Core/Template/Attribute.php).

(note: I also updated pathauto and token modules at same time, and one of those also had a db update,
so maybe that's related -- I don't recall seeing those errors a few days ago when 1st trying to update only 8.6.0)

I then proceeded to apply the updates -- success. (Phew!)

Steve

cilefen’s picture

cilefen commented
Related issues: +#2998096: Unknown column 'block_content_field_data.reusable' after upgrading from 8.5.7 to 8.6.0
morten-h’s picture

morten-h commented

I had the exact same issue when upgrading from 8.5.6 to 8.6.1.

After reading through every sort of hint of a solution i found that this solved it for me:

- Be logged in before updating and keep the window open
- Update the site / push the new files
- Attempt to flush the cache with the direct link from the window you kept open
- Run update.php by using the direct link (while the rest of the site has the WSOD) or do it from the window you kept open.

I had 24 updates waiting and after running update.php the site was back in business with no errors or issues.

I was lucky that I could just rollback to the working 8.5.6 version easily tho, if you can't do that i'm not sure how to solve it. The first time trying to update I could not run update.php because i hadn't been logged in before updating.

Not sure if you can run it when setting $settings['update_free_access'] = TRUE in settings.php.
Maybe that's worth a try.

morrisem’s picture

morrisem commented

Following the suggestions from others, I solved this problem AFTER installing 8.6.1 WITHOUT being logged in before updating as follows:

1. Use phpmyadmin to truncate all files beginning with "cache".
2. Edit settings.php to change $settings['update_free_access'] = FALSE to TRUE.
3. Run [siteurl]/update.php.
4. Switch $settings['update_free_access'] back to FALSE.

Everything seems to be working correctly now under 8.6.1.

imclean’s picture

imclean commented

@morrisem, if you use drush you can do that with 2 commands:

  1. drush cr
  2. drush updb

That worked, but now we're getting the block error in the related issue: #2998096: Unknown column 'block_content_field_data.reusable' after upgrading from 8.5.7 to 8.6.0

Terebinth’s picture

Terebinth commented

Thank you so much @morrisem. That worked like magic after spending the whole day with my site down and trying all sorts of solutions gotten online! Phew!!!!

Version: 8.6.0 » 8.6.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.6.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
cilefen’s picture

cilefen commented
Status: Active » Closed (outdated)

I am closing this support request because there have been no recent comments.

The Drupal Core issue queue is not the ideal place for support requests. Consider other sources of support.