There is no problem with feeds 7.x-2.0-alpha4. The problem is with feeds 7.x-2.0-alpha5. And that is the case for both this 7.x-1.3 version and the previous 7.x-1.2 version of commerce feeds. Also, there is no problem for any of the cases where the "Optional subdirectory" for commerce product images is not set.

When a product with an image field has the optional subdirectory set, at http://feeds.loc/admin/commerce/products/types/product/fields/field_image, feeds importer can't copy the downloaded images to the optional directory. Typical error for each image ..

The specified file temporary://fil2136.tmp could not be copied, because the destination directory is not properly configured .. a problem with file or directory permissions ..

The error message suggests a possible permissions problem but that's very unlikely. All perms are granted. Seems the folder location is not discovered.

Comments

rpmskret’s picture

rpmskret commented
Project: Commerce Feeds » Feeds
Version: 7.x-1.3 » 7.x-2.0-alpha5

I believe I have found the solution. It is just one extraneous "." in one of the feeds module files in the plugins directory.

Please see my post#5 in issues for the feeds module at http://drupal.org/node/1715662.

I am unsure how to "move" this bug report. I want to move it to feeds so I am entering Project: "Feeds" in the issue settings.

bluegeek9’s picture

bluegeek9 commented
Issue summary: View changes
Status: Active » Closed (outdated)

Drupal 7 reached end of life and the D7 version of Feeds is no longer being developed. To keep the issue queue focused on supported versions, we’re closing older D7 issues.

If you still have questions about using Feeds on Drupal 7, feel free to ask. While we won’t fix D7 bugs anymore, we’re happy to offer guidance to help you move forward. You can do so by opening (or reopening) a D7 issue, or by reaching out in the #feeds channel on Drupal Slack.

If this issue is still relevant for Drupal 10+, please open a follow-up issue or merge request with proposed changes. Contributions are always welcome!

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.