-
Notifications
You must be signed in to change notification settings - Fork 56
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
civix repair? #252
Comments
@artfulrobot It might be a good idea. Let me share a couple related thoughts first:
Anyway, that's a bit of rant. I need to stop typing. :)
I wonder if it would make sense to have an option like |
@artfulrobot I've added an option Closing because #254 and #255 should reduce the incidence a lot. Released v22.07.2. There could still be scenarios for something like (An ideal report is probably something like "Clone the repo |
Thanks @totten, makes sense.
I didn't know that, I suspect that's where I've fallen down. Wouldn't it make sense to either:
|
@artfulrobot Yup, |
The mixin thing is really clever, but I do keep breaking extensions, leading to situations where I'm not sure how to get back to a working state.
I think this comes from things like async changes: extension changed on site A and site B separately, then merge the changes and it breaks. Typically, I think it's like:
upgrade
.Then merge. I've ended up with functions in extension.php which want to call out to _civix_something() in extension.civix.php which no longer exists. e.g. on one extension, that uses settings, the
hook_civicrm_alterSettingsFolders
was left calling a non-existant civix function. I didn't want to remove that because presumably the settings would not be picked up, then, but I didn't know how to add the mixin for settings either.It leads to a situation where it kills Civi until you can resolve it. I've sometimes found removing the civix version from info.xml and re-running
civix upgrade
provides a fix.Anybody else had this trouble and got any tips? Is
civix repair
a non-sense idea?The text was updated successfully, but these errors were encountered: