Feeds bug do not move to folder

I am not familiar with importing feeds, so it is a bit hard for me to set up a test (I also don't know the specific module(s) you are using). However, I have a few thoughts.

When uploading a new file with FFP enabled, it is uploaded to the root folder, like you mention. After saving, FFP will move the file to the correct tokenised folder path. By default, FFP will only move newly uploaded files. If you enable 'Active Updating', it will ensure all the fields files are at the correct path.

The problem may lie within the way the nodes are created during the feed import. My first thought is that feed import is not giving the files the current date, but the date they were uploaded to the 'feed' site (ie, they are not flagged as new). Enabling 'active updating' may solve this.

My second thought is perhaps the feed import isn't doing a proper node_save, hence FFP doesn't get a chance to move the files. This would need more investigation if my first suggestion doesn't work.

Just going to switch this to support request until we can find some actual FFP code that needs fixing.

I have just closed some related issues, and hence will stick will stick this back to bug report as it does appear there are some issues using FFP in conjunction with Feed Import, although I still wonder if enabling 'Active Updating' will solve it.

#2104047: Feed Replace feature ommited with pathauto cleanup
#2188131: Feeds + Drush = not rewritten

And an old related issue that was closed as cannot reproduce and was noted as may be fixed in beta-4 (although apparently not...).
#1464172: Feed import module

If anyone can provide some exact steps on reproducing this error on a new drupal install with only FFP and Feeds Import modules, and an online demo feed, that would help.

This will require some further testing, but my gut feeling is that either FFP isn't being triggered during the Feeds Node/Entity creation process either due to the relevant hooks not being implemented or the relevant hooks being invoked.

Unfortunately issues like this take time to test as I need to configure a site in such a way that I am able to reproduce the issue, and when I'm not familiar enough with the exact modules or the required configuration it can often be more time than I have available.

The best thing that can be done to help resolve this issue is to either:
- Provide me access to an existing sandbox site that is configured correctly and that can 100% reproduce the issue (with some basic steps)
- Create a makefile/features/profile/distro based setup so I can quickly get my own pre-configured sandbox up and running
- Provide really good, easy to follow steps on how to setup a site from a fresh Drupal install

I know this can be a lot of work for someone to do, but it increases the chances of a fix.

Cheers,
Deciphered.

I am using the feeds module (7.x-2.0-alpha8) to import images and have set the file field path on my content type to "accommodation" (no other file field path settings such as path auto was selected) and the images have been pushed into that folder correctly when importing the content.

Really should make sure you re-activate tasks once providing updated information, otherwise it may get missed.

I have tested with the latest dev release and this is no longer an issue, atleast based on my testing.