Re^2: Authentication Script Path Problems

I think you will need to learn a lot about both, webservers and Perl, and also about how to install modules and how to load them.

You haven't shown any code, so it's hard to suggest changes to your existing code.

As a first tip, do not put any Perl modules below the website document root. Make a parallel directory, say /home/username/lib, and put your modules there. Then modify your CGI scripts to look (roughly) like this:

#!/usr/bin/perl -w
use strict;
use CGI::Carp qw(fatalsToBrowser);
use CGI;
use lib '/home/username/lib';
use MyLib::Simple;

my $q = CGI->new();

print $q->header;
print "Hello";
[download]

Comment on Re^2: Authentication Script Path Problems Select or Download Code

Replies are listed 'Best First'.
Re^3: Authentication Script Path Problems by Anonymous Monk on Sep 12, 2010 at 09:16 UTC
I'm not a programmer. I'm just making my own website so I can go out and do what I do. Here is the code RFC: Proposed tutorial - simple login script using CGI::Application. I haven't altered anything except for the 'use lib' and I'm not using the SSL for now. I'll try the new parallel directory.	[reply]
Re^4: Authentication Script Path Problems by Corion (Patriarch) on Sep 12, 2010 at 10:58 UTC
As you need to have edited the code from the page you linked to, I'll assume that you made some typo there. But you still don't tell me which exact part of the code you used, and what exact changes you made. If you are modifying a script, that makes you a programmer. To become a successful programmer, you will have to learn the main technique associated with it, that is, attention to detail. If you want to successfully communicate about faults in your programs that you can't find, you will have to show others your program as it is, because if you don't know where the fault in your program is, how do you expect others to divine the fault by your (neccessarily) vague retelling alone?	[reply]