Archived

Infinite loop detected in JError in Joomla 1.7

From Joomla! Documentation

Revision as of 08:54, 22 April 2013 by Wilsonge (talk | contribs) (Remove Under Construction Tag as 1.5 years old.)

This page has been archived. This page contains information for an unsupported Joomla! version or is no longer relevant. It exists only as a historical reference, it will not be improved and its content may be incomplete and/or contain broken links.

Copyedit.png
This Page Needs Your Help

This page is tagged because it NEEDS REVIEW. You can help the Joomla! Documentation Wiki by contributing to it.
More pages that need help similar to this one are here. NOTE-If you feel the need is satistified, please remove this notice.


When moving a locally developed Joomla 1.7 site to a server results in the error Infinite loop detected in JError in Joomla 1.7 there's something wrong with the configuration in configuration.php

First double check the following variables:

 public $dbtype = 'mysqli'; // if your server doesn't support mysqli, try 'mysql'
 public $host = '[some host]';
 public $user = '[some database user]';
 public $password = '[some password]';  // wrong password could be the cause
 public $db = '[some database]';
 public $dbprefix = '[someprefix_]';
 public $log_path = '/logs';
 public $tmp_path = '/tmp';

To get detailed information about the error, edit on the server /libraries/joomla/error/error.php

 public static function throwError(&$exception)
 {
     static $thrown = false;
 
 // If thrown is hit again, we've come back to JError in the middle of throwing another JError, so die!
    if ($thrown) {
       // echo debug_print_backtrace();
       jexit(JText::_('JLIB_ERROR_INFINITE_LOOP'));
    }

remove the //commenting tag and add the < pre > tags to get a readable output

 // echo debug_print_backtrace();

change to:

 print"<pre>";
 echo debug_print_backtrace();
 print"</pre>";

Now Joomla will show a more detailed error that might give you some clues of how to correct the settings in your configuration.php. Don't forget to switch off the detailed error reporting afterwards by commenting the echo debug_print_backtrace();.