-
Notifications
You must be signed in to change notification settings - Fork 30
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
Super flusher? #109
Comments
Something like |
I very much agree. Running What would be the down side to not just clear all caches? Any theoretical extra seconds used to fill up some caches occasionally pales in comparison to the hours or even days CiviCRM users needlessly spend trying to complete an operation, such as upgrading from Drupal 7 to Drupal 10. I should know, I just did. After completing what should have been a simple copying over of a separate CiviCRM database into Drupal 10 install, getting it running proved difficult. The I did of course run But by chance, earlier today, I found a mention of a page where I could "Reset Paths" and "Cleanup Caches" at And what do you know, additional old stuff was cleared out, and everything all of a sudden worked :) I think this is a critical issue, which needs to get fixed as soon as possible, and ProposalExpand the capabilities of |
I was recently cleaning up a site after an upgrade that had left an old flexmailer extension installed. In order to recognize the core flexmailer, there were a number of caches that needed clearing, but cv flush wouldn't work because it would error before getting to do anything useful. In the end, what I did that worked was:
It occurs to me that this should be possible to script, and would be nice to include in the usual cv commands, as a super flush kind of action.
Make sense?
The text was updated successfully, but these errors were encountered: