-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flushing cache fails to wipe view_preprocessed dir #930
Labels
Issue: Ready for Work
Gate 4. Acknowledged. Issue is added to backlog and ready for development
Comments
David, thanks for reporting this issue. I've opened up ticket MAGETWO-32705 internally to help the team investigate. |
muasir
added
bug report
Issue: Ready for Work
Gate 4. Acknowledged. Issue is added to backlog and ready for development
labels
Jan 26, 2015
Hello @davidalger, this issue should be fixed. Please verify and if you have any concerns, you may reopen this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Issue: Ready for Work
Gate 4. Acknowledged. Issue is added to backlog and ready for development
The CSS pre-processing builds everything into the
view_preprocessed/source
andview_preprocessed/less
directories. Even in developer mode and all caches disabled, however, the files inview_preprocessed/less
are not updated correctly when changes are made to the theme and the page refreshed (those inview_preprocessed/source
are though). This causes even bigger problems because when flushing the cache storage (or cleaning all types) from either the admin or the CLI, these directories are not emptied, resulting in a stale cache which must be manually removed from the file-system to update what's run through the LESS compiler.The text was updated successfully, but these errors were encountered: