Background: Drupal recommended some module upgrades (ctools and panels were the biggies) which I did through the new D7 upgrade interface. Drupal reported back that all updrages including database changes were successful. In the past I would have upgraded the old manual way but I thought I'd try out this "easier" method.

One immediate issue, that took me a while to diagnose, was that all the modules that had been upgraded had the wrong file permissions (644 instead of 755 iirc) and this was causing lots of broken functionality and styling as the js and css for those modules were coming up 404 not found. After I manually reset the permissions of all files in the upgraded modules to 755, they started working again.

Now however, administrative overlays are not closing and the page isn't redirecting to what would normally come after an overlay is submitted or closed. These are the relevant Firefox console errors:

Permission denied to access property 'Drupal' @ http://www.example.com/modules/overlay/overlay-child.js?v=1.0:16
Permission denied to access property 'defaultView' @ http://www.example.com/modules/overlay/overlay-parent.js?v=1.0:267

Related (I think) are ajax errors I'm getting in Views ("AJAX HTTP request terminated abnormally") which are happening every time I try to edit and then save and view property, essentially making my views uneditable at the moment.

Have tried clearing caches and with and without css/js aggregation etc.

Any ideas?

Comments

inteja’s picture

I had cleared the Drupal cache as indicated above, but trying another browser it worked fine, so cleared Firefox cache and all good now.

The strange file permissions issue after module upgrade still stands though. Maybe this post will be of help to anyone who encounters the same issue after using the administrative user interface to upgrade modules in D7+

--
Brian.