I have the following fatal error when upgrading from 7.37 to 7.38.

Fatal error: require_once(): Failed opening required '/public_html/includes/theme.inc' (include_path='.:/usr/lib/php:/usr/local/lib/php') in common.inc on line 5195.

Here are my upgrade steps:

  1. Place site into maintenance mode.
  2. Copy changes made to .htaccess file.
  3. Delete all files and folders from the drupal root except for the sites folder
  4. Uploaded new 7.38 drupal files.
  5. Pasted the changes to new .htaccess file.
  6. Already logged in as admin, navigate to mydomain.com/update.php

Can anyone shed some light on this issue? This is the first time I've had this problem after doing many many updates with Drupal core.

I've now downgraded back to Drupal 7.37 and the site is working again.

Comments

VM’s picture

perhaps a corrupted theme.inc file when it was extracted or when it was uploaded.

galacto’s picture

Hi chrisck,

I did not have same issue but upgrading from 7.36 to 7.38 caused issued with some of my custom pages. I went through git commits and did the diff on 7.36 and 7.38 files. I found that there are couple files which got changed in 7.38 but not listed on git commits so copied those files over to 7.38 includes/ folder and that worked for me.

specifically includes/entity.inc file did the trick.

HTH

~

rodvolpe’s picture

Hi galacto,

I had the same issue. Replacing the7.38 entity file with the 7.36 did the trick.

I am just worried that this is not a very clean solution isn't it.

Thanks

vedpareek’s picture

Hello,

Cart is not working for anonymous user after upgrade 7.36 to 7.38.
I have following fatal error on cart page for anonymous user.

EntityMetadataWrapperException: Invalid data value given. Be sure it matches the required data type and format. in EntityDrupalWrapper->set() (line 736 of /var/www/strandofsilk/profiles/commerce_kickstart/modules/contrib/entity/includes/entity.wrapper.inc).

FlutterStack’s picture

5. Pasted the changes to new .htaccess file.

Revert back the changes which you done for the .htaccess file test it once.