How could I have this category but not allow access until they pass through the Adult Verification page like http://www.adultcheck.com?
Aug 4, 2000, 7:08 PM
Veteran / Moderator (1936 posts)
Aug 4, 2000, 7:08 PM
Post #4 of 14
Views: 5124
Another thing to keep in mind is you need to modify search.cgi to not include links from the adult categories unless they've logged in (cookies...?). OR run a seperate LINKS engine for the adult categories. That would kill two birds with one stone.
--Drew
--Drew
Aug 5, 2000, 5:27 AM
Enthusiast (700 posts)
Aug 5, 2000, 5:27 AM
Post #5 of 14
Views: 5043
If you have FrontPage 2000, you can make a page that allows users to log in with a username and password that they create (frontpage just uses the same thing we use for our admin protection), that way you can tell adultcheck to take them to that page and they will be able to enter their name and password to sign up...
- Jonathan
http://www.magicdirectory.com/
- Jonathan
http://www.magicdirectory.com/
Aug 5, 2000, 12:31 PM
Enthusiast (700 posts)
Aug 5, 2000, 12:31 PM
Post #7 of 14
Views: 5029
If you really want to do that you can edit this routine in db.pl:
# --------------------------------------------------------
# Adds a record to the database. First, validate_record is called
# to make sure the record is ok to add. If it is, then the record is
# encoded and added to the database and the user is sent to
# html_add_success, otherwise the user is sent to html_add_failure with
# an error message explaining why. The counter file is also updated to the
# next number.
my ($output, $status, $counter);
# First we validate the record to make sure the addition is ok.
$status = &validate_record (%in);
# We keep checking for the next available key, or until we've tried 50 times
# after which we give up.
while ($status eq "duplicate key error" and $db_key_track) {
return "duplicate key error" if ($counter++ > 50);
$in{$db_key}++;
$status = &validate_record (%in);
}
if ($status eq "ok") {
open (DB, ">>$db_file_name") or &cgierr("error in add_record. unable to open database: $db_file_name.\nReason: $!");
if ($db_use_flock) {
flock(DB, 2) or &cgierr("unable to get exclusive lock on $db_file_name.\nReason: $!");
}
print DB &join_encode(%in);
close DB; # automatically removes file lock
if ($db_key_track) {
open (ID, ">$db_id_file_name") or &cgierr("error in get_defaults. unable to open id file: $db_id_file_name.\nReason: $!");
if ($db_use_flock) {
flock(ID, 2) or &cgierr("unable to get exclusive lock on $db_id_file_name.\nReason: $!");
}
print ID $in{$db_key}; # update counter.
close ID; # automatically removes file lock
}
&html_add_success;
}
else {
&html_add_failure($status);
}
}Try adding something like this:
&html_validate_email (%{$links{$id}});
- Jonathan
http://www.magicdirectory.com/
Code:
sub add_record { # --------------------------------------------------------
# Adds a record to the database. First, validate_record is called
# to make sure the record is ok to add. If it is, then the record is
# encoded and added to the database and the user is sent to
# html_add_success, otherwise the user is sent to html_add_failure with
# an error message explaining why. The counter file is also updated to the
# next number.
my ($output, $status, $counter);
# First we validate the record to make sure the addition is ok.
$status = &validate_record (%in);
# We keep checking for the next available key, or until we've tried 50 times
# after which we give up.
while ($status eq "duplicate key error" and $db_key_track) {
return "duplicate key error" if ($counter++ > 50);
$in{$db_key}++;
$status = &validate_record (%in);
}
if ($status eq "ok") {
open (DB, ">>$db_file_name") or &cgierr("error in add_record. unable to open database: $db_file_name.\nReason: $!");
if ($db_use_flock) {
flock(DB, 2) or &cgierr("unable to get exclusive lock on $db_file_name.\nReason: $!");
}
print DB &join_encode(%in);
close DB; # automatically removes file lock
if ($db_key_track) {
open (ID, ">$db_id_file_name") or &cgierr("error in get_defaults. unable to open id file: $db_id_file_name.\nReason: $!");
if ($db_use_flock) {
flock(ID, 2) or &cgierr("unable to get exclusive lock on $db_id_file_name.\nReason: $!");
}
print ID $in{$db_key}; # update counter.
close ID; # automatically removes file lock
}
&html_add_success;
}
else {
&html_add_failure($status);
}
}
&html_validate_email (%{$links{$id}});
- Jonathan
http://www.magicdirectory.com/
Aug 5, 2000, 12:37 PM
Enthusiast (700 posts)
Aug 5, 2000, 12:37 PM
Post #8 of 14
Views: 5160
Actually I think it would be more of something like this:
&html_validate_email (%in);
- Jonathan
http://www.magicdirectory.com/
&html_validate_email (%in);
- Jonathan
http://www.magicdirectory.com/
Aug 6, 2000, 12:10 AM
Enthusiast (700 posts)
Aug 6, 2000, 12:10 AM
Post #10 of 14
Views: 5017
Actually it would go right before or above &html_add_success;
- Jonathan
http://www.magicdirectory.com/
- Jonathan
http://www.magicdirectory.com/
Aug 8, 2000, 12:10 PM
Enthusiast (700 posts)
Aug 8, 2000, 12:10 PM
Post #13 of 14
Views: 5007
It shouldn't be trying to do that because this sub routines only affects links...
- Jonathan
http://www.magicdirectory.com/
- Jonathan
http://www.magicdirectory.com/