Since upgrading core from 7.16 to 7.17 I have been unable to update or install any modules using the admin interface. The modules download correctly, but when it goes to the install page, I get the following error message:

Update manager

Error message

Notice: Undefined index: log in update_authorize_update_batch_finished() (line 183 of /home7/japanphi/public_html/drupal7/modules/update/update.authorize.inc).
Warning: Invalid argument supplied for foreach() in update_authorize_update_batch_finished() (line 183 of /home7/japanphi/public_html/drupal7/modules/update/update.authorize.inc).
Notice: Undefined index: log in update_authorize_update_batch_finished() (line 232 of /home7/japanphi/public_html/drupal7/modules/update/update.authorize.inc).
Update failed! See the log below for more information.
Next steps

Your modules have been downloaded and updated.
Run database updates

A few of my modules have security updates needed, and so this is potentially a pretty serious problem. I'm not advanced enough with drupal to figure out what has caused this or how to fix it...

Comments

CowTownFarmBoy’s picture

Priority: Normal » Major
Status: Postponed (maintainer needs more info) » Active

Are you familiar enough with the process of doing it manually? If so until there is a fix you might do it that way to keep current. I do it that way by choice and find it quick and easy. So as a work around you might us the old way.

A link to information on the Drupal ste herewould be http://drupal.org/documentation/install/modules-themes/modules-7 which has instructions to both the way you are trying and the old alternative path.

YesCT’s picture

Priority: Major » Normal
Status: Active » Postponed (maintainer needs more info)

@osarusan this must be stressful for you.

We need some way to confirm that the error you are getting is reproducible.

Here are some suggestions: try searching for that error and see if you can find another issue with people having a similar problem.
If you do, come back to this issue, and link to that other issue in a new comment.

If no-on else is having the problem... this might be better classified as a support request.

And to get a good response to help you, please provide some more information, like a list of modules that you have enabled on your site.
And if you are using a hosting service, which hosting service? Maybe your hosting service changed something.

@CowTownFarmBoy perhaps you could give more detail about the manual instructions for uploading or a link to them?

CowTownFarmBoy’s picture

Priority: Major » Normal
Status: Active » Postponed (maintainer needs more info)

YesCT - thanks for the idea. I updated the previous post.

osarusan’s picture

Thanks, CowTownFarmBoy. I've been able to update them by manually uploading the files and running the update script. I'm hoping that is just a short-term solution, though, and that I can get to the bottom of this issue eventually.

osarusan’s picture

YesCT, thanks for the reply!

I've searched around and found people with very similar errors, but they all seem to be related to a particular module, and they looked like they were able to fix it by disabling that module. However, as far as I know, mine is not related to a particular module.

Here is one example: http://drupal.org/node/1225552
And another: http://drupal.org/node/1076810
And another: http://drupal.org/node/953708

But they don't seem to be applicable to my situation.

I'll look into filing this as a support request. Sorry for using the wrong area -- I'm still new to the drupal community and wasn't sure what the best way to go about doing this was, as my forum post got no replies.

YesCT’s picture

Oh, you are In the right area. You can change this to a support request by making another comment here and changing the Category drop down to support request.

I find the issue queues a better place than the forums too.

Also, here is a trick that works in the issue queues: take the links to other issues

Here is one example: http://drupal.org/node/1225552
And another: http://drupal.org/node/1076810
And another: http://drupal.org/node/953708

And put it just the issue number in side of: [# ]

And they link nice like

#1225552: Notice: Undefined index: log in update_authorize_update_batch_finished() (line 173
#1076810: Error Notice: Undefined index: log in update_authorize_update_batch_finished() (line 174 of
#953708: Error: "Undefined index: log in update_authorize_install_batch_finished" when installing modules on freshly installed D7 beta2

osarusan’s picture

Category: bug » support

Thanks for the tips! I'm changing this to a support request.

For extra info:

The site is hosted on Bluehost, we have a multisite installation with a total of 3 sites (1 main, 2 additional). I don't believe they changed anything recently though.

I have a number of modules installed: Authentication, CCK, Chaos tool suite, Charting, CiviCRM, Context, Date/Time, Development, Display suite, Drupal for Facebook, Facebook Social, Features, Fields, Fusion Accelerator, Input filters, Media, Mobile, Multilingual, OAuth, Organic groups, Panels, Rules, Skinr, Spaces, Spam control, Statistics, Styles, Testing, Theme Editor, ThemeKey, Ubercart, User interface, Variable, Views, Webform.

As far as I know, the problem occurred when I upgraded to 7.17. My only other hunch is that it might have something to do with htaccess, as I have drupal installed in a subdirectory... but I'm kind of at a loss about what to do to fix this.

chazzmann56’s picture

Status: Postponed (maintainer needs more info) » Active

I have started getting this error on 2 sites that I have updated to 7.17

Warning: fileowner() [function.fileowner]: stat failed for temporary://update_kZQ1fk in update_manager_local_transfers_allowed() (line 932 of /public_html/modules/update/update.manager.inc).

And this line beneath it:

Updating modules and themes requires FTP access to your server. See the handbook for other update methods.

The FTP access information has not changed and I can access it using any FTP software or browser.

On one site I did the update to 7.18, but that did not resolve the issue.

Coupon Code Swap’s picture

Issue summary: View changes

I ran into this issue with Secure Pages installed, even after applying the two recommended patches.

https://drupal.org/project/securepages

If you are running Secure Pages you need to remove:

admin
admin/*

from Pages which will be be secure.

hockey2112’s picture

#9, yes! I disabled Securepages, and that fixed the issue.

Version: 7.17 » 7.x-dev

Core issues are now filed against the dev versions where changes will be made. Document the specific release you are using in your issue comment. More information about choosing a version.