Upgrading Drupal

I have a Drupal 7 site I'm upgrading to Drupal 8. There is a custom "Articles" content type, and after upgrading, trying to edit existing articles or add new ones gives me this error:

Drupal\Core\Entity\Query\QueryException: 'field_last_name:value' not found in Drupal\Core\Entity\Query\Sql\Tables->ensureEntityTable() (line 368 of core\lib\Drupal\Core\Entity\Query\Sql\Tables.php).

'field_last_name' is used by a content type called "Writers". The "Articles" type has a few fields that are set up as entity references to "Writers".

How can I upgrade to drupal9?
Also, do you have auto-update?

Hello everybody, good day.

I am currentl working in a project that uses Drupal 8 core. This project includes the use of BLT and Lightning and it has its repository in GitHub, using automated checks through Travis.

I was requested to do a Drupal core update due to a security issue. I had to do an update from BLT 9 to BLT 11 version. I ran all updates locally and everything ran well.

However, when sending my pull request to GitHub, Travis is showing an error during run_tests script, specifically in the following command:

Dear community

I am currently trying to update modules on my Drupal7 websites, directly from the Web browser. However, I receive the following error message:

I already have Drupal 8 that was installed with composer.

At this point I want to reinstall & rebuild Drupal's web site from the beginning.

Wish to do it more properly according some experience I have learned, and your advise.

Please inform if it is a good idea to install Drupal 9?

Also. want to install it with git, so I can manage versions ,and go back in case of something will go wrong with new update etc -

Can you please recommend on a good tutorial for installing Drupal 9 with composer and Git?

Hi There,

I am trying to upgrade Drupal via composer from 8.7.10 to 8.8.5.

First, I am performing composer update and after updating composer getting the below metioned error:

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

I checked the server error log and got the following error: