Closed (fixed)
Project:
Patch manager
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
18 Jun 2010 at 22:04 UTC
Updated:
1 Sep 2010 at 09:40 UTC
I get the following error when I try to set the patch file storage path to sites/all/patches
* warning: mkdir() [function.mkdir]: No such file or directory in /var/www/mysite/sites/all/modules/patch_manager/patch_manager.module on line 139.
* Unable to create patch pathI do get a success message:
The configuration options have been saved.
... and the path setting seems to be retained when I revisit the configuration (admin/build/patch). Still the warning is there and might confuse users.
Comments
Comment #1
klonosping?
Comment #2
aidanlis commentedFixed in the new release.
Comment #3
klonosIn previous dev versions I see a 'Patch file storage path:' field available in the module's settings page (../admin/build/patch/configure). Now, all I see is a 'Patch binary path:' that defaults to
/usr/bin/patch.Where is the option to select path of stored patches? Is it hardcoded? If yes does it default to
sites/all/patchesor what? Am I missing something?Comment #4
aidanlis commentedYou can set this now by editing the CCK field, which makes it much more flexible and will work with other modules like filefield_*.
Comment #5
klonos...I just realized what you mean. One has to edit the 'Patch' content type's field_patch CCK field in ../admin/content/types/patch/fields/field_patch in the 'Path settings' fieldset (defaults to
sites/default/files/patchesand has tokens support!).We definitely need documentation.
Comment #6
klonos...still, it wouldn't hurt to have a setting in the module's configuration page. It's the first place people look for setting options like this one.