Forums
This topic is locked
DW and putting perl modules
Posted 05 May 2005 19:40:15
1
has voted
05 May 2005 19:40:15 Jessica Alvarez posted:
Hello,I am the web designer/webmaster who knows just enough cgi to make me dangerous. I have a developer who is working on our perl module/cgi ordering system. He is working remotely from another state. Last night I noticed changes to our script which overwrote an old fix and reinstated an old problem.
I "got" the file from the remote server (called order_form.pm), fixed one line of code, and "put" the file back on the remote server. This resulted in internal server error upon use of the html form. I checked the permissions with an extension built to do that and found that "execute" was not checked. I placed checkmarks in the execute column and the internal server error still occurred.
This is about the second or third time this has happened, on two different sites I maintain.
What settings can I change to be able to successfully "put" files with extensions of .pl and .pm? I have set DW to open these types of files in code view.
--
Jessica
Replies
Replied 05 May 2005 20:09:17
05 May 2005 20:09:17 Jessica Alvarez replied:
I posted a bit prematurely; I was able to fix my problem just now. Sorry for any inconveniences. I checked my hosting company's control panel, where I have access to the error log. This error log detailed the problem for me and it was entirely my fault for sloppy code.
Besides my syntax errors, this was also generated: Premature end of script headers: path to my orderform.pm file.
Anyone know how this happens, or what causes premature end of script headers?
--
Jessica
Besides my syntax errors, this was also generated: Premature end of script headers: path to my orderform.pm file.
Anyone know how this happens, or what causes premature end of script headers?
--
Jessica