Commit 97664d3
unknown
fix(admin): purge ALL scope overrides of merge_css/js setting
Migration 266 set dev/{css,js}/merge_{css,js}_files = 0 at the DEFAULT
scope but prod kept emitting merged-bundle URLs (each cache flush
produced a fresh hash, all of them 404). Diagnostic on prod confirmed
the bundle URL stayed in the rendered HTML across migration apply +
cache flush + Coolify redeploy.
Root cause: Magento config inheritance is default → website → store.
A leftover website- or store-scoped row in core_config_data with value
'1' shadowed the default '0'. The admin header's View As feature loads
whichever store context the operator picked, so a single website
override was enough to keep merging on for every admin page render —
and the merged bundle URL never existed on disk because the entrypoint
wipes media/js/* on every container start.
Fix: DELETE every row at every scope for the two paths, then INSERT
the default '0'. After this runs there's exactly one row per path
(scope=default, value=0) and no override can outrank it.
Pair with a cache-flush API call after deploy
(/reindex/api/flush?token=...) to invalidate the cached HTML still
referencing the dead bundle URL.1 parent a180360 commit 97664d3
1 file changed
Lines changed: 20 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
| 1 | + | |
| 2 | + | |
| 3 | + | |
| 4 | + | |
| 5 | + | |
| 6 | + | |
| 7 | + | |
| 8 | + | |
| 9 | + | |
| 10 | + | |
| 11 | + | |
| 12 | + | |
| 13 | + | |
| 14 | + | |
| 15 | + | |
| 16 | + | |
| 17 | + | |
| 18 | + | |
| 19 | + | |
| 20 | + | |
0 commit comments