|
in reply to Re: mkdir through a web interface
in thread mkdir through a web interface
You can mod me down for this as you like, but I see an incessantly overuse of modules going on around here. Everybody cries if you don't use CGI... even for something this simple. Ashley is merely printing ONE line to the screen, I hardly feel this requires the use of CGI.pm.. Now I'm not discrediting the use of modules or CGI.pm in general, I just think that sometimes you guys go a little overboard with it. Hell no I'm not going to use CGI to print one line. That's stupid. Not only that but your reply is out of context with the original question. What exactly does CGI do that's going to stop the 500 errors?
And to address Asley's qustion, the simple answer is probably file permissions.. Namely (as stated above) the permissions associated with the parent directory, the one you are attempting to create directories in, needs to be writable by the server. |
Re: Re: Re: mkdir through a web interface
by Anonymous Monk on Oct 05, 2001 at 02:00 UTC
|
Thanks all. I swore I checked all the premissions, but I guess not. I've got it working now, though.
Thanks again.
Ashley | [reply] |
Re: Re: Re: mkdir through a web interface
by Hero Zzyzzx (Curate) on Oct 05, 2001 at 16:14 UTC
|
I wouldn't mod you down, but I'd still use CGI.pm, even for something this simple, mainly because it takes care of the fact that improperly capitalized headers will make your page behave strangely on some browsers. I'd rather not worry about it, and it's quicker to develop a script like this with CGI.pm than to go and check the exact, proper method to make a header.
Do I use strict and taint checking for little scripts like this that don't take input? Nope. But for everything longer than 5 lines or that takes input I do, just in case.
-Any sufficiently advanced technology is
indistinguishable from doubletalk.
| [reply] |
|
