Closed (fixed)
Project:
File (Field) Paths
Version:
7.x-1.0-beta3
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
28 Feb 2012 at 03:35 UTC
Updated:
30 Apr 2013 at 23:10 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
rar9 commented+1 Same here when adding an D7 simple article
Comment #2
siteogra commented+1. Same problem. I'm use Mulutiupload Image Widget. Standart widget image from core work no stable.
Comment #3
callidryas commentedI, too, am experiencing the same issue:
Although, everything appears to work correctly. The images are renamed properly, but the error message is still displayed.
Comment #4
Tim Jones Toronto commented+1 Same here, tested with:
7.x-1.0-beta3 and 2012-Feb-09 dev version.
Used with Drupal 7.12
Thanks.
Comment #5
Bernsch commentedSame problem:
Undefined index: filefield_paths in filefield_paths_filefield_paths_process_file() (Zeile 45 von C:\wamp\www\drupal\sites\all\modules\filefield_paths\modules\filefield_paths.inc).I use:
Comment #6
David4514 commented+same here
simple add of a single file
Drupal 7.12
filefield_paths 7.x-1.0-beta3
Comment #7
David4514 commentedThe problem is that hook_filefield_paths_process_file() may be invoked for file or image fields where filefield settings have not been implemented. When that happens, the Undefined index for $instance['settings']['filefield_paths'] occurs.
A test should first be made to see if this value is set and not empty before executing the rest of the function.
The attached patch returns immediately if $instance['settings']['filefield_paths'] either does not exist or is empty.
Comment #8
alan d. commentedThe logic is probably right, but this should just be:
As a followup issue, these defaults should be set with the corresponding _info_alter() hook too.
Comment #9
alan d. commentedComment #10
alan d. commentedAnd the patch (without looking at field instance default values)
Comment #11
tarausa commentedI am experiencing the same problem, it looks as though now one knows how to fix it. It seams like to me the default page settings are not configured. I can not figure out how to fix that. The field path will cause problems with many other programs so until this is fixed I can not do anything further.
Comment #12
johnvThe patch works for me - it removes the notices.
Comment #13
edvanleeuwenTested and verified.
Comment #14
decipheredThis issue was fixed and committed a few days ago.
Comment #16
NenadP commentedGot this message on 7.14 when editing content type, and wsod... :(
Comment #17
flashwebcenterI had the same problem when I edit a content in 7.14 and filefield_paths 7.x-1.0-beta3. Thank you David4514 and Alan D.
Comment #18
hejazee commentedThis problem still persists in 7.x-1.0-beta3
#10 works fine
Comment #19
Bernsch commented#10 works for me too! Thanx!
Comment #20
decipheredPlease don't re-open fixed issues unless you confirm that they're not working with the latest dev (not beta or stable).
As said, a fix for this issue has already been committed.
Comment #21
Po3t commentedHi, I'm getting this error as well with beta3. There hasn't been a new version released since February 7th, 2012. Any chance we can get a new release soon?
Comment #22
plazik commentedPo3t, you can use dev version.
It works for me.
Comment #23
finex commentedThe bug is still reproducible using 7.x-1.0-beta4 and Drupal 7.22
Comment #24
deciphered@FiNeX,
Can't be, not at all possible.
Firstly, there's no code on line #45, so if you're getting the same error as this issue you aren't using beta4.
If you aren't getting this exact error, but similar, you couldn't be either, because if you look at line #47 (http://drupalcode.org/project/filefield_paths.git/blob/refs/heads/7.x-1....) there is a check to see if that value is set before proceeding, therefore preventing said error.
I suspect if you are getting an error, it can't be the same error and is probably unrelated to this issue, in which case can you open a new issue with the details of the specific error you are getting.
If you are absolutely getting the same error, then you aren't using beta4, not possible.