Closed sarahschuetz closed 4 years ago
No we are not using @web
. However we are using other aliases. Are all aliases a problem, or just @web
?
Just @web
, as it cannot be correctly calculated from console requests.
Was this issue resolved for you, and if so then how? It may be related, hence I ask.
@bencroker as said here, I changed my folder path from a relative path to @webroot/blitz/cache
. When warming the cache via console the language is set correctly on my local test environment. I will update you as soon as a had a chance to test it on the server as well.
Great, let me know.
Please also be sure to test this using the Guzzle warmer.
Changing the folder path to @webroot/blitz/cache
also fixed the problem on our server. All good now 🎉 Thanks for your help!
Sure thing!
Describe the bug
I am working on a multisite-project with german and english sites. When the cache is warmed using the "Warm Cache" button in the "Utilities" section, the
craft.app.language
is set incorrectly and the translations uses the wrong translation file. When the same page is cached just by visiting the page, without prewarming, the language works correctly. Also without cache, the language is correct.To reproduce
Steps to reproduce the behaviour:
lang="{{ craft.app.language |slice(0,2) }}"
on thehtml
element.<html lang="de">
and translations work correctly<html lang="de">
and translations work correctly<html lang="en">
and translations don't work correctlyVersions