Upgrading Drupal

FIXED:  I found that the PHP version was set to 5.3.  I changed it to 7.2 and all is working now.

Thanks all for your replies.

I tried to install the Drupal 7.66 update today and all I got was a screen full of weird characters.

I returned to my previous version and tried again and got the same thing.

Then I tried to install Drupal 7.65 and it installed cleanly.

Anybody have any ideas of what is going on?  And how do I fix it?

Hi there, 

I am migrating a large site form Drupal 6 to Drupal 8. 

After running Drush migrate-upgrade --configure only  with 

-sh-4.2$ env PATH="/opt/plesk/php/7.3/bin:$PATH" drush migrate-upgrade --legacy-db-url='mysql://AC_D6_clean_user:password@localhost:3306/AC_D6_clean' --configure-only

Had the error: 

In database.php line 365:
Driver not specified for this database connection: upgrade

I added a second $databases connection to the source database in setings.php

Hi all;

After updating to Security Update 8.6.15 (from 8.6.13).

Running composer command: "composer require drupal/geofield" or "composer require phayes/geophp".

I get the following timeout message;

Hi, when I try to perform a database update after core update from 8.6.13 to 8.6.15 I receive this error:

# drush updb
The following updates are pending:

system module :
Clear the library cache and ensure aggregate files are regenerated.

In this post I am not asking for help. Instead, I want to post it here in case anyone out there is managing their site via Acquia Dev Desktop.

After (quite) some pain, searching, trial and error, I have managed to update Drupal core (8.6.13). My site was built and is managed via Acquia Dev Desktop. I had tried various update methods, manual, composer, etc, each time getting errors. Finally I found a few posts and pieced it together how I was able to update D core. Leave it here in case anyone will bang their head into the wall as well.

Hi,

When upgrading from 8.5.x to 8.6.14 I get this message:

Warning: Class Drupal\Core\Extension\Extension has no unserializer in Drupal\Core\Cache\DatabaseBackend->prepareItem() (line 167 of core/lib/Drupal/Core/Cache/DatabaseBackend.php).

This problem gets discussed here.

https://www.drupal.org/project/drupal/issues/3031128