Re: CSS Problem
Reply #1 –
I'm going to guess that it works fine if you don't have CSS/JS minify enabled?
As the hives are located in a different directory then the original CSS files, it needs to change the relative directory pointers in the CSS files, and it looks like its doing that wrong for some reason?
Re: CSS Problem
Reply #4 –
I just realized that those are files for file based caching. Silly me.
But I am still wondering how the cache file went to the default theme folder. Will try to resolve this soon.
Re: CSS Problem
Reply #6 –
I failed to see how that can cause the css problems after the upgrade as I emptied all the js and css in the cache directory and uninstalled all addons before the upgrade. I could misunderstand the situation though with the new approach 1.1 is using for caching now.
I have deleted my cache in default theme and so far nothing is there. The folder or its content is not recreated until now.
Until it is fixed, I'd prefer it this way (i.e. in root cache folder) because the minified css in default theme is also using ../themes/default resulting errors due to reading /themes/default/themes/default rather than just /themes/default.
Re: CSS Problem
Reply #8 –
How can that work when it is already uninstalled, not reinstalled and not even exist as an integration hook?
Re: CSS Problem
Reply #12 –
That is correct but I am not sure what is its impact now. One thing I am sure is that it is started 2.16am i.e. about 1 1/2 hour ago. Error log is clear so far.
I guess I just leave these two cache folders as they are?