The previous single body field could not distinguish 'use the default' from 'save the pre-filled default', so the first settings save locked the hint in as a custom override for ALL orders — the paid/unpaid default logic never ran. Give each payment state its own editable body field (emailBodyHtmlDePaid / emailBodyHtmlEnPaid) with its own empty-fallback. A body submitted unchanged from its built-in default is stored as empty, so 'use default' survives saves and future default updates propagate.
4 lines
186 B
SQL
4 lines
186 B
SQL
-- AlterTable
|
|
ALTER TABLE "ShopSettings" ADD COLUMN "emailBodyHtmlDePaid" TEXT NOT NULL DEFAULT '';
|
|
ALTER TABLE "ShopSettings" ADD COLUMN "emailBodyHtmlEnPaid" TEXT NOT NULL DEFAULT '';
|