Log Database Errors to a File
If you would like to log all database errors to a file, enter the path to the file here. The file will be saved as {filename}.log.
Note:
Please note that the directory in which this file is to be created must be writable by the web server.
If you would like to log all failed Admin Control Panel login attempts to a file, enter the path to the file here. The file will be saved as {filename}.log
Note:
Please note that the directory in which this file is to be created must be writable by the web server.
If you would like to log all PHP fatal errors to a file, enter the path to the file here. The file will be saved as {filename}.log.
Note:
Please note that the directory in which this file is to be created must be writable by the web server.
If you would like to log all emails to a file, enter the path to the file here. The file will be saved as {filename}.log. You should only enable email logging if you suspect problems with the email system within vBulletin.
Note:
Please note that the directory in which this file is to be created must be writable by the web server.
If you would like your vBulletin error logs to be rotated when they reach a certain size, enter the maximum file size in bytes here.
1048576 bytes = 1 megabyte.
When a log file reaches this size, it will be renamed as {filename}{unix timestamp}.log and a new file will be created.
Set this value to 0 to disable log rotation.
Disable Database Error Email Sending (yes/no)
If you would like to prevent vBulletin from sending email to the $config['Database']['technicalemail'] address you specified in config.php, set this value to 'Yes'.
- Error reports about database connection errors will still be sent.
- It is not recommended that you set this value to 'Yes' unless you are logging database errors to a file. (see above)