2

There is maybe a simpler path but this worked for me. Documenting this here since I don't know where else to put it.

2
  1. Start creating a new D8+civi site by using the installer at https://gitlab.com/roundearth/drupal-civicrm-project.

  2. When doing the D8 install part, just install a minimal site and don't further configure it - just what's needed to get D8 installed.

  3. Follow the standard drupal instructions to upgrade. https://www.drupal.org/docs/8/upgrade/upgrading-from-drupal-6-or-7-to-drupal-8. The short version is enable the Migrate UI module on the new site and then go to /upgrade.

  4. Do not enable civicrm yet.

  5. From your old site, export the civicrm_xxx tables.

  6. There is probably a better way to do this step but it worked for me to manually update any urls and paths in the export file (taking care with php-serialized strings) and then import the sql file into the new database. Note that any references to sites/all/modules/civicrm are now under vendor/civicrm/civicrm-core. URLs for sites/default/files/... can stay as is, but note that filepaths will now be web/sites/default/files. Also userFrameworkResourceURL is now libraries/civicrm.

  7. Copy civicrm.settings.php to the new site under web/sites/default. Edit the file: Change CIVICRM_UF from "Drupal" to "Drupal8". Change the mysql connection strings. Change paths and urls as above. Again note civicrm_root is now under vendor/civicrm/civicrm-core, and you need to put "web/" in front of filepaths to "sites/XXX".

  8. Enable the civicrm module.

  9. Clear caches at admin/config/development/performance and also the civicrm caches at civicrm/admin/setting/updateConfigBackend?reset=1. I also ran /civicrm/menu/rebuild?reset=1 but I'm not sure it's necessary here.

  10. The UI will look all messed up because it was a minimal drupal install but you can change the theme and set things as you normally would.

  11. You may also need to set these settings in civicrm.settings.php: $civicrm_setting['URL Preferences']['userFrameworkResourceURL'] = CIVICRM_UF_BASEURL . '/libraries/civicrm/'; $civicrm_paths['civicrm.root']['url'] = CIVICRM_UF_BASEURL . '/libraries/civicrm/'; $civicrm_setting['domain']['userFrameworkResourceURL'] = CIVICRM_UF_BASEURL . '/libraries/civicrm/'; $civicrm_paths['cms.root']['path'] = '/full/path/to/web'; // the "web" folder at the root of the install

  • It sounds like in step 6 you've got URLs going to vendor/civicrm/civicrm-core, but that typically isn't web-accessible. Maybe they should go to libraries/civicrm instead? – Jon G - Megaphone Tech Feb 26 at 19:03
  • 1
    Yes the urls should go to libraries/civicrm, but anything that previously pointed to the file path in the filesystem for sites/all/modules/civicrm now need to be vendor/civicrm/civicrm-core. I admit this isn't a detailed list of what settings to change. I'm thinking there must be a better way anyway since this would hopefully never be the official way to do it. Just this worked for me. – Demerit Feb 26 at 19:09
  • maybe creating this as a new entry in civicrm dev docs?: github.com/civicrm/civicrm-dev-docs – luciano_s Feb 27 at 16:27

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.