I was upgrading my VCL 2.2.1 and 2.2.3 and ended up braking my conf file.

I'm having issues with making changes

ncluding .ht-inc/conf.php ...
successfully included .ht-inc/conf.php
Checking COOKIEDOMAIN setting in .ht-inc/conf.php ...
COOKIEDOMAIN is not defined in .ht-inc/conf.php
Checking that BASEURL in conf.php is set to use https ...
BASEURL is not defined in .ht-inc/conf.php
Checking that SCRIPT is set appropriately ...
SCRIPT is not defined in .ht-inc/conf.php
Checking that .ht-inc/maintenance directory exists ...
/.ht-inc/maintenance directory exists
Checking that .ht-inc/maintenance directory is writable ...
Maintenance directory is writable
Testing for required php extensions ...
Missing these extensions: ldap. Depending on the extension, some or
all of VCL will not work.
NOTE: The ldap extension is only required if using LDAP authentication
Checking values in .ht-inc/secrets.php ...
all required values in .ht-inc/secrets.php appear to be set
Testing mysql connection ...
Successfully connected to mysql on localhost
Successfully selected database (vcl) on localhost
Testing phpseclib ...
Successfully encrypted test string
Successfully decrypted test string
checking openssl encryption keys ...
successfully created private key from private key file
successfully created public key from public key file
Testing openssl encryption ...
successfully encrypted test string
successfully decrypted test string
Testing for existance of dojo directory ...
dojo directory exists
dojo directory is readable
Checking value of PHP display_errors ...
display_errors: disabled
NOTE: Displaying errors in a production system is a security risk; however,
while getting VCL up and running, having them displayed makes debugging
a little easier. Edit your php.ini file to modify this setting.


Could anyone help me trouble shot this issue.
I'm almost %100 sure my conf.php is correctly setup

-- 
Thanks,
Alex  Patterson
User Support Services
Operating System Analyst
California State University, East Bay

Reply via email to