Skip to content
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

Closed
davidalger opened this issue Jan 7, 2015 · 2 comments
Closed

Flushing cache fails to wipe view_preprocessed dir #930

davidalger opened this issue Jan 7, 2015 · 2 comments
Labels
Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development

Comments

@davidalger
Copy link
Member

The CSS pre-processing builds everything into the view_preprocessed/source and view_preprocessed/less directories. Even in developer mode and all caches disabled, however, the files in view_preprocessed/less are not updated correctly when changes are made to the theme and the page refreshed (those in view_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.

@maksek maksek added the PS label Jan 8, 2015
@otoolec
Copy link
Contributor

otoolec commented Jan 14, 2015

David, thanks for reporting this issue. I've opened up ticket MAGETWO-32705 internally to help the team investigate.

@muasir muasir added bug report Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development labels Jan 26, 2015
@tkacheva tkacheva added PROD and removed bug report labels Mar 20, 2015
@mbrinton01
Copy link

Hello @davidalger, this issue should be fixed. Please verify and if you have any concerns, you may reopen this issue.

magento-team pushed a commit that referenced this issue Mar 15, 2017
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
Projects
None yet
Development

No branches or pull requests

6 participants