Issue Bug Closed

#109638Backend user settings are JSON-encoded twice before being stored in the database

Stefan Bürk 04/17/26, 22:02 updated 04/21/26, 11:30

Description

Since #108832, backend user settings are persisted as JSON
in the be_users table, along with an upgrade wizard to
migrate serialized settings to JSON.

Due to a manual json_encode(), values were stored
double-encoded. As a result,

(string)’”{“key”: “some-value”}”’

was persisted instead of the expected

(string)’{“key”: “some-value”}’

Reviews 2

History 412

  1. Stefan Bürk commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-04-20T16:20:13+00:00" > 04/20/26, 16:20 </span>

    Applied in changeset commit:fa023de50e151c6d71f43922b5dc1183dba7a516.