Hi @oliviertassinari
,
The two sites you referenced appear to have different asset optimization settings. To resolve the issue, you’ll need to:
- figure out which site works the way you want, then go to the other site and
- uncheck the ‘Disable asset optimization’ setting in Site settings > Build & deploy > Post processing > Asset optimization
- mirror the settings from the working site
- recheck the ‘Disable asset optimization’ setting
You may be wondering why you need to disable and then re-enable asset optimization. We have an open bug and disabling and re-enabling is the workaround until we can roll out a fix!
Apologies we don’t have any docs on this, but you may want to check out our support guide on trailing slash behavior to get a better understanding.
Hope this helps and do let us know how it goes! ![]()