"Unable to save site report on configuration change: Serialization of 'Closure' is not allowed"

Created on 18 August 2023, over 1 year ago
Updated 28 August 2023, about 1 year ago

Problem/Motivation

When configuring fields, if site module is set to save report on config changes, it takes a long time and ends in error:

Unable to save site report on configuration change: Serialization of 'Closure' is not allowed

Steps to reproduce

Go to any Manage Fields page and add a field.

Proposed resolution

Figure out the same serialization technique that config API uses so "closure" are handled.
Add a setting for "Config Exceptions" so users can define a list of config types to ignore when saving a report.

Remaining tasks

TBD

User interface changes

A textarea on the Settings page that appears when "Save on Config" is checked.

API changes

None

Data model changes

Added setting.

πŸ› Bug report
Status

Needs work

Version

2.0

Component

Site Module

Created by

πŸ‡ΊπŸ‡ΈUnited States Jon Pugh Newburgh, NY

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @Jon Pugh
  • Status changed to Needs work about 1 year ago
  • πŸ‡ΊπŸ‡ΈUnited States Jon Pugh Newburgh, NY

    Same thing happens when saving a view.

    Drupal Config API converts these complex config objects to YAML at some point, storing it or writing it to files.

    We should research how that happens and do the same when saving it.

Production build 0.71.5 2024