Enabling a new theme during config import can delete smart decision tokens

Created on 6 May 2024, 6 months ago

This is not necessarily a bug with this module but I'm posting an issue to direct people to the necessary core patch that you need to install as a workaround. The problem is if you have an existing theme that uses smart decision blocks and you create a new subtheme the blocks from the parent theme are cloned by default when the module is enabled. If you already have the block config from the new theme exported and are re-importing e.g. deploying to a new environment, the block config will be first deleted and then re-created.

When the smart content blocks are deleted it also deletes the tokens stored in the database and leads to errors on the site.

The fix is to install the core patch (linked).

🐛 Bug report
Status

Closed: won't fix

Version

3.1

Component

Code

Created by

achap 🇦🇺

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

Comments & Activities

Production build 0.71.5 2024