mollify problem upload rgiles in remote server

[GoogleCodeExporter]

in mt web server remote
upload in not possible
1. new directory is not 755 permission in automatic
2. after i put 755 on new directory and uload mt file 40 kb i am the problem, 
it is not upload
why? apache is setting 200mb on all

Original issue reported on code.google.com by alealeal...@gmail.com on 8 May 2011 at 12:03

[GoogleCodeExporter]

What is "rgiles" and "mt web server"? I'm sorry but with this info nobody can 
tell what's wrong.

You'd have to get some errors etc, see troubleshooting wiki

Original comment by samuli.j...@gmail.com on 8 May 2011 at 8:55

[GoogleCodeExporter]

i not see the errors
while upload is started the tha page is stop for hours
no error
if i restart the page i see the file in the directory but to 0 byte

Original comment by alealeal...@gmail.com on 9 May 2011 at 5:41

[GoogleCodeExporter]

Please pay attention. If you had actually read the troubleshooting wiki, you'd 
realize that you need to enable server debugging and get the log, that's where 
the error is.

Original comment by samuli.j...@gmail.com on 9 May 2011 at 6:10

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Good, but unfortunately these log entries don't have anything for the upload. 
You have to get the log after the upload fails.

But if you did, and it still does not show, then you have to get the log from 
the PHP error log file.

Original comment by samuli.j...@gmail.com on 9 May 2011 at 7:21

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

The same log entries will go into the PHP error log, if one is configured. It 
can be also in apache error log. But you'd have to check your PHP configuration 
where the log is written, and that you have actually enabled it.

Original comment by samuli.j...@gmail.com on 9 May 2011 at 7:24

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

sorry again
the error exact of IE slash position extactly:
impossible download files/ from www.mydomain

Original comment by alealeal...@gmail.com on 9 May 2011 at 7:43

[GoogleCodeExporter]

or perhaps I have not understood what I must make

Original comment by alealeal...@gmail.com on 9 May 2011 at 7:45

[GoogleCodeExporter]

perhaps I would have to see the logs of apache? ok I will have to ask the 
technician of the server
my server is shared 
I hope that it will answer me

Original comment by alealeal...@gmail.com on 9 May 2011 at 7:48

[GoogleCodeExporter]

mmmh
phpinfo? not well?

Original comment by alealeal...@gmail.com on 9 May 2011 at 7:50

[GoogleCodeExporter]

Now calm down, put some thought and effort to it before posting every question 
here. This is not a chat program, I'll respond whenever I have the time.

How does the IE error relate to the original problem? I haven't seen that error 
before so I have no idea, but I really suggest trying some other browser than 
IE. Anyway, let's keep this issue on the upload problem.

For the upload, you simply have to get the PHP error log. Otherwise I cannot 
help you, your service provider should be able to tell you where this is. Then 
just reproduce the problem and get the error log, and post here.

Original comment by samuli.j...@gmail.com on 9 May 2011 at 8:45

[GoogleCodeExporter]

I hope that "he" will answer me
"he" is the techinc man of my service provider
i know u respond whenever u have the time 
this is a forum

i ask him after post here

thanks
:)

Original comment by alealeal...@gmail.com on 9 May 2011 at 9:07

[GoogleCodeExporter]

the problem is similar to http://code.google.com/p/mollify/issues/detail?id=230

Original comment by alealeal...@gmail.com on 9 May 2011 at 10:00

[GoogleCodeExporter]

First, you should have mentioned that you use Plupload plugin.

For the other issue, without your debug log I can't see anything in common 
between the two issues except that upload fails.

In fact I doubt this is the same, because you say you get 0 byte file, in that 
other issue the problem was PHP trying to use wrong temp folder, which did not 
result in 0 byte file.

Original comment by samuli.j...@gmail.com on 9 May 2011 at 10:54

[GoogleCodeExporter]

ah ok
therefore it is not the temp directory
ok
i wait the answer from my service provider for php log

Original comment by alealeal...@gmail.com on 9 May 2011 at 12:57

[GoogleCodeExporter]

now PHP display_errors is active
now?

Original comment by alealeal...@gmail.com on 9 May 2011 at 4:14

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

This log is again from debug url (and not from error log file), and does not 
display anything regarding upload.

You need to find out in what file is the server log written, and post it here 
(or email to me). Display_errors setting does not matter, it only sets whether 
errors are shown in the browser or not, but it does not matter because upload 
errors are never shown in the browser.

Original comment by samuli.j...@gmail.com on 9 May 2011 at 5:00

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Sorry, don't understand the last question. You insist they what? And what can 
on a server shared?

Original comment by samuli.j...@gmail.com on 9 May 2011 at 7:10

[GoogleCodeExporter]

can i ask log error on a server shared?

Original comment by alealeal...@gmail.com on 9 May 2011 at 7:50

[GoogleCodeExporter]

for privacy my service provider can't to give me the php log error
how i think...
i dont know that i do.

Original comment by alealeal...@gmail.com on 10 May 2011 at 8:04

[GoogleCodeExporter]

Sounds like poor server strategy, logs should be written separately for each 
user.

But if this is the fact, I guess the options are
a) check the upload request (for example with Firefox+Firebug) that if it shows 
the error
b) try to change the log file location in Mollify

For option a, you'd have to have some knowledge about where to look and for 
what.

For option b, you could try adding these in r.php (right after php tag):

error_reporting(E_ALL);
ini_set('error_log','mollify.log');

Original comment by samuli.j...@gmail.com on 10 May 2011 at 9:06

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

i dont know to use firebug
:(

Original comment by alealeal...@gmail.com on 10 May 2011 at 10:34

[GoogleCodeExporter]

from phpinfo post here for differences between my local server and remote server
u say that?

Original comment by alealeal...@gmail.com on 10 May 2011 at 12:20

[GoogleCodeExporter]

in my web local server:
upload_tmp_dir 
C:\Programmi\EasyPHP-5.3.5.0\tmp\ 
C:\Programmi\EasyPHP-5.3.5.0\tmp\ 

in remote server:
upload_tmp_dir 
no value 
no value 

Original comment by alealeal...@gmail.com on 10 May 2011 at 12:31

[GoogleCodeExporter]

now is ok

change
open_basedir ....................../httpdocs/tmp"

upload_tmp_dir "..............httpdocs/tmp"

session.save_path ...................../httpdocs/tmp"

register_globals on

register_long_arrays on

safe_mode off

Original comment by alealeal...@gmail.com on 10 May 2011 at 12:59

[GoogleCodeExporter]

Sorry, I have hard time understanding your questions. Are you saying it works 
now?

Original comment by samuli.j...@gmail.com on 11 May 2011 at 5:42

[GoogleCodeExporter]

yes the problem it was in the settings of the php.ini on the remote server 
this thing could be useful to others
however since it works as I had intention I will donate 20 $ on the official 
site

Original comment by alealeal...@gmail.com on 11 May 2011 at 5:57

[GoogleCodeExporter]

That's great news! Still bit unsure what was the real error, but if it works, 
it's all that matters.

Original comment by samuli.j...@gmail.com on 11 May 2011 at 6:23

• Changed state: Invalid