wayne durden wrote:
I am replacing perl cgi's and have found the process somewhat frustrating.
No matter how simple the tasks are, it seems there are an abundance of
places to make simple mistakes and very little feedback from the server
letting me know where I have goofed this time.
The best way to get more info about the server error is to look at the
server error logs. In many cases, you'll get two lines per error. One
will be the generic error that you see in your browser (error 500,
usually) and the other line, if you're lucky, is the Revolution script
error from the Rev compiler. That line can give you a good clue.
If you aren't getting a Rev error, then the problem may not be in your
script at all, but rather with the server interaction itself. Make sure
your files have correct permissions and that line endings in your text
files are Unix line endings. Those are the two most common causes for
errors that aren't script-related.
Another good technique is to move your cgi script to a button in
Revolution and run it there. You may have to make minor changes for it
to work in the IDE, but that is the easiest way to check whether you're
getting compiler errors.
Finally, you could post a sample here and see if anyone notices where a
problem might be.
--
Jacqueline Landman Gay | [EMAIL PROTECTED]
HyperActive Software | http://www.hyperactivesw.com
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
