Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
As a site admin, I need definitive steps for updating the govCMS distro (including security updates) #344
Can you advise where I would find such a guide, if it exists?
I haven't been able to find one so far. So I have written my own, which I have now updated (and works) as my old approach based on the steps for Panopoly ( https://www.drupal.org/node/2691663#comment-11571127 ) did not work for govcms.
My previous approach (based on the Panopoly steps) did not work, here is what works:
I found this new approach to work. Thanks to drupal.org user edb for the advice on the above.
Why did my previous approach not work?
Source directory /tmp/drush_tmp_1472811109/govcms is not readable or does not exist. [error]
I tried setting all the permissions, changing the tmp path in Media, File System in Config in Drupal Admin pages, but still got the same error.
Tip for the new working approach: Make sure you use the .zip/tag.gz from drupal.org/project/govcms and not the ones from the github project page for the distro. I would not suggest using the zip from github in these steps as not everything is included with that version, regarding dependencies. Package/dependency management is used to resolve that. But with the zip (or tar.gz from drupal.org/project/govcms everything regarding dependencies is included) so it's good to go straight out the box.
I've updated the drupal.org issue: https://www.drupal.org/node/2691663#comment-11571127
I know that one cannot just do a
There is a guide for developers, https://github.com/govCMS/govCMS/wiki/Managing-Drupal-Security-Updates - but this appears to be about contributing fixes into the govCMS codebase, so is not for Site Admins who actually want to apply updates to the distro that have been officially made available.
Your approach above is a good one. The issue with using the raw ZIP/TAR from Github is that it's actually a series of build scripts essentially, that build sources like Drupal.org will process and turn into something more usable as you've unfortunately discovered the hard way. So, yes, preferable to take the download directly from Drupal.org and apply that.
One of my focuses over the backend of this year is to really ramp up the amount of supporting documentation we have available for the distribution, both from a maintenance perspective for customers using it outside of our hosted platform, and for modules and functionality available to Site Builders and editors that might not be immediately obvious (especially for those new the Drupal).
Thank you @aleayr for the folllow up here and on my Drupal issue: https://www.drupal.org/node/2691663 - thank you for commenting there and closing - I will now follow the the thread here on Github. Thank you for your support regarding documentation creation.
I can close this issue on the basis that you have agreed my approach is good for updating. Or perhaps keeping it open it may be useful as todo when updating the official documentation. Let me know and I can close if that would be suitable. Thank you.
I should add further information to my instructions to make them more precise:
What this actually means is to download the packaged version of the distro that includes Drupal core, so that both the distro and Drupal core version (that the distro is parity with) will be upgraded. For example, on the drupal.org/project/govcms page you can download the code with both core and govcms distro here: https://ftp.drupal.org/files/projects/govcms-7.x-2.10-core.zip
But note that if a version of the distro is released that uses the same version of Drupal core as before, then you would only need the distro itself.
In my most recent case we needed to upgrade both: we were running 7.44 parity with govcms 2.8. Core 7.52 introduced security updates and govcms 2.10 is parity with this so we upgraded both.
For a core and distro update the files from the downloaded package (e.g. .zip) need to replace both core files and distro files. I removed all of my existing Drupal core and replaced with that from the downloaded zip above. I was careful to leave intact my contrib and custom modules, and themes, anything specific to my implementation not part of core. I deleted the profiles folder I had and replaced this with the profiles folder from the zip download (this folder contains the updated govcms).
as before. No change here. You should still run this command.
FYI Distros can be updated the CLI way - not for the faint of heart so YMMV.
You can do it with Drush - check the process and it’s caveats on this page re: features (https://www.drupal.org/node/22721772):
Change into the root directory of your govCMS site and run:
…or you can follow the manual upgrade instructions to download and update database on that same Panopoly page…
You should always update release-by-release - skipping a release could have unintended consequences.
Happy to help more if you need it!