Loading Profile...
Upload Directory Problem
Using Wordpress, I keep getting the following error: "Your image upload directory () is not writable. Zemanta cannot upload images there."
What is the path to this image upload directory, as I have tried to alter the attributes to all the directories I could think of.
Please advise, thank you.
Regards
Michael
What is the path to this image upload directory, as I have tried to alter the attributes to all the directories I could think of.
Please advise, thank you.
Regards
Michael
I’m confused
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company marked this problem solved.
-
Inappropriate?Hi Michael
Go to to your WordPress dashboard and select Plugins -> Zemanta Configuration.
Under "Image uploading" there's a box with the path to the directory you need to make writable by the user that your Wordpress installation runs as.1 Comment
Add a comment
This solves the problem
-
Thank you Tomaž for your suggestion.
I have tried to follow directions but still fail :o|
If I call the directory 'zemanta' and place it like this: http://domain.com/zemanta - then I guess what to fill in the 'URL' field should be http://domain.com/zemanta.
But what am I to fill in the 'path' field? (The attributes of zemanta directory is set to 777)
Michael -
Inappropriate?The path "Uploader should save images to this directory" should be the absolute filesystem path of the directory that appears at the URL http://domain.com/zemanta.
This is usually the document root directory + "zemanta". For example, if document root is "/var/www/domain", then the correct path is "/var/www/domain/zemanta".
If you don't know what the document root is, try disabling the "use custom path" checkbox and look at the default paths. If you WP installation is accessible directly at http://domain.com, document root is the part of the path that appears before "wp-content".
By the way, why are you using a custom path? Default didn't work for you?
2 people say
this solves the problem
1 Comment Add a comment
This solves the problem
-
I >did< use a custom path because default didn't work for me.
That was the sentence that gave me the clue, what could be wrong.
The blog has recently been moved from an other server, and the default path (in MMiscellaneous Settings) was pointing back to the old hosting account.
Setting the path to default solved the problem.
Thank you for your kind help. You have been great.
EMPLOYEE
