Contents
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.
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 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”.
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.
Why do I get error when installing CiviCRM in Drupal?
If you get this error on a new Drupal/CiviCRM installation, you may have skipped the step of running CiviCRM’s installation script. You can not install CiviCRM using the standard Drupal module installer. If you see this error, you may need to modify the session.save_handler method for your site.
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.
Is there a fatal error in WP includes / rewrite?
Fatal error: Call to a member function add_rewrite_tag () on a non-object in /home/10/96/3029610/web/wp-includes/rewrite.php on line 172 Please help. Thanks in advance. You just saved me, as well, @travel_girl. Thank you. Due to the plugin Fatal Error cannot even login to admin page.
Do you need a firewall to install CiviCRM?
If CiviCRM is installed on a server behind a firewall with NAT, you’ll need to add your internal IP address and host name to /etc/hosts (on Linux). Otherwise, the dashboard will time out and the Force Secure URLs option will have issues.