In version 2.0.39, there was a problem with projects with non-empty BaseUrl and appendTimestamp included. In this case, when the list of files (.css and .js) was compiled, the path to the file was built incorrectly when the file modification time was received. BaseUrl was contained in both @webroot mask and relative file path. Those, it turned out something like this G: /XAMPP7/htdocs/subdomain/site/web/subdomain/site/css/custom.css instead of the prescribed G: /XAMPP7/htdocs/subdomain/site/web/css/custom.css. There it was fixed by removing BaseUrl in the relative path.
Here I found a similar problem: no compiled files were generated on projects with non-empty BaseUrl. The script that bypassed the .css and .js lists could not get any of the files, since paths contained doubled BaseUrl.
The issue was discussed here https://github.com/yiisoft/yii2/issues/18414.
In version 2.0.39, there was a problem with projects with non-empty
BaseUrl
andappendTimestamp
included. In this case, when the list of files (.css and .js) was compiled, the path to the file was built incorrectly when the file modification time was received.BaseUrl
was contained in both@webroot
mask and relative file path. Those, it turned out something like thisG: /XAMPP7/htdocs/subdomain/site/web/subdomain/site/css/custom.css
instead of the prescribedG: /XAMPP7/htdocs/subdomain/site/web/css/custom.css
. There it was fixed by removingBaseUrl
in the relative path.Here I found a similar problem: no compiled files were generated on projects with non-empty
BaseUrl
. The script that bypassed the .css and .js lists could not get any of the files, since paths contained doubledBaseUrl
.Fix #54