Jump to:
| Project: | Multiple Image Upload |
| Version: | 6.x-2.1 |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | closed (duplicate) |
Issue Summary
Hello,
I just installed the postlet module for drupal : Installation Ok, the upload page in dispaying link in the add image page, and the applet is correctly loaded. When i add files they are corctly diplayed and the upload button seems to work...
BUT after upload, nothing append : the progress bar ended and... just nothing ! no file uploded nowhere and no more action frome imagex module.
i also have "The selected file /xxx/xxx could not be uploaded, because the destination is not properly configured." error when i access image galleries.
My question is : is there a configuratino file or page that have to be configured to tell to imagex where tu put the uploded files ? Because it seems to be the problem !
I need some help ! I will also post in drupal Forums.
Regards,
Vincent
Comments
#1
I also post here : http://sourceforge.net/projects/postlet/forums/forum/553003/topic/3430935
In the sourceforge forum postlet project.
Please help !
This module is just perfect for Drupal users !
Regards,
Vincent
#2
I tried to modify tmp directory, as it was said in Drupal 5 issues... but not working...
May be imagex want to create its own tmp directories at the root of my web server...
BUT i think it is not a good idea to have the web root with write access !
Vincent
#3
i tried your imagex SVN here : http://svn.scratchpads.eu/svn/scratchpads/branches/drupal6/sites/all/mod...
but same problem...
Note that after upload progress bar ended, i have the following message : "The following images have been uploaded by you in the last hour." but nothing below...
Help definitively needed !
Thanks,
Vincent
#4
I'm having exactly the same problem. I keep looking for somewhere to configure the destination directory and wonder if I'm doing something wrong. Has anyone managed to correct this?
Thanks,
Scott
#5
Hello,
no news...
:o((
#6
It's because Drupal can't write .htaccess file to sites/default/files (or your files folder) and you must do next: Set 775 rights to sites/default/files folder. Drupal will write there .htaccess file with next content:
SetHandler Drupal_Security_Do_Not_Remove_See_SA_2006_006
Options None
Options +FollowSymLinks
Sorry for my english.
#7
It's not a permission issue, not for me at least.
I have tried to change temp directory, but still I can not trace this problem :(
#8
Does it work when you try to upload a single image manually using the node/add/image form?
#9
I'm having the same issue. Here's what gets spit out in the Java 1.6.0_18 console:
POSTLET VERSION: 0.15
2008-05-13 16:34:40 +0100 (Tue, 13 May 2008)
*** maxfilesize is not a number ***
*** proxy is null ***
*** endpage is badly formed:###null### ***
*** helppage is badly formed:###null### ***
*** failedfilemessage is null ***
*** maxpixels is not a number ***
*** setting the tables colours ***
*** Adding button ***
*** Windows D'n'D ***
*** Enabling the upload and remove buttons ***
*** Windows D'n'D ***
*** Enabling the upload and remove buttons ***
*** could not retrieve proxy configuration, attempting direct connection. *** (4 times)
*** Unable to send status to Javascript *** (99 times)
*** REPLY ***
*** ***
*** END REPLY ***
*** REPLY ***
*** ***
*** END REPLY ***
*** REPLY ***
*** ***
*** END REPLY ***
*** REPLY ***
*** ***
*** END REPLY ***
*** Unable to send status to Javascript ***
*** Executing: postletFinished(); ***
#10
What browser/OS are you using Dan?
#11
I believe this is a duplicate of #407644: Error: destination is not properly configured.
Note bramilo's comment:
#12
I think this permission thing is a fundamental Drupal problem and module independent, which even worsens if your hosting company moves your site from one server to another for any reason. All permissions will then be completely messed up. I spent 3 awfully frustrating weeks to understand and get it all kindof working again, and still only to half of the websites original state...
But this stupid /tmp (or tmp - at the end it's absolutely not clear) is still breaking many of Drupal's functionallities. Right now at admin/settings/file-system I get:
1. The selected file /tmp/filewBARyE could not be uploaded, because the destination is not properly configured.
2. warning: fopen(sites/default/files/.htaccess) [function.fopen]: failed to open stream: Permission denied in /whatever1/whatever2/domains/mydomain.com/public_html/includes/file.inc on line 129.
3. Security warning: Couldn't write .htaccess file. Please create a .htaccess file in your sites/default/files directory which contains the following lines:
SetHandler Drupal_Security_Do_Not_Remove_See_SA_2006_006
Options None
Options +FollowSymLinks
Number 1 is clearly the MOST despairing message.
Firstly because you never know (and I haven't seen any good explanation on this) if the "/" of "/tmp" means:
- in the root of your server - in other words: C:/tmp, D:/tmp or whatever letter your hardisk has,
- or if it means in the root of the current domain - in other words: /domains/yourdomain.com/tmp
- or if it means in the root of the navigatable part of your domain - in other words /domains/yourdomain.com/public_html/tmp
- or is "root" just an irrelevant and erroneous indication and does it want to say just in the same folder - in other words: /domains/yourdomain.com/public_html/includes/tmp
And secondly because even if you create each of those "tmp", just to make sure, and even giving them CHMOD 777, you still get this stupid error message and malfunctioning of my webs.
Changing "/tmp" to "tmp" as #11 says, DOES NOT make any difference either.
Getting errors 2 and 3 at the same time makes one seriously doubt about the credibility of Drupal's messages or you start doubting about yourself. Because the permission IS CHMODed 777 (error 2) AND there IS "a .htaccess file in your sites/default/files directory which contains the following lines bla bla bla....."
I have seen dozens of messages of desperate people because of this /tmp and permission errors for a variety of modules, so maybe someone at Drupal top would like to consider to dedicate some real clear explanation on this. It could help stop people loosing weeks of their lifetime or stop people from just forgetting about Drupal at all.
#13
I've been looking for a simple mass-upload tool like this for a while now, and this is the only one so far that I like from the non-technical user's UI perspective. The temp directory on my site had been set to:
"sites/(sitename)/tmp" (without quotation marks) under admin>settings>file-system, which is how I prefer to set up all Drupal site installations on my server.
I went ahead and changed this to "/tmp" (without quotation marks) and it started working as expected.
I agree with @suffering drupal's assessment that the usage of tmp, /tmp and sites/(sitename)/tmp is rather unlcear. Some details on which /tmp folder is being referenced within the module itself would be helpful.
#14
I had a similiar problem but it wasn't related to this module. I had copied our production site over to a SUSE local installation and setup a Drupal VM for development purposes. The site worked and then I followed the upgrade instructions and then ran into "The selected file could not be uploaded ..."
What I ended up doing to fix it was I compared the group and owner of the files located in /tmp to sites/default/files and noticed that my tmp files were owned by wwwrun group www. So I then changed the owner of the files directory to wwwrun group www that did it. I also did that to all the underlying files. Now all new files have that same ownership, and everything works. I think if you situation is different it's probably related to permissions. Keep in mind I did what all of you did and granted full permissions on the file directory with no success. So weird. The ownership turned out to be key for me. Hope that helps, good luck.