I'm getting WSOD since i upgraded to 8.2.0, there's a PHP exception in FPM logs:
Uncaught PHP Exception Drupal\Component\Serialization\Exception\InvalidDataTypeException: "yaml_parse(): scanning error encountered during parsing: mapping values are not allowed in this context (line 11, column 30)" at .../core/lib/Drupal/Component/Serialization/YamlPecl.php line 63
| Comment | File | Size | Author |
|---|---|---|---|
| #12 | interdiff-2815613-8-12.txt | 13.47 KB | darol100 |
| #12 | 2815613-Fixing-Uncaught-PHP-Exception-InvalidDataTyp-8-12.patch | 14.83 KB | darol100 |
| #8 | Uncaught-PHP-Exception-2815613-8.patch | 6.63 KB | sozkara |
Comments
Comment #2
tstoecklerSo (a little bit confusingly) this is not part of the serialization module. Tagging as base system until we know what it actually is.
Do you have any way of finding out what the YAML file is that is causing the problem?
Comment #3
sozkara commentedUnfortunately not, since error is somewhat cryptic. I tried removing all custom themes to no avail. Creating a new site with same codebase yields no errors.
Comment #4
sozkara commentedWell, since i was randomly uninstalling modules that provides .yml files, the root of the issue was "bootstrap layouts" module it seems. As soon as i disabled the module the site opened no problem.
Comment #5
tstoecklerAhh, that helps. Yeah that's a bug in that module.
bootstrap_layouts.layouts.ymlcontains code, such as:That is invalid, due to the double colon (":").
It must be
instead.
Comment #6
darol100 commentedThank you for the report of this bug. I will see if I can get this fix today in dev branch. Patches are appreciated.
Comment #7
sozkara commentedHere's the patch as per tstoeckler's comment. Seems to work just fine
Comment #8
sozkara commentedSorry, file was empty for some reason
Comment #9
darol100 commentedChanging the status to needs review.
Comment #10
tstoecklerPatch looks good to me.
Comment #11
markhalliwellThis needs to be committed ASAP. In case people are unaware of why some are getting this and others are not, parsing YAML files are inconsistent between the PECL and Symfony implementations. This is just another example of a "quirk" that is technically allowed by the Symfony code.
Comment #12
darol100 commented#8 Patch it was a good start but is only taking care of the label key value pair, which is not preventing in the future to cause the same error in other value. I wrote another patch that cover every key value pair in YML file.
Changing the status for needs review.
Comment #14
darol100 commentedI have committed the patch from #12. And I believe this issue is been solve please let me know if this still an issue.
Comment #17
chaitanya17 commentedSeems #12 patch is not working for 8.2.1