About Features Downloads Getting Started Documentation Events Support GitHub

Love VuFind®? Consider becoming a financial supporter. Your support helps build a better VuFind®!

VuFind Documentation

Site Tools

You are here: start » development » troubleshooting
Trace:
Warning: This page has not been updated in over over a year and may be outdated or deprecated.
development:troubleshooting

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
development:troubleshooting [2019/05/03 11:47] – demiankatzdevelopment:troubleshooting [2020/02/19 14:57] – [Turn on Debug Mode] demiankatz
Line 3: Line 3:
 When VuFind doesn't behave as expected, there are several things you can do to gain more information about what is going wrong. When VuFind doesn't behave as expected, there are several things you can do to gain more information about what is going wrong.
  
-===== Check the Apache Error Log =====+===== Check Error Logs =====
  
 If you are not seeing on-screen errors, it is possible that they are being captured by the Apache error log (often found in /var/log/apache2/error.log, /var/log/httpd/error.log, or a similar path). Checking the end of this log (or watching it with the "tail -f" command) may reveal useful information. If you are not seeing on-screen errors, it is possible that they are being captured by the Apache error log (often found in /var/log/apache2/error.log, /var/log/httpd/error.log, or a similar path). Checking the end of this log (or watching it with the "tail -f" command) may reveal useful information.
 +
 +Some operating systems use [[https://php-fpm.org/|PHP-FPM]] to run PHP, and the PHP-FPM error log is another place to check in this case. It is often found at /var/log/php-fpm/www-error.log (or something similar).
  
 ===== Turn on Development Mode ===== ===== Turn on Development Mode =====
Line 23: Line 25:
 If you want more information about what VuFind is doing, you can set the debug setting in the [System] section of your config.ini file (generally found in $VUFIND_LOCAL_DIR/config/vufind/config.ini) to true. This will output debug messages as part of the HTML that VuFind generates. In many cases, these will reveal useful information, but be warned: in some cases, the debug messages will be difficult to read, and they may interfere with some of VuFind's AJAX functionality. If you encounter those problems, proceed to the next section.... If you want more information about what VuFind is doing, you can set the debug setting in the [System] section of your config.ini file (generally found in $VUFIND_LOCAL_DIR/config/vufind/config.ini) to true. This will output debug messages as part of the HTML that VuFind generates. In many cases, these will reveal useful information, but be warned: in some cases, the debug messages will be difficult to read, and they may interfere with some of VuFind's AJAX functionality. If you encounter those problems, proceed to the next section....
  
 +==== "Debug on the Fly" ====
 +
 +You can also turn on debug mode via a URL parameter, if you have appropriate permissions set up. If you add "debug=true" to the end of any VuFind URL, debug mode will be activated if the current user has the "access.DebugMode" permission granted via the [[configuration:permission_options|permission system]]. This feature was broken in several VuFind releases; see [[https://vufind.org/jira/browse/VUFIND-1382|VUFIND-1382]] for details on affected versions and a fix for the problem.
 ===== Turn on Logging ===== ===== Turn on Logging =====
  
development/troubleshooting.txt · Last modified: 2024/02/23 11:36 by demiankatz