Fatal error in serialization_update_8302() when updating to 8.3.0-rc2

+++ b/core/modules/serialization/serialization.install
@@ -42,7 +42,7 @@ function serialization_update_8302() {
+    ->save(TRUE);1

Syntax error :)

RTBC after that's fixed.

17:32:28 <berdir> what confused me is that it explicitly passes FALSE to save, I'd understand forgetting to pass TRUE, but not sure about this
17:32:44 <berdir> maybe damiankloip or someone else who worked on https://www.drupal.org/node/2751325 knows?
17:32:51 <drupalbot> https://www.drupal.org/node/2751325 => All serialized values are strings, should be integers/booleans when appropriate #2751325: All serialized values are strings, should be integers/booleans when appropriate => 265 comments, 1 IRC mention
17:47:44 <catch> berdir: my assumption would be they meant to pass TRUE and got the argument switched when writing the patch.

I agree with @catch's suspicion at 17:47:44.

But I still did some issue archeology. Turns out that the patch at #2751325-179: All serialized values are strings, should be integers/booleans when appropriate had this right (->save(TRUE)). Then #2751325-182: All serialized values are strings, should be integers/booleans when appropriate removed that hunk completely. (Both of those patches by @tedbow.) Then @alexpott restored this hunk in #2751325-188: All serialized values are strings, should be integers/booleans when appropriate after discussing it with @catch. But it inverted the value. Why? I suspect because we changed the default value for

#182

+function serialization_update_8302() {
+  $config_factory = \Drupal::configFactory();
+
+  $config_factory->getEditable('serialization.settings')
+    ->set('bc_primitive_data_normalizer', TRUE)
+    ->save(TRUE);
+}

#188

+function serialization_update_8302() {
+  $config_factory = \Drupal::configFactory();
+  $config_factory->getEditable('serialization.settings')
+    ->set('bc_primitives_as_strings', FALSE)
+    ->save(FALSE);
+
+  return t('The REST API will no longer output all values as strings. Integers/booleans will be used where appropriate. <a href="https://www.drupal.org/node/2837696">If your site depends on these value being strings, read the change record to learn how to enable the BC mode.</a>');
+}

i.e. I'm willing to bet that @alexpott simply search-and-replaced TRUE with FALSE and replaced one thing too many.

Nice archaeology.

Committed/pushed to 8.4.x and cherry-picked to 8.3.x. Thanks!

Hi,

I am trying to update from Drupal 8.1.1 to the latest Drupal 8.3.0 stable version but I am receiving that error message:

PHP Fatal error:  Call to undefined method Drupal\Core\Config\Schema\Undefined::get() in /.../core/lib/Drupal/Core/Config/StorableConfigBase.php on line 179

I have checked the serialization_update_8302() function in serialization.install but it has already ->save(TRUE) call.

I am unable to update to 8.3.0 and I would like not to use the 8.3.x unstable version.
Is there a solution for 8.3.0 or are you going to release a new stable version?

@MmMnRr are you able to provide a backtrace? It's possible a different update has a similar problem to the one fixed here.

It's possible a different update has a similar problem to the one fixed here.

That seems unlikely, I grepped the entire codebase for ->save(FALSE), and the only remaining occurrences are in ConfigEntityStorageTest.

Besides, #11 says they traced it to this ->save(TRUE) call. It seems that #11 is a different error. AFAICT this must be happening in here:

  protected function castValue($key, $value) {
    $element = $this->getSchemaWrapper()->get($key);

It's the only ->get( call in StorableConfigBase.

Without more information/steps to reproduce, I don't think we'll be able to help here.

I tried to run update.php again and for no reason it worked perfectly now.
So the issue is solved.

I tried multiple times to run update.php and I always received the same error. But now it worked.

I do not have drush installed in my server yet.
The trace came from the Apache log.
I checked the specific line referenced in the trace and it is the following:

/.../core/lib/Drupal/Core/Config/StorableConfigBase.php

protected function castValue($key, $value) {
    $element = $this->getSchemaWrapper()->get($key);

It is the same code as explained in comment #14.
The error appeared when I try to run update.php. But now it disappeared.

The only difference since the last try is that I have navigated through the website pages, although the update did not work.
Maybe that navigation triggered something. But I have no proof.

Thank you and sorry for the inconvenience.

Created #2867444: Configuration schema errors whilst updating to 8.3.0

@MmMnRr also if you have anymore of the backtrace of #11 it would be really great to see it.

@alexpott Unfortunately, as I did not update from drush I do not have more trace information. Furthermore, as the update worked now, I am unable to reproduce the issue again.

I have same issue.
BTW first i was working on drupal 8.1 and I updated to 8.3.4
Files updated but when trying to run update.php its giving below errors.

An AJAX HTTP error occurred.
HTTP Result Code: 200
Debugging information follows.
Path: /update.php/start?id=14&op=do_nojs&op=do
StatusText: OK
ResponseText:
Fatal error: Call to undefined method Drupal\Core\Config\Schema\Undefined::get() in /core/lib/Drupal/Core/Config/StorableConfigBase.php on line 179

Hello all,

My error also solved.
I also tried to run update.php multiple times but its not helped.
after that I have cleared the caches and run again update.php all the errors got disappeared.
I have list of errors if anyone want to check more.