search

backdrop-contrib / d2b_migrate

GNU General Public License v2.0
5 stars 6 forks source link

No Pending Updates #56

Open stpaultim opened 3 months ago

stpaultim commented 3 months ago

I've been testing the D2B Migrate module for the last few days and I'm not able to run the actual upgrade process on the database.

I'm using:

  1. Two local DDev environments for Drupal 7 site and Backdrop CMS
  2. Drupal to Backdrop Migrate (D2B) 1.x-0.8.0-alpha4

Steps to reproduce:

  1. Install D2B and Backup and Migrate on a fresh Backdrop CMS installation.

  2. Create private files directory

image

  1. Configure database connection

image

  1. Database Analysis Step - Run Update Project Data AND Download Available Projects (multiple times) - all expected modules download except Google Analytics.

  2. Skip Backup Files step

  3. Click "Prepare for Upgrade" button

  4. Click "Upgrade Drupal 7 Database" button

image

NOTE: Because of this security notice, I have tried changing permission on private files directory to '750'. This change did not effect the results.

  1. Click "Continue" button

image

I am able to run database analysis, but not the actual upgrade process. I got around this by actually doing a manual command line import of database and running /core/update.php

I am not sure if this is specific to my DDev situation or if this is broken for everyone?

Atten: @docwilmot and @irinaz

irinaz commented 2 months ago

I can import db on most of sites that I migrated, I did have experience similar to what you are describing one or two times. For some reason instead of importing D7 db new Backdrop DB is re-imported and therefore you have to import D7 db manually to run upgrade. I am not sure what is best way to track this behaviour.

stpaultim commented 2 months ago

So, I've tried this many times with one specific database and get these results everytime, if I use the direct database configuration option. If I instead upload a backup and migrate version of the database, I am able to run the upgrade process on this page as expected.

I don't know if this is specific to my site or general. I am able to make copies of this database available to anyone interested in testing. Please, contact me in Zulip.

@docwilmot I am happy to do additional testing if you specify things i should try or watch for.

stpaultim commented 1 month ago

Just trying D2B with another site and running into this same problem. I may need to install backup and migrate on the Drupal 7 site, simply to generate another database output. It would be very nice to get this fixed.

@docwilmot Did you have a theory on how to fix this, if I can find someone to work on it?

AlexHoebart-ICPDR commented 1 month ago

I had the same issue - "No pending updates" after database import (no other errors reported). I noticed that the database import did not finish as some tables were not present in the Backdrop database. I tried using upload database dump but had the same result. Then I removed some database views I had in the Drupal database. After this the database import finished and updates started. I ran now into another issue, so I cannot tell if the presence of custom views was the problem, but maybe it helps.

It would be good to have some error reporting about the database import in this module, then the issue would be easier to debug.