File upload and browse server not working for me

Pinelli, Thierryfrom Nice, Drap Associate, 1740 posts	on May 4 2008 What editor use you? (FCK or TINYMCE ?) Have you chek your chmod rights ? Testing 707 for section and article directory (Sorry for my bad english ) Un annuaire propulsé par YACS - Skins pour Yacs : YordPress - Yacs couleurs Wordpress - Bonbon Skin 1.3.2 : Le graphisme "Green" - Totem 930 : L'équilibre pour petits écrans Communiqués de Presse : Site de Communiqués de Presse à propulsion Yacs - Création de sites, Référencement et webmastering - Skins pour Yacs : YordPress - Yacs couleurs Wordpress - Bonbon Skin 1.3.2 : Le graphisme "Green" - Totem 930 : L'équilibre pour petits écrans
Moore Hazel 5 posts	inspired from ThierryP on May 5 2008 ThierryP: Thank you for your reply. I have checked my permissions and they seem to be fine, not willing to alter them to allow global write as I'm on a shared server. If I have to change permissions to 777 or 666 then I'll have to use another CMS, tried 707 and nothing worked. This is happening on FckEditor and YACS editor, I don't use the TextEditor. No one can add images or browse server for existing images including Admins. Only way I can get images on to the server is via FTP. Any suggestions would be very welcome.
Vincentfrom on-a-few-hops-from-you 23 posts	on Aug. 29 2008 Hi there, i got the same problem on the shared server, no uploading or staging possible - "No file has been transferred". The same yacs (8.6beta30.31.12) version on my own server does not pose the problem, my gut says it is something to do with the right of the user (via php?) on the shared server. BTW did a chmod 777 on articles to rule out the obvious. php says its upload limit is 2M and so does yacs. I even set the uploaded files rights to 777 in case they are kept in some 'tmp' area before being moved to the proper dir. To no avail :( Anyone found a solution for this? thank you, Vincent
Vincentfrom on-a-few-hops-from-you 23 posts	on Aug. 29 2008 Hi there, i got the same problem on the shared server, no uploading or staging possible - "No file has been transferred". The same yacs (8.6beta30.31.12) version on my own server does not pose the problem, my gut says it is something to do with the right of the user (via php?) on the shared server. BTW did a chmod 777 on articles to rule out the obvious. php says its upload limit is 2M and so does yacs. I even set the uploaded files rights to 777 in case they are kept in some 'tmp' area before being moved to the proper dir. To no avail :( Anyone found a solution for this? thank you, Vincent
Vincentfrom on-a-few-hops-from-you 23 posts	inspired from vincent on Aug. 30 2008 -- sorry for the double posting there. Meanwhile, i tried the same yacs on another domain at the same provider, and there was no trouble to upload stuff. So my guess is now that the problem has to be with the provider. I could not found any limitation in upload size in all the config files - is there (do i miss something very obvious)? The current stable (8.3beta31.1) gives a slightly different error: 'It is likely file size goes beyond the limit displayed in upload form. Nothing has been transmitted for email.png' I'll hope to have contact with this provider soon, and will post the solution. Vincent
Vincentfrom on-a-few-hops-from-you 23 posts	inspired from vincent on Aug. 30 2008 So installing the latest version again (see up). All is 777 by now :( Created a file collection: "uploads-area" and the corresponding folder. Here is the reply after "upload a file" ==== Home « File collections « uploads-area Nothing has been received. Impossible to read . ==== Now i wonder what "." is -current dir- is after all also 777 .
Vincentfrom on-a-few-hops-from-you 23 posts	on Sep. 1 2008 Two things jumped up at the provider: the php tmp_dir variable was not set in the php.ini, so no temp dir to upload for php. The owner of the files is not the owner of the process :( this means a lot of hassle or wide open files (hence the advised 707 from the readme.txt) + the above mentioned 'same' server appeared a cluster of servers; therefore YACS worked on the one site but not on the other site, as they were on different machines.