Ok, i knew I will eventually get this to work and I did and I exactly know why.
It makes alot of difference if your using a good FTP client which I found out the hard way. WS_FTP don't cut it and also some other free FTP clients since they are poorly structured and so on. BulletProof FTP might be a good one. Any who, I only had to upload my files once with CuteFTP and it immediately worked. Amazing, I was about to freak out.
I guess what happens when your script reads premature etc etc in the error logs, it means your script is probably corupted and useless and you would have to upload the script again. Making sure you have a FTP client that wont curupt your script during its upload to your server via ACSII. Don't upload your script via Binary.
What it all comes down to when uploading your scripts to your cgi folder is to relize that having a decent FTP client plays a large role. Upload scripts,html files in ACSII and pictures in Binary mode.
I can say this, I got help with this and figure some stuff out. I just want to pass it along to other people to help them.
I hope this does help and remeber, WS_FTP sucks big time.
Also remember to chmod your files to the correct permissions. I would say 755 is the most commonly used. But perl scripts usually comes with ReadMe files which tell you what to do.
As to add to another note, make sure your text editor you are using wont mess up your script. I found a script call Arachnophilia to be useful and free and useful.
Full Version: I figured CGI and Perl out. This might help you,
QUOTE
Originally posted by dnsprotocol
Ok, i knew I will eventually get this to work and I did and I exactly know why.
It makes alot of difference if your using a good FTP client which I found out the hard way. WS_FTP don't cut it and also some other free FTP clients since they are poorly structured and so on. BulletProof FTP might be a good one. Any who, I only had to upload my files once with CuteFTP and it immediately worked. Amazing, I was about to freak out.
I guess what happens when your script reads premature etc etc in the error logs, it means your script is probably corupted and useless and you would have to upload the script again. Making sure you have a FTP client that wont curupt your script during its upload to your server via ACSII. Don't upload your script via Binary.
What it all comes down to when uploading your scripts to your cgi folder is to relize that having a decent FTP client plays a large role. Upload scripts,html files in ACSII and pictures in Binary mode.
I can say this, I got help with this and figure some stuff out. I just want to pass it along to other people to help them.
I hope this does help and remeber, WS_FTP sucks big time.
Also remember to chmod your files to the correct permissions. I would say 755 is the most commonly used. But perl scripts usually comes with ReadMe files which tell you what to do.
As to add to another note, make sure your text editor you are using wont mess up your script. I found a script call Arachnophilia to be useful and free and useful.
Ok, i knew I will eventually get this to work and I did and I exactly know why.
It makes alot of difference if your using a good FTP client which I found out the hard way. WS_FTP don't cut it and also some other free FTP clients since they are poorly structured and so on. BulletProof FTP might be a good one. Any who, I only had to upload my files once with CuteFTP and it immediately worked. Amazing, I was about to freak out.
I guess what happens when your script reads premature etc etc in the error logs, it means your script is probably corupted and useless and you would have to upload the script again. Making sure you have a FTP client that wont curupt your script during its upload to your server via ACSII. Don't upload your script via Binary.
What it all comes down to when uploading your scripts to your cgi folder is to relize that having a decent FTP client plays a large role. Upload scripts,html files in ACSII and pictures in Binary mode.
I can say this, I got help with this and figure some stuff out. I just want to pass it along to other people to help them.
I hope this does help and remeber, WS_FTP sucks big time.
Also remember to chmod your files to the correct permissions. I would say 755 is the most commonly used. But perl scripts usually comes with ReadMe files which tell you what to do.
As to add to another note, make sure your text editor you are using wont mess up your script. I found a script call Arachnophilia to be useful and free and useful.
That is ridiculous! WS_FTP is one of the best ftp clients you can use. Its a different matter when you dont know the difference between uploading cgi/pl/asci/txt/doc/gif/jpeg/php/inc in the appropriat format. Its not up to ws_ftp to determine this. Its up to the uploader to select the format. I'm not sure which version your using but if you were up to date and using the latest version which is 7.04 then you wouldnt even need to think about that. The latest version automatically senses the file extension and takes the appropriate measure to upload it in the correct format, ascii as opposed to binary. The the older version of ws_ftp in the option area you simply define everthing that is ascii using the extensions and select auto during your uploads. Ws_ftp will then upload binary and ascii correctly. Now in the latest version those buttons are gone and its done automatically for you. So get the latest version ok.
Unless of course he was using WS_FTP LE which is no where near as good as Pro.
Anyway in Pro you can tell it that anything with a .pl or .cgi, etc to be uploaded as ASCII all the time... thus colves your problem.
Anyway in Pro you can tell it that anything with a .pl or .cgi, etc to be uploaded as ASCII all the time... thus colves your problem.
In WS_FTP LE, under Extensions, you can specify which extensions are ASCII.
The reason for the binary vs. ASCII issue is simply that Windows, Macintosh, and Unix based system all use a different method of ending lines in text files, so in order for it to show up as a normal text file on the other system, the line ending has to be changed to the appropriate format. If the transfer is between two systems of the same type, then binary would work too.
The reason for the binary vs. ASCII issue is simply that Windows, Macintosh, and Unix based system all use a different method of ending lines in text files, so in order for it to show up as a normal text file on the other system, the line ending has to be changed to the appropriate format. If the transfer is between two systems of the same type, then binary would work too.
Here my Favorites:
FTP: CuteFTP Pro
File Management/ Packed Files /FTP on Windows: Windows Commander
Editing (PHP,Perl, etc.):
UltraEdit
HTML (incl. PHP/Javascript):
HomeSite
Website Design (DHTML/Tables/CSS/etc.):
Dreamweaver
Graphic Work (Buttons, Logos, etc.):
Fireworks
Telnet:
NetTerm
FTP: CuteFTP Pro
File Management/ Packed Files /FTP on Windows: Windows Commander
Editing (PHP,Perl, etc.):
UltraEdit
HTML (incl. PHP/Javascript):
HomeSite
Website Design (DHTML/Tables/CSS/etc.):
Dreamweaver
Graphic Work (Buttons, Logos, etc.):
Fireworks
Telnet:
NetTerm
By default PLESK accepts files in Binary. WS_FTP will always be a problem until you tell PLESK to make the default ASCII. Then WS_FTP is w/o question superior to anything I have ever used for FTP.
The FTP client, including WS_FTP, can set the file transfer mode between every file transferred, the default, for most graphical FTP clients, on the client is all that matters.
QUOTE
Originally posted by meballard
The FTP client, including WS_FTP, can set the file transfer mode between every file transferred, the default, for most graphical FTP clients, on the client is all that matters.
The FTP client, including WS_FTP, can set the file transfer mode between every file transferred, the default, for most graphical FTP clients, on the client is all that matters.
It does not matter in the case of PLESK & WS_FTP. With WS_FTP it will upload as binary and you will never get a cgi file to execute. That is, until you change the conf file for PLESK so that ASCII is the default.
Forcing WS_FTP to upload as ASCII did nothing for me until I made that change.
I have plesk set to binary and uploading with WS_FTP in ascii was find (although I think there may be a bug in the latest LE version which for some reason you have to switch between binary and ASCII before it realises you want to upload in ascii).
WS_FTP Pro 7.04 does not suffer this problem and ASCII uploads are fine with plesk set to binary.
WS_FTP Pro 7.04 does not suffer this problem and ASCII uploads are fine with plesk set to binary.
Yeah, well for fragile stuff like cgi, perl, etc etc. I will not use FREEware.
My favorites and what I'm using now are CuteFTP Pro for ftp access, My personal Fovorite Macromedia DreamWeaver 4 for HTML related stuff, and extra softwares like these (just cause I can)...
Macromedia Flash 5
Macromedia Fireworks 5
Adobe Photoshop 6
Eye Candy Expansion for Photoshop/Fireworks Plugin
Yeah, of course, these cost an arm and a partial of your leg, but alwell. They get the job done.
Oh yeah, back to cgi/perl related stuff. Since everyone is on the subject...
If I want to add perl modules and since I never install a PM file on my server. How do I install one. It does seem pretty simple to do. Do I need to install it in my root. Root, I mean where all the first directories are like /usr/. And put all the make , make perl, etc commands. Will it install itself into the correct folder?
Better yet, how would I upload files and directories to my root?
My favorites and what I'm using now are CuteFTP Pro for ftp access, My personal Fovorite Macromedia DreamWeaver 4 for HTML related stuff, and extra softwares like these (just cause I can)...
Macromedia Flash 5
Macromedia Fireworks 5
Adobe Photoshop 6
Eye Candy Expansion for Photoshop/Fireworks Plugin
Yeah, of course, these cost an arm and a partial of your leg, but alwell. They get the job done.
Oh yeah, back to cgi/perl related stuff. Since everyone is on the subject...
If I want to add perl modules and since I never install a PM file on my server. How do I install one. It does seem pretty simple to do. Do I need to install it in my root. Root, I mean where all the first directories are like /usr/. And put all the make , make perl, etc commands. Will it install itself into the correct folder?
Better yet, how would I upload files and directories to my root?
Installing perl modules is verry easy.
just type:
perl -MCPAN -e shell
Then you can use
install Mod::Name
to install the module without any further configuration.
just type:
perl -MCPAN -e shell
Then you can use
install Mod::Name
to install the module without any further configuration.
If you do all your stuff on Unix, you don't have to worry about any of this :-)
In fact, I just use scp (secure copy - it's part of OpenSSH) to move files around. Using public key (DSA) authentication, I don't even need to type my password :-)
When you work in web design 24/7 you have to have that sort of software... unfortunately not many of the software out there is any good at things like Perl, PHP, JSP, ASP etc (although XMLSpy is very good at XML and XSL). Well at least to any reasonable level... although Visual Studio.NET is good at ASP.
This although using things like Dreamweaver Ultradev 4 you still have to use trusty old notepad lots.
Photoshop 6 (soon to be 7
)
Flash MX
I think I've gone way off topic but oh well
This although using things like Dreamweaver Ultradev 4 you still have to use trusty old notepad lots.
Photoshop 6 (soon to be 7
)
Flash MX
I think I've gone way off topic but oh well
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.