Contents
Where do I find stack trace in CiviCRM?
Stack Trace – To display stack trace at the top of the page when an error occurs, set Enable Backtrace from Administer » System Settings » Debugging and Error Handling. This error occurs when your database has lost a MySQL function definition for civicrm_strip_non_numeric.
How to troubleshoot CiviCRM installation in Windows 10?
Go to Administer menu > System Settings > Debugging and Error Handling, select “Yes” to both “Enable Debugging” and “Display Backtrace”, and press “Save”. Repeat the steps that caused your error, and you’ll see a much more detailed error.
How to reset enable debugging to no in CiviCRM?
Set Enable Debugging to Yes and click Save. Click the Administer CiviCRM menu (or any other CiviCRM menu item). After the page is loaded, add an additional query string value ( sessionReset=2) to the URL in your browser’s location bar, and reload the page. Now reset Enable Debugging to No and click Save.
Where to find the CiviCRM fatal error log?
If you receive a CiviCRM fatal error, you can find a more detailed error in one of two ways. CiviCRM fatal errors are characterized by a yellow background: If you have direct access to the files on your server, the CiviCRM log can be found in the ConfigAndLog directory. Directions to find the ConfigAndLog directory can be found here.
Where can I find the CiviCRM installation log?
If you have direct access to the files on your server, the CiviCRM log can be found in the ConfigAndLog directory. Directions to find the ConfigAndLog directory can be found here. Errors are labeled with timestamps, and include both debug and backtrace information.
Where do I find CiviCRM in my Drupal site?
If your CiviCRM codebase is not located in either /modules/civicrm or /sites/all/modules (for example, if you’re using a symlink from there to your codebase) – you will need to create a local file in the top-level directory of your codebase which points to the location of your drupal sites directory.
What to do if CiviCRM is not working?
For example, you will have problems if CiviCRM is configured to use http://example.com as its BASE_URL and your CMS is using http://www.example.com. You can use an .htaccess entry to redirect to the configured URL if needed (i.e. push all users to http://www.example.com even if they hit http://example.com ).
Where can I find the CiviCRM log file?
If you have direct access to the files on your server, the CiviCRM log can be found in the ConfigAndLog directory. Directions to find the ConfigAndLog directory can be found here. Errors are labeled with timestamps, and include both debug and backtrace information. Using the built-in Debugging Tools
Can a CMS use the same machine name as CiviCRM?
Ensure your configuration settings are using the same “machine name” for CiviCRM and your CMS. For example, you will have problems if CiviCRM is configured to use http://example.com as its BASE_URL and your CMS is using http://www.example.com.
What’s the difference between a timestamp and a date?
The TIMESTAMP data type is used for values that contain both date and time parts. TIMESTAMP has a range of ‘1970-01-01 00:00:01’ UTC to ‘2038-01-19 03:14:07’ UTC. A DATETIME or TIMESTAMP value can include a trailing fractional seconds part in up to microseconds (6 digits) precision.
Where to find the configandlog directory in CiviCRM?
Directions to find the ConfigAndLog directory can be found here. Errors are labeled with timestamps, and include both debug and backtrace information. Go to Administer menu > System Settings > Debugging and Error Handling, select “Yes” to both “Enable Debugging” and “Display Backtrace”, and press “Save”.