Critical Error- Destination directory.............. Critical Error- Destination directory..............
 

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Main Menu

Critical Error- Destination directory..............

Started by topgear, February 05, 2005, 10:31:37 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

topgear

i get this error message when trying to post photos up, it was working fine before. i have just been told by someone that its not working. the last time it was working was friday night.

the error message is.........

Destination directory modules/coppermine/albums/userpics/10002/ is not writable by the script !

i have checked the permissions. they were on 755 and i put them to 777 but it still didnt work.

topgear

just thought i would add something............

the folder name, 10002 (numbers on the end). it doesnt matter which one it is, it doesnt work for any of them.

kegobeer

Do not send me a private message unless I ask for one.  Make your post public so everyone can benefit.

There are no stupid questions
But there are a LOT of inquisitive idiots

Kitelife

#3
I'm getting the same issue...

I upgraded successsfuly to 1.3.2... Everything looks gravy, except:

1.  The files upload okay iniitially (presuumably to the "edit" folder)...
2.  On the following page where you can enter title, etc, the photo shows okay...
3.  When I click the button to finalize the addition and photo description, I still get this message:

  Destination directory albums/userpics/10006/ is not writable by the script !

Again, I've already played with the permissions on both 755 and 777 as well.

(not using any ports or integration with other scripts)

Kitelife

Sorry to be impatient, but this issue is becoming a concern for us...

I wonder if this problem is a result of the recent upgrade of PHP implemented by a number of hosting companies? 

I don't have the technical knowledge to figure it out, but that is the only thing I've seen that correlates with the dates that this quirk began.

Help!  :-[

Casper

Have you tried the 'SILLY_SAFE_MODE' as per the docs 'safe mode issues'.
It has been a long time now since I did my little bit here, and have done no coding or any other such stuff since. I'm back to being a noob here

Kitelife