1

while the website documents the upgrading process for civicrm itself, i noticed this seemed to touch less upon general tips for updating its extensions.

now i've heard advice to in general first perform a process of 'update extension, run DB upgrades, clean caches' for the more basic extensions, to only then run similar steps for extensions built on top of those.

i'd like to deploy civicrm using a docker container tho, with any extensions built into the container image. in that type of scenario, the above process would end up somewhat more cumbersome, as you'd end up having creating intermediate images to update only part of the extensions used.

hence i was wondering, does the advice to only sequentially update civicrm extensions make sense? or should one generally be able to get away with deploying an image updating any used extensions to their newer versions?

1 Answer 1

2

I think that advice is somewhat outdated. Recently, CiviCRM has gotten better about upgrades, in fact the same command will upgrade both CiviCRM core + all installed extensions: cv upgrade:db. Extensions are internally sorted and upgraded in order of their dependencies. Not all extensions have opted-in to being sorted yet, but a lot of those don't have any dependencies so it's not a problem.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.