Please forgive me for not going the canonical path with either Drush or Composer. I tried, but could not find documentation to get me started. I'm coming from a Debian installation of Drupal 7 that used Debian packages.

I have had bad experiences with skipping major releases with several software product, so I did not want to skip from Drupal 7 to 9. Please correct me if you think this is a bad idea. So I downloaded the latest Drupal 8 tarball and installed that. I configured a basic site and started .../upgrade.

Most of the migration went OK, but I could not get it to import the files from Drupal 7. I had kept them in /var/lib/drupal6/files. The log mentioned files, but with the path like //varlibdrupal6filessomething.jpeg. So I copied the files to / with the prefixed name, but no dice.

I can't find why there is a lot of error messages (but less than one per file) like this:

Source ID 1022: Could not create or write to directory 'private:'

I straced apache but could not find anything that looked like a problem with the private files path. The top level directory is owned by www-data:www-data is is set to 0777 anyway. The strace does not show any access involving that directory, accept for a few to PHP files like this:


The apache access.log shows this: - - [14/Mar/2022:21:13:37 +0100] "POST /buexeCMS8/node/add/rezept?element_parents=upload/widget&ajax_form=1&_wrapper_format=drupal_ajax&_wrapper_format=drupal_ajax HTTP/1.1" 200 6292 "https://drudev.lupe-christoph.de/buexeCMS8/node/add/rezept" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:98.0) Gecko/20100101 Firefox/98.0"

So it looks like it the POST has succeeded. Except it hasn't.

I tried diving into the PHP code but had to give up when I got to a file with very complex Entity-related code.

I installed the File (Field) Paths module and built a new content type using both the old and the new File widgets. The old one refuses to upload, the new one presumably using File (Field) Paths, does its job.

Now I'm completely confused, and have no idea where to look next. Any nudge in the hopefully right direction would be very welcome.

  • 3
    It is a bad idea to migrate to Drupal 8. It is end of life. You are only making more work for yourself. Composer codebase install is well documented and is a single command drupal.org/docs/develop/using-composer/…. You will cause yourself many problems by choosing not to use Composer.
    – cilefen
    Mar 14, 2022 at 20:53
  • Sorry, I did not get composer to work for me. As for more work - as I said, I'm paranoid about version skips. But I'll keep Drupal 9 as a last resort if I can't get the migration to Drupal 8 to work. Right now I'm looking for help importing those files.
    – Arture
    Mar 14, 2022 at 23:56
  • Drupal 9 IS Drupal 8 with some deprecated code cleanup. Also the migration tools continue to be improved, so Drupal 9.3 should have less buggy migration than any release of Drupal 8. As cilefen said, composer is the way forward and you are unlikely to get support by saying composer did not work for you. Please take a second look at composer; it is very likely to pay off for you in the long run if you continue to do PHP development. Mar 15, 2022 at 1:15
  • 1
    You directly asked for advice on these matters. Please listen. I’ve seen a lot of people who “know better” and decided to go their own way with these things and that decision cost them time and money.
    – cilefen
    Mar 15, 2022 at 2:32
  • OK, I'll try to migrate to Drupal 9. More when I'm stuck or done. Thanks for explaining the relation of 8 and 9. Given the huge step from 7 to 8, I expected a similar step between 8 and 9. I don't think I "know better", it's just that I've been burned quite a few times by trying to take two steps at once.
    – Arture
    Mar 15, 2022 at 12:46


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Browse other questions tagged or ask your own question.