I did upgrade my drupal 7 site to a drupal 9 site with the module 'migrate'.
After this upgrading I see that the database is grown from 98 to 250 records.
Most new records are named ".._migrate_map_d7_" and ".._migrate_message_d7_".
My question is; may these records ".._migrate_map_d7_" and ".._migrate_message_d7_" been deteted from the database when the upgrading is completed?
Are there besides these records still more records that maybe can deleted?
I am currently running a small Drupal site (Drupal 7.34) as a web based vinyl records database which I would like to migrate to a new server on latest Drupal. I have a lot of questions regarding this "double" migration (migrate from an old to a new drupal core, and change physical servers) but I think its better that I solve my current issues before I actually migrate my data.
We have a website which has 3 modules patched for Drupal 9 compatibility. We managed to get the site updated and everything's been fine for a few weeks. I've been doing some new work on the site and I just ran the `composer update` and now I'm getting `requires drupal/core ~8.0 ... but it conflicts with your root composer.json require (^9.2)` errors on all of them. Does anyone know what's up with this? Shouldn't composer pass all of these patched d8 modules as compaitble with d9?
I just manually upgraded from Drupal 9.2.7 to 9.2.8. I attempted to uncomment the .htaccess file, but still can't access the site. I am running the Drupal in a subdomain blog.xyz.com which is linked in my webhost to xyz.com/clickandbuilds. I did this successfully last time I upgraded from Drupal 8 to Drupal 9.2.7, but this time it doesn't seem to work no matter what I try. I'm getting an error that the site can't provide a secure connection, and it's being redirected to www.blog.xyz.com.
I purchased a theme that came with a full Drupal install with it. The problem is that it was last updated several months ago and Drupal core and numerous modules are outdated. I've been trying to update via composer and can't seem to get it done. The first problem was locked modules, so I overwrote the lock file with the one that comes with this version of Drupal. That seemed to fix that issue, as now I can get further in the update. It still fails, though. And then the site becomes unavailable with a 500 error.
After some checks, everything seems to work fine except for status page that is empty (no errors, no WSOD, just sections title and no information underneath..?)