I'm using W2k3, php5, mysql4 and apache2.
I just installed drupal and have everything working fine. I've set all of the general settings (with no errors), added/configured modules etc...
I dl'ed and installed filemanager, attachment, and acidfree.
filemanager installed/configured with no errors
attachment (same)
acidfree (same)
I run the acid free test and everything passes except 7.
System file path not properly set or permissions are not right (must be web writeable). Go to admin/settings to configure it.
Drupal doesn't complain about the path, but acidfree's test does.
I haven't tried to create any content yet until i fix the error.
The files system path is c:/progra~1/apache~1/apache2/files
In filemanager:
public path is just - files
private path is c:/progra~1/apache~1/apache2/files/private
Also, i've changed the paths and switched from public to private many times, trying to figure this out.
There is no content, so i'm hoping that hasn't caused a problem.
If you can't tell, i'm a noob, so any help would be appreciated.
I've searched the forums and read everything i can find that is related.
thanks in advance
btw - the site is http://skri11a.servebeer.com/drupal
Comments
try creating the directory yourself
I think I have seen this problem with other windows installs. I am not sure why, but for some reason, the directory doesn't get created on its own.
mkdir c:/progra~1/apache~1/apache2/files/acidfree
mkdir c:/progra~1/apache~1/apache2/files/acidfree/tmp
And then make sure they are web writeable. Then go see if problem 7 goes away.
More ideas?
You are correct. The directories did not get created.
Mine is a windows install. I do not have shell access. Php is in safemode and I can't change it. I am not a programmer and am trying to figure this out as go.
I created the directories per your instructions and made them web writeable with my FTP client. Prior to changing the permissions, Acidfree test had a red box at the top of the page that said "Files is not webwriteable". That box is no longer there after I changed the permissions of the Files directory, the Files/Acidfree directory, and the Files/Acidfree/tmp directory. Acidfree test still reports a system path problem #7.
Also, Watchdog is reporting these errors when I go to Acidfree test:
is_dir(): Stat failed for /.../files/acidfree (errno=13 - Permission denied) in /.../modules/acidfree/acidfree.module on line 1554.
mkdir(/home/pcwick/public_html/files/acidfree): Permission denied in /.../modules/acidfree/acidfree.module on line 1558.
Any more ideas about how I can make Acidfree happy?
Thanks for the reply...
I tried what you suggested (the folders were not created), and i made the folders web writable. This still did not fix the problem.
It still fails at step 7.
I also tried just ignoring it and tried to upload a picture. The album created, but when i upload a picture, it shows a new picture with a pretty red X.
If i upload a mov, it just dumps me back to the add content screen without doing anything.
In either case, it does not copy the file to the acidfree dir.
Any other ideas? I'm a willing test subject.
Got it working
Well, I went ahead and built a LAMP server to try and avoid the windows insconsistencies. Unfortunately, I ran into the same problem.
The good news is, manually creating the folders worked once i chmod 777 acidfree/tmp... (out of curiosity, what exactly is the chmod for a web writable folder?)
After that almost everything worked beautifully. "Almost", because i still can't get mass upload to work. I have no idea why it doesn't work. I upload a .zip and it tries but just drops me back to the upload screen.
I tried firefox and ie just to see if something was different between the two in that sense, but they reacted the same.
Thanks for helping me get acidfree usable, i like everything about it.... oh... :-) .... one thing that would be nice, is the ability to turn off user picture for acidfree elements. it looks kinda funny with the user picture hovering around the album page.. imo...
Thanks again vhmauery for this module and all your help...
I had this exact same
I had this exact same problem myself. I'm not sure how it went away, but it did. I think it happened when I uploaded a photograph just to see what would happen. The problem with that is that acidfree made directories in the files directory that I can't get to via my ftp client. I had to ask the webhoster to change the permissions on them for me, but I don't remember what they are now...