Dear all,

I run a small private website on 1&1 (IONOS) Server. When ordered the Version 9.1.5. was installed. All Updates are not done by the provider.

So, yesterday I started to manually update to 9.1.7 security update and I followed strictly the guide here:
https://www.drupal.org/docs/updating-drupal/updating-drupal-core-manually

When I have finished the FTP Deletes and uploads (/core; /vendor; top level dircectory) I wanted to start mywebsite.com/update.php

So I changed in settings.php to: 

$settings['update_free_access'] = TRUE;

When I wanted to execute update.php I got this error message:

"The website encountered an unexpected error. Please try again later."

I could not identify the cause so I deleted again everything and restored the backup that I made before.

But again the same problem

Did I do something wrong or failed to see something?

  • In the Update Information it is said that no changes have been made to the .htaccessweb.configrobots.txt, or default settings.php 
  • Can I update directly from 9.1.5 to 9.1.7? I would say YES.
  • I run some modules in Drupal (autofill, ctools, linkit, pathouto, views_slideshow) Do they effect the update?

Thanks for any help

Friedhelm

Comments

mmjvb’s picture

Add
$config['system.logging']['error_level']='verbose';

to your settings.php to see what is wrong.

You could check your error log to see the same. You even could set error reporting to show errors. 

There should be no problem to go from 9.1.5 to 9.1.7. The extensions in use could have an effect, especially when they are not current. However, that is very unlikely in your case (two bug fix releases).

GenGomez’s picture

Dear @mmjvb

Thanks for your comment.

Since I have not a dedicated Apache Server at my WebSite Hoster (IONOS / 1&1) I decieded to let them upload the backup before my failed trial.

So, my website is back and I think since it is only a small private site, I will skip the updates until my project has been finished

Thanks anyway.

Greetings

Friedhelm

mmjvb’s picture

Before trying again make sure you enabled error reporting!