I've seen other issue reports like this that eventually gets closed as 'works as designed' but I beg to differ.

I'm running an instance of OpenChurch and was presented with email warnings and a status screen that tells me an update from beta 10 to beta 11 is available.

I try to do the update from the UI and it fails with

Downloading updates failed:

    openchurch-7.x-1.11-beta11-core.tar.gz does not contain any .info files.

If this is "as designed" there is a problem with someone's design.

Comments

drupalninja99’s picture

Status: Active » Needs review

I have done some more testing on this. I don't know why the updater can't just re-download the profile. I know that with drush you can just do "Drush dl openchurch" and then "drush updatedb" to update OpenChurch to the latest version. This is what Commerce Kickstart does:

http://www.drupalcommerce.org/commerce-kickstart-2/install

Commerce Kickstart is the most popular distribution on Drupal so I would defer to their way of handling updates. I don't control the Drupal updater so this is not something that I can fix or some problem with OpenChurch itself.

drupalninja99’s picture

Status: Needs review » Closed (works as designed)
jmcboots’s picture

Closed?

It does the same thing for beta14 trying to use the admin update interface.

I also cant do a drush dl either because openchurch is a profile, and drush is trying to install it as a module.

So how does one go about updating openchurch?