- 🇳🇱Netherlands megachriz
Do you have any additional file related modules installed? It has been reported before that one messed things up for Feeds. I don't remember which module it exactly was, but it could be that it was "File Entity".
- 🇳🇱Netherlands megachriz
I see that this happens when the configured upload directory on the feed type is not writable.
Go to your feed type, and on "Fetcher settings", check which upload directory you have configured there. Then check if the file permissions on your system are set correctly for that directory. Or the parent directory if the directory does not exist yet. If it is set to "private://feeds" (the default), then your site may have an issue with writing files to the private file system. If it is set to "public://feeds" (the default if there is no private file system), then there is an issue with the public file system instead. You can see on /admin/config/media/file-system which directories are used for the public and private file system.
As for the log message, this is caused by a bug in Drupal Core: #1903010: Notice: Undefined index: #field_name in file_managed_file_save_upload() → .
Automatically closed - issue fixed for 2 weeks with no activity.
- 🇬🇧United Kingdom mcswann
This may be totally the wrong way to do this but posting my solution here incase it helps/someone can correct me.
I am running my drupal 10 site using ddev on macOS. This did turn out to be a file permission/ownership issue.
To check permissions with the default public file system, run
ddev ssh
cd /var/www/html/web/sites/default/files
ls -la
Which outputted:
drwxr-xr-x 10 [username] dialout 320 Nov 10 13:36 . drwxr-xr-x 8 [username] dialout 256 Nov 10 13:28 .. -r--r--r-- 1 [username] dialout 486 Nov 9 14:42 .htaccess drwxrwxr-x 3 [username] dialout 96 Nov 10 13:18 2024-11 drwxrwxr-x 58 [username] dialout 1856 Nov 10 14:01 css drwxrwxr-x 5 root root 160 Nov 10 15:37 feeds drwxrwxr-x 50 [username] dialout 1600 Nov 10 14:01 js drwxrwxrwx 2 [username] dialout 64 Nov 9 15:43 php drwxrwxr-x 3 [username] dialout 96 Nov 10 13:18 styles drwxr-xr-x 3 [username] dialout 96 Nov 9 14:42 sync
For some reason the automatically generated feeds directory is owned by root instead of [username] like the others ([username] as a placeholder for my actual username).
chat gpt gave me this code to run
sudo chown -R [username]:dialout /var/www/html/web/sites/default/files/feeds
again replacing [username] with your actual userI believe dialout isn't actually essential here but it matched the others for me so i figured it made sense to keep it.
I'm not sure if this is going to give me trouble down the line/there's something more fundamentally wrong with my setup but it got me up and running so I'm going to consider it a win.